[ROM] AW 1.5 Build M9E42C (Use to Downgrade from 2.0)

[TheSt33v]

I have a small hunch that some of you want a one shot, easy way to downgrade to the most recent AW 1.5 version. Here it is. Flash with TWRP.

THIS WILL WIPE YOUR DATA!!!! THIS WILL WIPE YOUR DATA!!! THIS WILL WIPE YOUR DATA!!!

The first boot takes a while. Be patient.

https://www.androidfilehost.com/?fid=889764386195900228

To disable OTA updates, do the following:

1. Download supersuwear.zip (attached to this post) and flash in TWRP to root the watch.
2. Factory reset the watch in TWRP.
3. Boot normally. DO NOT SET UP THE WATCH YET.
4. At the welcome screen, hold the power button until you get into settings.
5. Enable USB debugging.
6. Download the latest version of Google Play Services from here: https://www.apkmirror.com/apk/google-inc/google-play-services-android-wear/
7. Connect to your computer and install this apk file by performing the following command:

adb install -r C:\path to apk file\file.apk
This might take a few minutes. Do not close the window until it says Success.

6. Either use the batch file attached to this post (rename to killUpdate.bat, move to same folder as adb.exe, double click on it) or perform the following commands:

adb shell
su
pm disable com.google.android.gms/.update.SystemUpdateServiceActiveReceiver
pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService
pm disable com.google.android.gms/.update.SystemUpdateWearableActivity
pm disable com.google.android.gms/.chimera.GmsIntentOperationService

7. Reboot the watch.
8. Flash unsu.zip to remove root if desired.
9. Feel free to setup and use the watch normally now.

You will need to repeat these steps if you ever factory reset the watch or delete the data for Google Play Services in the future. If the update ever pops up again, please let me know in this thread or pm me. If you change your mind and you want to go 2.0, use the restoreUpdate batch file in the same way that you used the killUpdate batch file.

 

[inteks]

I have a small hunch that some of you want a one shot, easy way to downgrade to the most recent AW 1.5 version. Here it is. Flash with TWRP.

THIS WILL WIPE YOUR DATA!!!! THIS WILL WIPE YOUR DATA!!! THIS WILL WIPE YOUR DATA!!!

The first boot takes a while. Be patient.

I tried to make it so OTA updates were disabled in this version, but I haven't been able to test it yet. If someone could test that for me, that would be awesome.

https://mega.nz/#!vwZhjZrK!S_3yyZo1JjyQgq3XJTp8ZXpNDb_DVwtyAhlvEForHUA

big thx !!! (i dont like the 2.0!)

one question. is the the "full" image or OTA ? completly stock?

i try this when i'm back home ;o)

btw. i found this (maybe helpfull)->
https://forum.xda-developers.com/g-watch-r/general/to-android-wear-1-5-complete-guide-t3592606

ELIMINATE THE PERSISTENT UPDATE NOTIFICATION

need rooted watch (orginal thread is for LG watch!!!)

1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService

 

[TheSt33v]

big thx !!! (i dont like the 2.0!)

one question. is the the "full" image or OTA ? completly stock?

i try this when i'm back home ;o)

btw. i found this (maybe helpfull)->
https://forum.xda-developers.com/g-watch-r/general/to-android-wear-1-5-complete-guide-t3592606

It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.

The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.

 

[Jrubes]

It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.

The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.

Hi TheSt33v,
I'm trying to better understand how to deploy this to my Huawei watch, as I'm not so certain on which you refer to with regards to using TWRP. Would you, or anyone else, be so kind as to provide a quick write-up or how-to on how to reflash with this image?

Everything I've found so far refers to using ADB to flash the watch, and unsure if that is the same or a different process to using TWRP.

I really dislike AW 2.0 and have no intention to ever go back to it should I be successful in downgrading back to 1.5.

Thank you very much for the work you have done and I hope that you (or someone else) can give just a quick guide.

Thanks everyone!

 

[inteks]

goto https://forum.xda-developers.com/hu...ecovery-negalite-hw-twrp-3-0-2-0-lz4-t3448137
and download negalite-HW-TWRP-3.0.3-v1.5.img

enable usb debugging
adb push '.\Downgrade to M9E42C.zip' /sdcard/
adb reboot bootloader
fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img

on watch select "install zip"
select /sdcard/Downgrade to M9E42C.zip

 

[TheSt33v]

