• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]

Search This thread

ghost_monk

New member
Jan 5, 2011
2
0
Tried using the pro 2020 rom on a pro S and I was able to get to the recovery to delete the cache but the sideload fails with "adb: failed to read command: Success" this a normal issue with sideload? I am using Linux
 

boycott56

Member
Dec 16, 2020
14
0
My device is 4G/LTE, it's unlocked, I'm using ROM 2-ROM-PWDD.190617.059.A3-Dec-28. (USB debugging switched on)
Now I'm wanting to lock bootloader, but after command "adb devices" get "list of devices attached" but nothing showed.
"adb reboot bootloader" works, the watch reboots.
But "fastboot devices" doesn't recognize the watch.
Any idea?
 
I attached the one that worked for me when flashing the stock images! Hope this helps you out! Actually, to install the stock.img files should be done with fastboot not Twrp! You have to get the watch in bootloader mode, than use command prompt and run the command fastboot devices, and see if it picks up your device! Than flash each img file to the corresponding partition!
Thank you so much. I've spent like 3 hours trying to get my watch back to stock because of a bootloop. Flashing each individual .img with fastboot worked for me.....Now to try this again 😆
 
I was late to the party and just got a Tic Watch Pro 4G a few days ago. Of course the first thing I did was look for a root solution. I got it rooted and running great except for the data part of it. I rooted it before I activated the service so I don't know if root is why I'm having issues. Bluetooth calling and texts work for about an hour then it seems to always forget the permissions I granted it and asks everytime. When it starts doing that the calls always fail then I open the phone app and it's asks for permission again. Anyone else have this issue?
Besides that, what are you guys doing with your rooted watch? I found a few apps that run great on mine.

1. Package Disabler Pro (Samsung) works surprisingly well.

2. SELinux Mode Changer. Change SELinux to permissive. Lol, not sure why but I did because I could.

3. Busy Box Pro. I couldn't get the Watch zip version to stick so I gave it a shot and it worked.

4. Root Essentials works great.

5. Termux installed but the keyboard is an issue. Anyone know how to use adb to push the "Enter" key☺️. "adb shell pm input text"
Will input text, just can't hit Enter, lol. Keyevent 66 seems to do nothing.

6. L-Speed works nicely

7. The forbidden app "Lucky Patcher" works great. I use it to get lists of services and it's convenient to get info on apk's and app locations. Don't judge me.

8. And the amazing app simply called "App Manager" from F-Droid. Works perfectly.
 
Last edited:
  • Like
Reactions: Ofelipe

SmartwatchDestroyer

New member
Oct 2, 2021
4
0
Hello people,
I have a problem and hope one can still save me here or better said my SmartWatch still save. I tried to update my SmartWatch with @janjan's firmware to get some more joy out of the old watch. Unfortunately, that didn't work and the watch kept booting back into recovery. I think now retrospectively, this would have been the time to ask for help here, but I had decided something else.
Instead, I had decided to load the stock rom from the entrance post onto the SmartWatch. This must have made it worse, because now the clock only shows the logo as shown in the linked video.

many thanks in advance
The video: https://devtube.dev-wiki.de/videos/watch/679cabfe-474e-4c98-b851-4598544ac078?muted=1
bild.php
 
Hello people,
I have a problem and hope one can still save me here or better said my SmartWatch still save. I tried to update my SmartWatch with @janjan's firmware to get some more joy out of the old watch. Unfortunately, that didn't work and the watch kept booting back into recovery. I think now retrospectively, this would have been the time to ask for help here, but I had decided something else.
Instead, I had decided to load the stock rom from the entrance post onto the SmartWatch. This must have made it worse, because now the clock only shows the logo as shown in the linked video.

many thanks in advance
The video: https://devtube.dev-wiki.de/videos/watch/679cabfe-474e-4c98-b851-4598544ac078?muted=1
bild.php
I got a TicWatchPro 4G just about a week ago. I was flashing this stuff to it and it wasn't working right. Root or no root it wouldn't remember permissions and data would not work. I'm from the US so I was flashing the US version. When I was out of ideas and US options, I said "F it" nothing left to flash but the EU versions. And wouldn't you know, I now have root on a perfectly functional watch, lol.
Here is what fastboot looks on mine.

