[ROM] [7.1.1] newdory (WIP Wear OS 3.0 Clone)

[amir-mahdavi]

I already attempted and failed miserably. That method is guaranteed to soft brick your watch.

Thank you for your advice. Thank you for guiding me out of this danger

 

[amir-mahdavi]

I already attempted and failed miserably. That method is guaranteed to soft brick your watch.

 

[amir-mahdavi]

Does this mean that the only way to flash this ROM is through fastboot and adb?

 

[rodken]

Does this mean that the only way to flash this ROM is through fastboot and adb?

Affirmative - which happens to be the safest way to flash.

 

[amir-mahdavi]

Affirmative - which happens to be the safest way to flash.

Very strange! Because I cleaned and sanded the pins, I can't think of anything else. Because I don't get the usb not recognized error until I turn on adb debugging, but when I activate adb debugging, I get this error.

 

[rodken]

Very strange! Because I cleaned and sanded the pins, I can't think of anything else. Because I don't get the usb not recognized error until I turn on adb debugging, but when I activate adb debugging, I get this error.

Prerequisites

Download the latest Android SDK and the latest drivers from here. Enable USB debugging and open Device Manager and keep it opened.

Steps

1) Connect your device and see if it is detected under "Android Devices" section. If it does, then its OK, otherwise, check the "Other devices" section and install the driver manually.

2) Be sure to check "Android Composite ADB Interface". This is the interface Android needs for ADB to work.

3) Go to "[SDK]/platform-tools", Shift-click there and open Command Prompt and type "adb devices" and see if your device is listed there with an unique ID.

4) If yes, then ADB have been successfully detected at this point. Next, write "adb reboot bootloader" to open the bootloader. At this point check Device Manager under "Android Devices", you will find "Android Bootlaoder Interface". Its not much important to us actually.


5) THIS IS IMPORTANT - At this point, check the Device Manger under "Android Devices". If you do not see anything under this section or this section at all, then we need to manually install it.

6) Check the "Other devices" section and find your device listed there. Right click -> Update drivers -"Browse my computer..." -> "Let me pick from a list..." and select "ADB Composite Interface".

7) Now you can see your device listed under "Android Devices" even inside the Recovery.

8) Write "adb devices" at this point and you should see your device listed with the same ID.

9) Now, just write "adb sideload [update].zip" and your are done.

 

[amir-mahdavi]

Thank you for taking the time to help me. I will try this method

Prerequisites

Download the latest Android SDK and the latest drivers from here. Enable USB debugging and open Device Manager and keep it opened.

Steps

1) Connect your device and see if it is detected under "Android Devices" section. If it does, then its OK, otherwise, check the "Other devices" section and install the driver manually.

2) Be sure to check "Android Composite ADB Interface". This is the interface Android needs for ADB to work.

3) Go to "[SDK]/platform-tools", Shift-click there and open Command Prompt and type "adb devices" and see if your device is listed there with an unique ID.

4) If yes, then ADB have been successfully detected at this point. Next, write "adb reboot bootloader" to open the bootloader. At this point check Device Manager under "Android Devices", you will find "Android Bootlaoder Interface". Its not much important to us actually.


5) THIS IS IMPORTANT - At this point, check the Device Manger under "Android Devices". If you do not see anything under this section or this section at all, then we need to manually install it.

6) Check the "Other devices" section and find your device listed there. Right click -> Update drivers -"Browse my computer..." -> "Let me pick from a list..." and select "ADB Composite Interface".

7) Now you can see your device listed under "Android Devices" even inside the Recovery.

8) Write "adb devices" at this point and you should see your device listed with the same ID.

9) Now, just write "adb sideload [update].zip" and your are done.

 

[amir-mahdavi]

Prerequisites

Download the latest Android SDK and the latest drivers from here. Enable USB debugging and open Device Manager and keep it opened.

Steps

1) Connect your device and see if it is detected under "Android Devices" section. If it does, then its OK, otherwise, check the "Other devices" section and install the driver manually.

2) Be sure to check "Android Composite ADB Interface". This is the interface Android needs for ADB to work.

3) Go to "[SDK]/platform-tools", Shift-click there and open Command Prompt and type "adb devices" and see if your device is listed there with an unique ID.

4) If yes, then ADB have been successfully detected at this point. Next, write "adb reboot bootloader" to open the bootloader. At this point check Device Manager under "Android Devices", you will find "Android Bootlaoder Interface". Its not much important to us actually.


5) THIS IS IMPORTANT - At this point, check the Device Manger under "Android Devices". If you do not see anything under this section or this section at all, then we need to manually install it.

6) Check the "Other devices" section and find your device listed there. Right click -> Update drivers -"Browse my computer..." -> "Let me pick from a list..." and select "ADB Composite Interface".

7) Now you can see your device listed under "Android Devices" even inside the Recovery.

8) Write "adb devices" at this point and you should see your device listed with the same ID.