Hi TheSt33v,
I'm trying to better understand how to deploy this to my Huawei watch, as I'm not so certain on which you refer to with regards to using TWRP. Would you, or anyone else, be so kind as to provide a quick write-up or how-to on how to reflash with this image?

Everything I've found so far refers to using ADB to flash the watch, and unsure if that is the same or a different process to using TWRP.

I really dislike AW 2.0 and have no intention to ever go back to it should I be successful in downgrading back to 1.5.

Thank you very much for the work you have done and I hope that you (or someone else) can give just a quick guide.

Thanks everyone!

The guide provided by inteks is accurate, mostly. Alternatively, you can use the same method with my updated version of TWRP here: https://forum.xda-developers.com/hu...ent/recovery-twrp-3-1-0-0-unofficial-t3603001. The older version should work just as well though.

 

[TheSt33v]

goto https://forum.xda-developers.com/hu...ecovery-negalite-hw-twrp-3-0-2-0-lz4-t3448137
and download negalite-HW-TWRP-3.0.3-v1.5.img

enable usb debugging
adb push '.\Downgrade to M9E42C.zip' /sdcard/
adb reboot bootloader
fastboot boot negalite-HW-TWRP-3.0.3-v1.5.img

on watch select "install zip"
select /sdcard/Downgrade to M9E42C.zip

adb reboot-bootloader

 

[inteks]

adb reboot-bootloader

adb reboot bootloader also work i know this because that are the steps i put into my console
anyway

but it seems that your disableOTA.sh does not work. it runs without errors but the services are still active. maybe because pm cannot disable services from recovery if wear is not running...

i flashed superuser and disabled them from adb shell.

this is my "debloat" script

pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
pm disable com.google.android.apps.fitness
pm uninstall me.timos.busyboxonrails
pm disable com.huawei.dailytrack

(chargedetection has to be disabled if you use chargingwidget)

pm disable com.huawei.mercury.chargedetection

 

[TheSt33v]

adb reboot bootloader also work i know this because that are the steps i put into my console
anyway

but it seems that your disableOTA.sh does not work. it runs without errors but the services are still active. maybe because pm cannot disable services from recovery if wear is not running...

i flashed superuser and disabled them from adb shell.

this is my "debloat" script

pm disable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gsf/.update.SystemUpdateService
pm disable com.google.android.apps.fitness
pm uninstall me.timos.busyboxonrails
pm disable com.huawei.dailytrack

(chargedetection has to be disabled if you use chargingwidget)

pm disable com.huawei.mercury.chargedetection

I thought that might be the case. My goal was to make this as easy as possible, so I don't want to tell people to root just yet. I'll see if I can include a script that runs at boot that disables the services. Rooting might be unavoidable though. If it is, I'll pre-root the image.

Maybe I can decompile the appropriate apk and disable it that way...

 

[Jrubes]

Thanks everyone! I was able to successfully downgrade back to 1.5 with this information. As previously mentioned, the update notification is still there.

Thanks again for all the hard work and the assistance.

 

[agarth]

It is completely stock. It's the full image, but it does not include the bootloader, userdata, cache or recovery images. Including the bootloader is unnecessary, as 1.5 runs just fine with the 2.0 bootloader and flashing the bootloader would require that people unlock their bootloaders first. Without the bootloader image, this package can be flashed with a locked bootloader. I didn't include userdata or cache because these partitions were not changed at any point in the history of HW updates, so simply wiping those partitions is sufficient. I didn't include recovery.img because that would erase people's TWRP installations, and if you never plan on updating, there is no reason to have the stock recovery. However, if anyone wants any of the images that I left out, I have them and will provide them upon request.

The commands that you linked to are integrated in this zip. Please let me know if you see any OTA pop ups when you give this a try. If it doesn't work, I'll try to figure out a better way to disable them.

Thanks for your work! I want to back to competely stock M9E42C but I find the files just for M6E69F. Can you share all the images please? Also, do I have to wipe data, cache, or something in twrp?
EDIT: I found the zip containing the 3 OTAs to install in M6E69F. Which is the right way?

 

[TheSt33v]

Thanks for your work! I want to back to competely stock M9E42C but I find the files just for M6E69F. Can you share all the images please? Also, do I have to wipe data, cache, or something in twrp?
EDIT: I found the zip containing the 3 OTAs to install in M6E69F. Which is the right way?