Have you tried flashing each individual image with fastboot? If all else fails try the EU version. If that doesn't work don't worry you can still flash another version. Good luck finding one from anywhere besides this thread though.
Very odd that tic watch firmware is like non- existant across the internet except here
 

Attachments

  • 20211002_111258.jpg
    20211002_111258.jpg
    1.1 MB · Views: 13
Last edited:
My device is 4G/LTE, it's unlocked, I'm using ROM 2-ROM-PWDD.190617.059.A3-Dec-28. (USB debugging switched on)
Now I'm wanting to lock bootloader, but after command "adb devices" get "list of devices attached" but nothing showed.
"adb reboot bootloader" works, the watch reboots.
But "fastboot devices" doesn't recognize the watch.
Any idea?
you have the fastboot driver installed?
 
Hello and sorry for bothering but where can I find the stock EU rom for Ticwatch Pro 4g/LTE. I can only see, in mega folder, the USA stock version.

Or can I use the USA version?

Thank you very much.

Edit. I used the USA version and all my problems are solved. Before this the watch was getting blocked and reboots randomly, the screen made strange thing (the menu moved itself) and it didn't respond to the touches. Now it works everything, esim and pay nfc (like before)
 
Last edited:
my Ticwatch-Pro-4G-USA(Catshark) is booting into twrp every boot after hangign on the initial setup. so far I've tried flash vendor ... Boot to that twrp ... Then factory wipe, advance wipe, format data, sideload ... Flash ROM , BusyBox then magisk also am I using the correct busybox as the link was dead

- Busybox 1.31.1 NDK - One single file for all CPU

Busybox 1.31.1 NDK ARMv7 32bit/ARMv8 64bit/Stabndard/SELinux - ZIp installer for recovery - Host mega
Still having issues? I have to exact same watch as you. Nothing worked right until I flashed the EU version. Funny thing is that I live in Ohio, which is the US for people who don't know the states. As for Busybox. I couldn't get it to flash so you know what I did. I installed it from the Play Store with my phone, extracted the apk and used adb to install it on my watch. Worked perfectly. I used BusyBox Pro, but I would think any version would work also
 

SmartwatchDestroyer

New member
Oct 2, 2021
4
0
Hello people,
I have a problem and hope one can still save me here or better said my SmartWatch still save. I tried to update my SmartWatch with @janjan's firmware to get some more joy out of the old watch. Unfortunately, that didn't work and the watch kept booting back into recovery. I think now retrospectively, this would have been the time to ask for help here, but I had decided something else.
Instead, I had decided to load the stock rom from the entrance post onto the SmartWatch. This must have made it worse, because now the clock only shows the logo as shown in the linked video.

many thanks in advance
The video: https://devtube.dev-wiki.de/videos/watch/679cabfe-474e-4c98-b851-4598544ac078?muted=1
bild.php
is anyone able to dump me there working firmware for the TicWatch Pro Catfish? I have seen the Vendor part is missing on the MEGA-Link.
 

Nazar27015

New member
Oct 9, 2021
1
0
Hello! tell me how to return to the stock on the tikvatch about 512 mb, it is more clear, and if possible, then in Russian.the problem is that I have a custom, but for some reason the magisk is not installed, I tried different versions, nothing happens, writes that it will be installed , my watch sees the root, without the magic, I can start Google pay.
 