9) Now, just write "adb sideload [update].zip" and your are done.

I feel like I should be carefree

 

[InvisibleCat]

I dont have playstore on my for some reason

 

[KardchCode]

I dont have playstore on my for some reason

It should install itself after a few mins connected to the phone

 

[KardchCode]

As promised... Update time!

Finally got around UI modding again and this time I think I went for the biggest UI changes. This update changes some UI elements to look like Wear OS 3.0, specially the drawers items. You will notice also some big changes in the Settings app since I reordered the main elements and updated most of the icons so that it looks as close to a pixel watch as possible (also added the Locations panel heh). Updated and cleaned up the build props as well (again huh) and also included a better and lighter Phone Shortcut app. Finally I updated the Google Play app to the latest possible (this was a pain in the ass and I better not explain why) and also updated the system fonts to the Google Sans Text variant (Introduced in A12~ as the default font).

That said, enjoy aand let me know any issues!

Latest newdory 0.8 (24/01/2023):
• Updated build.prop (optimal af now)
• Better Phone Shortcut (source)
• Solved issues with Google Play Store
• Added another level of brightness (lowest possible)
• Updated UI to look like Wear OS 3.0 (wip)
• Updated Settings app look (Wear 3.0 style)
• Added the Location panel in Settings
• Updated fonts to Google Sans Text (Wear OS 3.0 style)

New rom link available here

Btw I'll leave some screenshots so you can see what I'm really talking about

 

[rodken]

As promised... Update time!

Finally got around UI modding again and this time I think I went for the biggest UI changes. This update changes some UI elements to look like Wear OS 3.0, specially the drawers items. You will notice also some big changes in the Settings app since I reordered the main elements and updated most of the icons so that it looks as close to a pixel watch as possible (also added the Locations panel heh). Updated and cleaned up the build props as well (again huh) and also included a better and lighter Phone Shortcut app. Finally I updated the Google Play app to the latest possible (this was a pain in the ass and I better not explain why) and also updated the system fonts to the Google Sans Text variant (Introduced in A12~ as the default font).

That said, enjoy aand let me know any issues!

Latest newdory 0.8 (24/01/2023):
• Updated build.prop (optimal af now)
• Better Phone Shortcut (source)
• Solved issues with Google Play Store
• Added another level of brightness (lowest possible)
• Updated UI to look like Wear OS 3.0 (wip)
• Updated Settings app look (Wear 3.0 style)
• Added the Location panel in Settings
• Updated fonts to Google Sans Text (Wear OS 3.0 style)

New rom link available here

P.S: Hopefully expect Wear OS 3.0 notifications and apps drawer for the next update!

Btw I'll leave some screenshots so you can see what I'm really talking about

Outrageous. Long live Dory.

 

[rodken]

Try "fastboot continue" command. Unfortunately, it is not a permament fix. It will boot into twrp again afterevery restart.

Begin with a clean slate:

Code:
fastboot erase boot
Code:
fastboot erase system
Code:
fastboot erase userdata
Code:
fastboot erase cache
formated all the partitions of the watch by typing :


fastboot format boot
Code:
fastboot format system
Code:
fastboot format userdata
Code:
fastboot format cache

And reboot the watch by typing :

Code:
fastboot reboot bootloader

Reflash the stock recovery for the LG G Watch.

1. Reboot to fastboot again
2. fastboot flash boot /path-to-boot2-img
3. fastboot flash system /path-to-newdory-img
4. Run fastboot -w (it will factory reset your watch)
5. Reboot twice.

You can also send additional apps to the G Watch:
-- adb install app.apk — This will install an apk file on the device and be mindful of the size of the apk. The G Watch only has <4GB of storage space. Keep in mind that you’ll have to copy the apk file to the platform-tools folder or specify a path in the command instead.

 

[Theo1218]

Is it possible to play music on the watch it's some bluetooh earphones?

 

[KardchCode]

Is it possible to play music on the watch it's some bluetooh earphones?

Yes, it should be possible

 

[beastes]

Thank you for this work Wow ! I just found my zw2 and flash this and im very please whit it . It so cool my watch have a second life thank you.

 

[SampIeTexx]

I'm interested in how you bring Wear OS 3 SystemUI into other ROM, will this work on normal android?

 

[KardchCode]

I'm interested in how you bring Wear OS 3 SystemUI into other ROM, will this work on normal android?

What do you mean exactly by "normal android"?

 

[SampIeTexx]

What do you mean exactly by "normal android"?

Like I said, not WearOS. just AOSP

 

[KardchCode]

Like I said, not WearOS. just AOSP

Well, for Wear OS it can only be done by modding over the existing android resources (very limiting). For AOSP tho, should be much easier since the source is completely open. However, backporting android features natively isn't really a choice tbh, so you would probably aim at modifying your current source and making changes to try and mimic your desired look.
So to your question; yeah, this should be doable in normal android (but still a big pita).