If you found the zip containing the 3 OTAs, just install them in order (update1, update2, update3) when you're on M6E69F. Make sure to reboot in between each update.

Or if you prefer, flash my M9E42C zip (cache and data are wiped automatically) and then flash the following images via fastboot:

Recovery: https://www.androidfilehost.com/?fid=817550096634771860

Bootloader: https://www.androidfilehost.com/?fid=673368273298957367

 

[agarth]

If you found the zip containing the 3 OTAs, just install them in order (update1, update2, update3) when you're on M6E69F. Make sure to reboot in between each update.

Or if you prefer, flash my M9E42C zip (cache and data are wiped automatically) and then flash the following images via fastboot:

Recovery: https://www.androidfilehost.com/?fid=817550096634771860

Bootloader: https://www.androidfilehost.com/?fid=673368273298957367

Thanks a lot for the clear answer! :good:

 

[Bielinsk]

I have flashed the supersuwear.zip in twrp rebooted and when I try to SU, I get

/system/bin/sh: su: not found

NM I got it

 

[ddaggebi]

Is there any stock fastboot .img files for wear 1.5 or 2.0?
I want to go completely stock whenever I want to.
It seems that there was a download link in developer.android.com but it must have been removed...
Can anyone share fastboot img files?
I especially need stock wear 2.0 recovery img or all images for wear 1.5.

Also a noob question: is it safe to relock after flashing twrp? When I used Huawei 6P, its bootloader shouldn't be unlocked unless every file(boot, recovery, system, etc...) is completely stock. Is it the same with Hwatch?

 

[alleyman]

Does this require a bootloader unlock before proceeding?

(Please ignore, found the answer (it doesn't), mustve been blind )

 

[TheSt33v]

Is there any stock fastboot .img files for wear 1.5 or 2.0?
I want to go completely stock whenever I want to.
It seems that there was a download link in developer.android.com but it must have been removed...
Can anyone share fastboot img files?
I especially need stock wear 2.0 recovery img or all images for wear 1.5.

Also a noob question: is it safe to relock after flashing twrp? When I used Huawei 6P, its bootloader shouldn't be unlocked unless every file(boot, recovery, system, etc...) is completely stock. Is it the same with Hwatch?

Sorry for the late response, but here is the factory image for 1.5 build M6E69F (not the most recent build of 1.5): https://www.androidfilehost.com/?fid=745425885120748838

Here are the three OTAs that will take you from M6E69F to M9E42C (do not flash directly, extract the three zips within and flash those in order): https://www.androidfilehost.com/?fid=745425885120732730

I'm not aware of any other official factory images other than the 2.0 dev preview images, but I didn't hang on to those.

Also, note that if you take an OTA from ANY version of 1.5 using your watch's official OTA function, you will be directly updated to 2.0. You can't use the OTA function to get to the latest version of 1.5. The only options are using the official OTAs that I posted or flashing the TWRP package that takes you straight there.

 

[ddaggebi]

Sorry for the late response, but here is the factory image for 1.5 build M6E69F (not the most recent build of 1.5): https://www.androidfilehost.com/?fid=745425885120748838

Here are the three OTAs that will take you from M6E69F to M9E42C (do not flash directly, extract the three zips within and flash those in order): https://www.androidfilehost.com/?fid=745425885120732730

I'm not aware of any other official factory images other than the 2.0 dev preview images, but I didn't hang on to those.

Also, note that if you take an OTA from ANY version of 1.5 using your watch's official OTA function, you will be directly updated to 2.0. You can't use the OTA function to get to the latest version of 1.5. The only options are using the official OTAs that I posted or flashing the TWRP package that takes you straight there.

Thanks for kindly answering my nooby question!
So in theory, if I want to set my watch to completely stock 2.0, I have to flash 1.5 factory image and OTA it to 2.0, right? Again, Thanks!

 

[TheSt33v]

Thanks for kindly answering my nooby question!
So in theory, if I want to set my watch to completely stock 2.0, I have to flash 1.5 factory image and OTA it to 2.0, right? Again, Thanks!

Yes

 

[pjl3dm]

I was on Android Wear 2.0 with a locked bootloader.

Now I just tried this method to downgrade from 2.0 to 1.5.

I installed TWRP, then pushed the zip file to /sdcard/

Flashed the zip in TWRP. Now it's stuck on the google animation for like 20mins now.. is this normal?