Top Liked Posts

  • 1
    The 2020 august ROM seems to work except root.
    I have installed the Magisk-v23.0 with TWRP (renamed the apk to zip).

    The su command is a symlink to a zero-byte file:
    Bash:
    catfish:/ $ ls -la /sbin/su
    lrwxrwxrwx 1 root root 8 1970-01-07 01:57 /sbin/su -> ./magisk
    catfish:/ $ ls -la /sbin/magisk
    lrwxrwxrwx 1 root root 10 1970-01-07 01:57 /sbin/magisk -> ./magisk32
    catfish:/ $ ls -la /sbin/magisk32
    -rwxr-xr-x 1 root root 0 1970-01-07 01:57 /sbin/magisk32

    Any suggestion?

    My other problem is that the busybox link in the first post is broken. Where can I download the busybox zip that 100% works with this ROM?

    Thanks
    1
    The 2020 august ROM seems to work except root.
    I have installed the Magisk-v23.0 with TWRP (renamed the apk to zip).

    The su command is a symlink to a zero-byte file:
    Bash:
    catfish:/ $ ls -la /sbin/su
    lrwxrwxrwx 1 root root 8 1970-01-07 01:57 /sbin/su -> ./magisk
    catfish:/ $ ls -la /sbin/magisk
    lrwxrwxrwx 1 root root 10 1970-01-07 01:57 /sbin/magisk -> ./magisk32
    catfish:/ $ ls -la /sbin/magisk32
    -rwxr-xr-x 1 root root 0 1970-01-07 01:57 /sbin/magisk32

    Any suggestion?

    My other problem is that the busybox link in the first post is broken. Where can I download the busybox zip that 100% works with this ROM?

    Thanks
    I got you😁
  • 1
    I was late to the party and just got a Tic Watch Pro 4G a few days ago. Of course the first thing I did was look for a root solution. I got it rooted and running great except for the data part of it. I rooted it before I activated the service so I don't know if root is why I'm having issues. Bluetooth calling and texts work for about an hour then it seems to always forget the permissions I granted it and asks everytime. When it starts doing that the calls always fail then I open the phone app and it's asks for permission again. Anyone else have this issue?
    Besides that, what are you guys doing with your rooted watch? I found a few apps that run great on mine.

    1. Package Disabler Pro (Samsung) works surprisingly well.

    2. SELinux Mode Changer. Change SELinux to permissive. Lol, not sure why but I did because I could.

    3. Busy Box Pro. I couldn't get the Watch zip version to stick so I gave it a shot and it worked.

    4. Root Essentials works great.

    5. Termux installed but the keyboard is an issue. Anyone know how to use adb to push the "Enter" key☺️. "adb shell pm input text"
    Will input text, just can't hit Enter, lol. Keyevent 66 seems to do nothing.

    6. L-Speed works nicely

    7. The forbidden app "Lucky Patcher" works great. I use it to get lists of services and it's convenient to get info on apk's and app locations. Don't judge me.

    8. And the amazing app simply called "App Manager" from F-Droid. Works perfectly.
    1
    The 2020 august ROM seems to work except root.
    I have installed the Magisk-v23.0 with TWRP (renamed the apk to zip).

    The su command is a symlink to a zero-byte file:
    Bash:
    catfish:/ $ ls -la /sbin/su
    lrwxrwxrwx 1 root root 8 1970-01-07 01:57 /sbin/su -> ./magisk
    catfish:/ $ ls -la /sbin/magisk
    lrwxrwxrwx 1 root root 10 1970-01-07 01:57 /sbin/magisk -> ./magisk32
    catfish:/ $ ls -la /sbin/magisk32
    -rwxr-xr-x 1 root root 0 1970-01-07 01:57 /sbin/magisk32

    Any suggestion?

    My other problem is that the busybox link in the first post is broken. Where can I download the busybox zip that 100% works with this ROM?

    Thanks
    1
    The 2020 august ROM seems to work except root.
    I have installed the Magisk-v23.0 with TWRP (renamed the apk to zip).

    The su command is a symlink to a zero-byte file:
    Bash:
    catfish:/ $ ls -la /sbin/su
    lrwxrwxrwx 1 root root 8 1970-01-07 01:57 /sbin/su -> ./magisk
    catfish:/ $ ls -la /sbin/magisk
    lrwxrwxrwx 1 root root 10 1970-01-07 01:57 /sbin/magisk -> ./magisk32
    catfish:/ $ ls -la /sbin/magisk32
    -rwxr-xr-x 1 root root 0 1970-01-07 01:57 /sbin/magisk32

    Any suggestion?

    My other problem is that the busybox link in the first post is broken. Where can I download the busybox zip that 100% works with this ROM?

    Thanks
    I got you😁
  • 77
    -[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020]
    - [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020]
    - [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020]
    #############################
    - [Ticwatch Pro 4G/LTE (USA) (Catshark)-PWDD.190617.032]-[DISCONTINUED]-
    -[Ticwatch C2 (Skipjack)-PWDS.190618.001.B4]-[DISCONTINUED]
    -[Ticwatch E2 (Tunny)-PWDS.190618.001.B3]-[DISCONTINUED]
    #############################



    Code:
    ****Disclaimer****
    [COLOR="Red"][B]WARNING:  IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS. I accepts no responsibility for any damage to your device. Please read the instructions and notes before flashing anything[/B][/COLOR]

    IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
    DONATE-ME-HERE

    ###################
    REQUIREMENTS
    ###################

    - Ticwatch Pro, Ticwatch Pro 4G, Ticwatch Pro 2020 Ticwatch C2 and Ticwatch E2 ONLY INTERNATIONAL VERSION. It may also work on Chinese version too but I haven't test it personally.
    - An unlock bootloader, working driver and working adb/fastboot
    - You can download ADB/FASTBOOT from here Download: ADB/FASTBOOT
    - Custom recovery TWRP- (Se download section below)

    ###################
    HOW TO FLASH- STEPS
    ###################

    (FOLLOW EITHER THE INSTRUCTIONS FROM MEGA FOLDER OR THE STEPS BELOW)

    - Download the latest ROM, latest vendor, latest Magisk and busybox - (Everything are include in the MEGA folder)
    - Attach your watch to your PC and enable USB Debugging from settings menu. Ensure adb/fastboot is working. Please Google and see "how to enable debugging from settings menu".
    - Extract the vendor folder and go inside the folder (Here you will find vendor.img and twrp.img + other files)
    (You have to flash the vendor image and format userdata and cache)
    - Boot your watch into fastboot/bootloader mode by applying the following code.
    Code:
    - adb devices
    - adb reboot bootloader
    - fastboot flash vendor vendor.img
    - fastboot format userdata OR fastboot erase userdata
    - fastboot format cache OR fastboot erase cache
    - fastboot boot NAME-OF-THE-TWRP.img (Se the name of the twrp.img)

    - Now move the ROM, Magisk and busybox to your watch.
    - Flash the ROM and reboot. If you prefer root then
    - Flash busybox and finally Magisk (IMPORTANT flash ROM, then Busybox and Magisk in this order)

    NOTE
    - When rebooting your watch, IF a Prompt come up and asking about installing twrp bla.bla then un-mark both lines/ then click on DO Not Install
    - Let your device boot up, then connect your watch to your phone and finish the initial setting
    - Open Magisk Manager and go to settings and set Automatic Response to Grant, Uncheck updates and Superuser notifications to None
    - Reboot and enjoy

    ###################
    ROM AND KERNEL FEATURES-
    See latest changelog here
    ###################

    DOWNLOAD
    [DECRYPTION KEY]
    Code:
    iZbWXMs8vabDW1szJz1hgg

    OPTIONAL
    TO INSTALL KERNEL CONTROL APP WEAR OS

    Code:
    - Download the KernelAudiutor4Wear.apk from above link and move it to your adb folder.
    - adb devices
    - adb install KernelAudiutor4Wear.apk

    MAGISK/BUSYBOX/APP-KERNEL-CONTROL
    DOWNLOAD LATEST MAGISK FROM HERE
    DOWNLOAD LATEST BUSYBOX FROM HERE
    KERNEL CONTROL APP WEAR OS

    ###################
    BACK TO STOCK ROM
    See Mega folder for Stock images
    Code:
    [[B]DECRYPTION KEY[/B]]
    iZbWXMs8vabDW1szJz1hgg
    [B][SIZE="4"]STEPS[/SIZE][/B]
    - fastboot flash aboot aboot.img
    - fastboot flash boot boot.img
    - fastboot flash recovery recovery.img
    - fastboot flash vendor vendor.img
    - fastboot flash system system.img
    - fastboot format userdata OR fastboot erase userdata
    - fastboot format cache OR fastboot erase cache
    - fastboot reboot
    ##############################
    Source/GitHub
    ##############################

    -Source
    -Source
    -Source

    ###################
    IF YOU LIKE MY WORK AND WANT TO BUY ME A COFFEE
    DONATE-ME-HERE
    ###################

    Special thanks to:
    If you can, donate and respect all the devs and enjoy :)
    @Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
    @topjohnwu for his great effort (Magisk)Thank you so much
    @SuperR.R for the great kitchen
    @YashdSaraf for the busybox (I edit a bit to make it work for Ticwatch-pro)
    Sultan Al Sawaf for his patch
    Mobvoi, Google and Qualcomm for providing us the kernel source.
    Please always support devs and others (soon).
    21
    Performance Tips

    Final Update
    Janjan has already included in the new rom all of these changes. So no need to keep reading this post.

    I'll leave it here in case it helps someone with other type for smartwatch.

    Great job @janjan keep it going.

    ------------------- Original Post -------------------------
    Here are my two cents on performance on this device.

    The Problem
    Like in many android devices one of the main issues ( i learned this with old phones ) is the RAM and Swap.
    While switching apps or opening new ones the following events happen (please remember this is a linux based OS so all of this assumptions are based on Linux experience)

    1. App open request happens
    2. Os checks if app is running if it is is switches to it
    2.a If app is in RAM it loads it from there
    2.b if its not it loads it from the swap to the RAM and then loads it from there (less expensive than reopening the app)
    3. If app is not running it start it (running all the initialization procedures that can be very expensive in some apps) and gets the app to RAM

    Now, if at any point of that process the RAM is full, the OS will dump another app to Swap. If the swap is full the OS will dump another (least used app) completely out of the system stopping it and therefore having to reopen it entirely later on (expensive process).

    Ok. Now that this is clear lets see the Ticwatch.
    The available RAM is less than 512Mb. After the system boots and all the Google services, google play, keyboard services, assistant, etc are loaded we end up with less than 100Mb available. Enough to open two apps. One of them being the launcher, "wearable.app". After this the thing start swapping. Right?.....Wrong!!!

    See, there is no swap on the device. therefore opening any app will force another one out of the system completely stopping it and having to restart it later on (EXPENSIVE for CPU and Battery). This includes the wearable app. Your watchface.
    One of the apps really capable of doing this is Google Play since it just LOVES RAM. It will kick everythinbg out of RAM pretty much, including your watchface. And since it runs background processes (like app updating) the OS will find hard to kick Google Play out of RAM as well.

    I will not post more examples and reasons why Swap is important. But I will post the solution

    The solution
    USE AT YOUR OWN RISK
    Creating a swap file will allow us to extend the maximum amount of available RAM. We are aware that RAM disk is slow, and should be avoided at all cost, but in this case it is quite beneficial. Here is how to enable it

    1. Have the custom ROM installed
    2. Have the latest kernel installed
    3. Have developer options enabled
    4. Have busybox and magisk installed

    Run the following commands on your computer
    adb devices (device should show up there if properly connected)
    adb shell
    su (approve access on device itself)
    fallocate -l 256M /sbin/.magisk/mirror/data/swapfile
    mkswap /sbin/.magisk/mirror/data/swapfile
    swapon /sbin/.magisk/mirror/data/swapfile
    sysctl vm.swappiness=60

    Now, some notes
    1. The 256Mb is a (so far) arbitrary number I came up with. Over monitoring it closely it seems that 256Mb is enough. Change this to your liking. You can check the amount of used swap by running the command top while in adb shell
    2. The selected swappinesss is the default for a desktop computer, it may require tweaking but so far seems ok.
    3. Updating apps with the play store still uses a LOT of CPU, but is way more responsive now and I would recommend updating apps only when you are not going to need the watch or while charging.
    4. Use this alongside kernel auditor and ondemand governor with 4 cores enabled and 1.2Ghz as max cpu frequency.
    5. After reboot swap will be lost and you will have to set it up again. Please note that I did it this way since i'm still testing this.
    6. Your device may have a reduces SD life and could be detrimental if the manufacturer used a low grade chip

    The Result
    Well. Apps NEVER get relaunched.
    1. They never get stopped in the first place in order to make space for other apps
    2. They switch WAY faster since they are either in RAM or in SWAP
    3. First launch of any app is faster since other apps don't need to be stopped first
    4. Finally the TicWatch Pro is a useful device. I no longer think that getting a Google Authenticator code will be faster if i just use my phone.

    I hope this helps you all.
    I'm available to answer your questions on European (i'm awake) times.

    ---------- Post added at 06:57 PM ---------- Previous post was at 06:27 PM ----------

    I recorded a video to show the snappiness of the device now.
    Note about the video. Some apps where previously opened (therefore where on RAM or the new shinny SWAP)
    other apps like the flashlight, weather and Magisk, where not. but you can see that after opening them they reopen (switch back) pretty much instantly.
    During the video the Swap usage was 140Mb.

    Link to video - Please remove spaces since XDA does not allow me to post links XD:
    https ://youtu.be/UVk4JLqC8Do

    One of the main things I realized is that after launching the google assistant (hold main button 1 sec) I can actually relaunch it 100 times after that (including app witching) and still get my response to (turn on the lights in the house, or how is the weather in less than 1 sec)

    This is a must try :)

    ------------------------------------------------------ Update 1 -----------------------------------------------------------

    After testing, using swap seems to affect battery usage on a rate of about 10% drain (depends on your usage).
    The main reason could be the fact that now we are using the storage a lot more, and using the storage means that this chip will consume more power.
    my watch have been running now for 2 days (with 1 battery charge in between) and I had not performance issues. I was able to work with notifications, receive phone calls, use the assistant, google fit, etc.

    ------------------------------------------------------ Update 2 -----------------------------------------------------------
    I realized that after having every app running and not having to boot them again the device battery is actually well improved. I'm doing 36-48h now.
    Also realized that finally the Google assistant is useful. Responsive and helpful
    I reduced the amount of cache to 256Mb and updated the script. Seems to be enough for a custom watchface Google fit, assistant, calendar, weather, hr monitor and Google play to run at the same time.
    Do not try (as I did), to run 1Gb of swap. You will never get to use it and since you need to allocate all the space at once you cannot install more apps. The device will become unresponsive and and connection fails at this point for a reason. Causing weird connection and disconnections

    ------------------------------------------------------ Update 3 -----------------------------------------------------------
    How to make it persistent after reboot
    Here is small script in oder to make the swap permanent
    I did not find a way to use the fstab or the init.rc since none of them seem to be available in Android
    It seems that is available in some devices but not on other. But, since we also need Magisk for the actual swap we can also use it to run the script using the handy service.d folder

    Script (save to a remount_swap.sh file in your pc, you can do this with a text editor, just make sure that you don't accidentally have a .txt at the end)
    #!/system/bin/sh
    sleep 10
    sysctl vm.swappiness=60
    swapon /sbin/.magisk/mirror/data/swapfile

    How to copy the script
    adb push <path_to_your_script>\remount_swap.sh /storage/emulated/0/
    adb shell
    su
    cd /storage/emulated/0/
    mv remount_swap.sh /sbin/.magisk/img/.core/service.d/
    cd /sbin/.magisk/img/.core/service.d/
    chmod +x remount_swap.sh
    adb reboot
    20
    Hello there..
    First of all I am apologize for the delay. I am still experimenting and trying different settings with the new ROM and kernel. So far so good.... Kernel and ROM, both are almost ready, But I am still working with a script in order to create and use zram as a swap space/ virtual memory. It is the best combination of RAM and disk space. It seems it doesn't use the CPU all the time...which means doesn't reduce the battery. I tried different settings of zram and swap and end up with this..balance with CPU usage and battery. It boost the speed and gives more memory and good battery..Almost 3 days of battery..(ofc depends how much u use the watch)

    The scripts is also done now...I am happy with that. I also implement init.d in the ROM in order to use the script automatically. It is also possible to just flash the script in TWRP. I just need to clean up and take sometime to upload the ROM.

    I would also like to thanks those who have donated me. I really appreciate that. Thank you so much for your donation.

    I am also start working with Ticwatch C2 and Ticwatch Pro 4G. New ROM and kernel for both devices are coming too.
    12
    Hi all.
    This is perfect way to get Gpay on your watch. Tested by TicWatch Pro

    Go to https://sqlite.org/download.html and download sqlite-tools-win32-x86-3280000.zip
    Unzip and use sqlite3.exe
    You have to got ADB files

    Let's go

    0. Commands start to execute from cmd, so that adb and sqlite3 was visible from there (put in the desired directory, or run with the full path)
    1. Enable Developer on watch (click on the build number in about watch")
    2. Enable adb debugging
    3. Open cmd On PC (adb folder with adb files)
    4. Execute
    Code:
    adb shell
    You should see an invitation with "$"
    5. Execute
    Code:
    su
    confirm on the clock. If suddenly not confirmed, and left Permission denied, find in Magisk Manager and confirm manually.
    6. Execute
    Code:
    cp /data/data/com.google.android.gms/databases/dg.db /mnt/sdcard
    copy the database to where the file can be easily copied to the PC
    7. Open an additional cmd window (in ADB folder)
    Execute
    Code:
    adb pull /mnt/sdcard/dg.db
    The database will be copied to the PC in the current directory
    8. In the same terminal window run
    Code:
    sqlite3.exe dg.db
    you will be prompted with ">"
    9. Execute
    Code:
    update main set c = 0 where a like 'attest%';
    Change the value of the 3rd column ("c") to 0 if the first ("a") starts with attest
    10. Exit sqlite (press Ctrl-D)
    11. Push the file back on the clock
    Code:
    adb push dg.db /mnt/sdcard
    12. Select the first open window with "adb shell"
    Code:
    cp /mnt/sdcard /data/data/com.google.android.gms/databases/dg.db
    13. Changing access rules
    Code:
    chmod 440 /data/data/com.google.android.gms/databases/dg.db
    Go to Gpay on your watch and add your credit card
    12
    Review of the current version of the ROM

    I've asked a number of questions about user experience with the ROM and I feel a responsibility to give back to this community with my experience installing and using the ROM. I have the 512M version of the Ticwatch Pro. I give details of my usage so you can see my use case (feel free to skip any of it).

    Before changing to this ROM I made a number of adjustments to the watch using the stock ROM:
    1. I turned on Always On Display (AOD)
    2. I turned off Raise to Wake
    3. I disabled all of the Tic Exercise / Ticwatch apps available in the applications settings menu.
    4. I used adb to disable ticsystem.
    5. I used the developer settings to turn off all of the animations

    Having done this I was actually rather satisfied with performance for the most used functions (swiping for: notifications, tiles, google, settings, etc.). I was not satisfied when switching to an app, going to and changing settings on a watch face and so on. I also felt that I was not always getting notifications as quickly as I should.

    I did find, though, that I had rather good battery performance. I recharge every night. Also, I exercise first thing in the morning and I put the watch back on the charger during my shower. I occasionally take a walk during the day and don't put the watch back on the charger, although I do track the walk. Overall I usually went to bed with 30-40% power left.

    I've been following the forum closely and decided to install the ROM a bit over a week ago. My biggest concern was being able to backup and restore (I always take a TWRP backup of a phone before installing a ROM). I never felt I had a clear picture on the correct way to backup the watch. I tried doing an adb backup of each of the partitions that I saw in the stock ROM posted to this forum (each of the .img files) which was slightly older than what was on my watch. I found the size I pulled was rather different than in the zip file so I assume I did it incorrectly. At that point I decided to just take the plunge and hope that if things went west the stock image I had would work and the watch would update itself the my current level.

    I performed the install exactly as described in the "steps.txt" file. All went as expected and the watch booted up fine the first time. I then took the time to reinstall my apps and watch faces. I then made the same changes described above (except I didn't have to disable ticsystem). Here are my observations having used the ROM for over a week:
    1. The watch now performs as I had hoped it would. All the normal swipes and app changes are smooth. You do need to keep your expectations in mind. If you open an app on your phone it doesn't start "instantaneously." You can't expect better than that on a watch, but on the watch the apps open and come to life quickly and a lot better than stock.
    2. The one caveat to the performance observation is that when notifications are coming in (particularly a large set in the morning) and you are working with the watch at the same time, things can stutter and swiping and clicking can happen in the wrong places. An overwhelming of the multitasking, I guess.
    3. Battery life is still good. About the same as I was getting with stock or perhaps just a bit less. That may be because I'm still tweaking things and trying new watch faces. I certainly have 20-30% left and often up to 40%.
    4. The ROM has been totally stable. Absolutely no crashes or restarts
    5. Installation recommendations - for JanJan
      • Provide a good guide to backing up the stock ROM - preferably in steps.txt
      • I knew that the bootloader had to be unlocked but this should be in the steps
      • I knew that you had to get into fastboot before running 2-flash-windows.bat. That process should be in steps.
      • My fault - but I had problems getting Google Pay working (I know it now works well enough to accept the card - haven't tried to make a payment yet). I made too many changes to try and fix it to pinpoint the exact problem but I believe the problem was that I left the watch in ADB debug when I tried to set it up. EDIT: While the card is accepted, I CAN'T pay with it.
    6. To users
      • Be very patient. Give the watch and the ROM a number of days (or a week) to let things settle down. It gets much better.
      • I still recommend disabling animations and Tic Exercise - the watch just seems snappier
      • Send JanJan a donation - cheers!
    Sorry for the length of this but I wanted to give as clear a picture as I could. I would really appreciate any comments or corrections to what I have written.