Would you install TWRP and Magisk if you could?


  • Total voters
    128
Search This thread

bernarbernuli

Senior Member
Aug 26, 2010
201
432
Vigo
www.htcmania.com

Hi, I have printed your 3D design, congratulations, it looks great but the Ticwatch pro Charging and Data Cable does not work on Ticwatch Pro 3.

I have disassembled the TWP charger as seen in the screenshot, when I connect it to my TWP3 it does nothing, it does not charge. I tested with a voltmeter and indeed the outer 2 of the 4 have current, I do not know if this charger requires more voltage.

Can you tell me if something is missing?



IMG20220409214132.jpg
 

Attachments

  • IMG20220409214041.jpg
    IMG20220409214041.jpg
    1.3 MB · Views: 69

yesimxev

Senior Member
May 8, 2017
313
142
Hi, I have printed your 3D design, congratulations, it looks great but the Ticwatch pro Charging and Data Cable does not work on Ticwatch Pro 3.

I have disassembled the TWP charger as seen in the screenshot, when I connect it to my TWP3 it does nothing, it does not charge. I tested with a voltmeter and indeed the outer 2 of the 4 have current, I do not know if this charger requires more voltage.

Can you tell me if something is missing?



View attachment 5586381
Not sure about the cable version. I'm using the data dock pcb version. You didn't attach a pic of the pro3 printed dock. Does the pins come out enough so they reach the pro3's pins? Also make sure your board is fixed with a screw, so it won't be pushed down and lose contact
 

bernarbernuli

Senior Member
Aug 26, 2010
201
432
Vigo
www.htcmania.com
Not sure about the cable version. I'm using the data dock pcb version. You didn't attach a pic of the pro3 printed dock. Does the pins come out enough so they reach the pro3's pins? Also make sure your board is fixed with a screw, so it won't be pushed down and lose contact
Thanks for your answer, I think that the 3D printed case is not determinant for charging the watch because I put the cable with the pins touching the watch contacts with my hand but even though the 4 pins are touching the watch contacts it does not charge or detect the watch. I bought the charger on Amazon, I think it is the official charger or at least it looks very similar, long ago owned this watch and I recognize it.

 

yesimxev

Senior Member
May 8, 2017
313
142
Thanks for your answer, I think that the 3D printed case is not determinant for charging the watch because I put the cable with the pins touching the watch contacts with my hand but even though the 4 pins are touching the watch contacts it does not charge or detect the watch. I bought the charger on Amazon, I think it is the official charger or at least it looks very similar, long ago owned this watch and I recognize it.

That should work. You didn't confirm, is that little board fixed with screw to the new 3d case? Also, do you use the magnets? I noticed that the connection only works if there's a balanced contact. And when I also tried to put the board to mine with hand, it didn't work when I fully pushed in for "maximun contact"
 

bernarbernuli

Senior Member
Aug 26, 2010
201
432
Vigo
www.htcmania.com
That should work. You didn't confirm, is that little board fixed with screw to the new 3d case? Also, do you use the magnets? I noticed that the connection only works if there's a balanced contact. And when I also tried to put the board to mine with hand, it didn't work when I fully pushed in for "maximun contact"

I don't understand why it doesn't work for me, what does balanced contact mean?


I have put the magnets with the same disposition of the original case in the 3D printed case as you can see in the first capture, on the right is the original case and on the left in the 3D print, I printed it at low quality, however the 4 holes for the pins were well printed, and the pins are well introduced as you can see in the 2nd capture.

Furthermore, I am also trying it by hand as seen in the third capture, but it does not respond, as I said in previous post, I have tested with a voltmeter if there is electric current and in the 2 pins at the ends (V- and V+) gives me that there is electric current.


IMG20220417175849.jpg


IMG20220417175712.jpg



IMG20220417182756.jpg
 

yesimxev

Senior Member
May 8, 2017
313
142
Seems almost done. I mean balanced that the contact is straight. To get that, screw the board to the dock so it will be fixed. And use magnets on both side. Btw does the cable work with TWP if you put back now?
 

bernarbernuli

Senior Member
Aug 26, 2010
201
432
Vigo
www.htcmania.com
Seems almost done. I mean balanced that the contact is straight. To get that, screw the board to the dock so it will be fixed. And use magnets on both side. Btw does the cable work with TWP if you put back now?

I don't have a Ticwatch Pro watch to check that the cable is working properly, the current flows through it, that's for sure.

I think the charger I bought on amazon from TUSITA brand (must be a clone) does not allow to screw into the plate, if you look at the first screenshot of post #89. The plate has 3 holes that are inserted into three posts of the original case so that the pins are inserted completely straight through its 4 hole. I think that plate is not suitable for screwing into your printed case, because I think it has a different hole layout than the charger you recommend from Aliexpress.
 
  • Like
Reactions: yesimxev

yesimxev

Senior Member
May 8, 2017
313
142
Ah yes not sure why I thought you have a Pro. I see, best to find a way to at least underlay it so if you print and put the backplate on, it will hold it's back so the pins won't push away when the watch is on
 

tarattata

Senior Member
Feb 17, 2009
105
18
hi guys, can i install this recovery on my watch? it is a ticwatch pro 3 ultra lte. having problems with my manager that i cannot modify apn having root would be the only solution. thank you
 

Attachments

  • 20220507_191411.jpg
    20220507_191411.jpg
    1.2 MB · Views: 56
  • 20220507_191431.jpg
    20220507_191431.jpg
    3.1 MB · Views: 57

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hello all. Is anyone able to provide the stock ROM for the TWP3 Ultra LTE (Rover) version please?

    Thanks ever so much!
    1
    I can't use adb bluetooth and fastboot because i don't have câble with 4 pins... I test with another old câble but too difficult even i dont use magnet do you know where i could buy à good câble ?
    You need to build your own
    cable-casero.jpg
  • 18
    Hi all, I've just got my hands on a TicWatch Pro 3 and am keen to mod it.
    As far as I can tell, there've been no kernels or recoveries built for it yet. I'd like to fix that.
    This will be my first time bringing up TWRP (I have experience with building AOSP and porting Ubuntu Touch and PostmarketOS).

    If anyone else is interested in helping with this stuff, feel free to join in! It'd be great if we can build a bit of a community around this.

    My plan of action is as follows:
    1. Boot TWRP or obtain temporary root access in another way. Some kernel sources are available.
    2. Extract images of every partition on the device (excluding userdata) so we have a way to restore everything if anything goes wrong,
    3. Properly port TWRP to the device. This may be difficult; I don't think TWRP has run on the SDM429W before, though it's based off the SDM429. The Nokia 3.2 may be a useful reference.
    4. Root the device with Magisk, and document the process so users can do it.
    5. Build a custom kernel. To be honest, I'm not sure if this device needs one, but @janjan managed to squeeze amazing performance out of the OG TWP by tweaking a few things and disabling junk.
    Here's some useful information to get started:
    • The TWP3 ships with a charging cable that only has power wires. It's possible to use an old TWP dock to get a data connection, though, and the bootloader can be unlocked through fastboot. See this thread for more info. The USB wire layout is not in the regular order (D+ and D- are swapped), so if you don't have an old dock and are using wires, refer to the pictures here.
    • The TWP3 LTE kernel source code is available here. I've also forked it here, in case anything happens to the original repo. As far as I can tell, there are no sources for the GPS model, but the kernel version in the repo (4.9.232) matches my GPS model's kernel version. I expect the LTE kernel can be used on the GPS with minimal effort.
    • The rubyfish kernel configuration is available through /proc. It's attached to this post.
    I'm not sure if unlocking the bootloader blocks OTA updates; if it does, perhaps we should work out a way to manually download OTA updates before unlocking the bootloader.

    Here's some miscellaneous information:
    • The TWP3 LTE is codenamed "rover", and the TWP3 GPS is codenamed "rubyfish".
    • As far as I can tell, the Snapdragon Wear 4100 in this device is a 64-bit SoC, but a 32-bit OS is in use.
    • Here's the complete kernel version string on my rubyfish running the latest OTA update: Linux version 4.9.232-perf+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Jun 9 09:55:19 CST 2021
    9
    Hey everyone,
    For those who want to root their TWP3 with Magisk, here is how to do:

    1- Make your own cable that supports data transfer
    2 - Unlock your bootloader:
    -Enable adb debugging by going to "Settings>System>About" and press build number 7 times then go back 2 times then go to "Developpers options>ADB debugging"
    - Reboot to bootloader by pressing the 2 buttons until you see fastboot mode
    - Connect the watch to your computer
    - Type fastboot oem unlock in a command prompt (you need to have adb and fastboot installed)
    - Confirm on your watch
    3 - Download one of the image for your watch
    4 - Flash it on your watch in fastboot mode:
    - Type fastboot flash recovery magisk_recovery_model.img in a command prompt (replace
    model with your version of TWP3)
    - Boot recovery via the fastboot mode
    9
    OneOS WearOS

    21.10.3 Changelo
    ---FIRST PREVIEW VERSION--
    -Added ONE Bootanimatio
    -Tweaks to system/etc/prop.defaul
    -Tweaks to system/build.pro
    -Moved some apps to data-app
    -Removed the deletion of Custom Recover
    -Deodexed
    7
    I think the project is fantastic, the truth is that Mobvoi totally succeeded in minimizing attempts to root the watch, simply sold the watch with a cable that only serves to charge, and also there is none for sale (not even in the Asian market), you can only make one by hand, which pushes back 99.9% of users.

    For those who don't know, the cable is mandatory, because to flash TWRP or root you must first unlock bootloader. Unlocking bootloader is done in bootloader mode (fastboot) and there will not work debugging via Wi-Fi, as the watch in this mode does not connect to the Wi-Fi network, it will only work with a USB cable.

    Anyway, I want to contribute the info I have on the subject:

    - Last May the user @mind-overflow was trying to port TWRP, I do not know if he has managed to advance something. Since May i do not know anything. Here the last thing he talked about it.

    - Here, at the end of that post I explain how to make a handmade cable from a Ticwatch S/E cable.
    Use "fastboot boot rubyfish_recovery.img"
    Without "" obviusly

    Actually it's untested
    Edit: i see u from Spain, Send me pv if u have Telegram ;)

    Edit2: for upload the Rover variant


    Rubyfish = BT + GPS Ticwatch Pro 3
    Rover = LTE Ticwatch Pro 3
    4
    I've made a full eMMC dump. I've uploaded every partition that doesn't contain sensitive info.
    Excluded partitions in my upload are: cache, DDR, mcfg, persist, tz, userdata.
    I'll publish a guide on how to do this yourself soon. Everyone should back up their own persist partitions as they contain sensor calibration data.

    Download the images here: https://androidfilehost.com/?fid=7161016148664816932

    Here's a complete partition list:

    Code:
    # lsblk -o name,partlabel,fstype,size,uuid /dev/loop1
    
    NAME       PARTLABEL    FSTYPE  SIZE UUID
    loop1                           7.1G
    ├─loop1p1  modem        vfat     84M 00BC-614E
    ├─loop1p2  fsc                    1K
    ├─loop1p3  ssd                    8K
    ├─loop1p4  sbl1                 512K
    ├─loop1p5  sbl1bak              512K
    ├─loop1p6  rpm                  512K
    ├─loop1p7  rpmbak               512K
    ├─loop1p8  tz                     2M
    ├─loop1p9  tzbak                  2M
    ├─loop1p10 devcfg               256K
    ├─loop1p11 devcfgbak            256K
    ├─loop1p12 dsp          ext4     16M af32c008-2a39-7e5b-a5dc-201456d93103
    ├─loop1p13 dspbak       ext4     16M af32c008-2a39-7e5b-a5dc-201456d93103
    ├─loop1p14 modemst1             1.5M
    ├─loop1p15 modemst2             1.5M
    ├─loop1p16 DDR                   32K
    ├─loop1p17 fsg                  1.5M
    ├─loop1p18 sec                   16K
    ├─loop1p19 splash                11M
    ├─loop1p20 aboot                  1M
    ├─loop1p21 abootbak               1M
    ├─loop1p22 dtbo                   8M
    ├─loop1p23 dtbobak                8M
    ├─loop1p24 vbmeta                64K
    ├─loop1p25 vbmetabak             64K
    ├─loop1p26 boot                  32M
    ├─loop1p27 recovery              32M
    ├─loop1p28 devinfo                1M
    ├─loop1p29 system       ext4    1.5G c8d4c976-2cc7-553b-8c90-9810db1915c1
    ├─loop1p30 vendor       ext4    512M 38ba1d68-5883-5923-afce-5094c89a2e99
    ├─loop1p31 cmnlib                 1M
    ├─loop1p32 cmnlibbak              1M
    ├─loop1p33 cmnlib64               1M
    ├─loop1p34 cmnlib64bak            1M
    ├─loop1p35 keymaster              1M
    ├─loop1p36 keymasterbak           1M
    ├─loop1p37 cache        ext4     64M 8a2a63b8-6101-4879-b3d7-3af37090d3f5
    ├─loop1p38 persist      ext4     32M 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
    ├─loop1p39 misc                   1M
    ├─loop1p40 keystore             512K
    ├─loop1p41 config                32K
    ├─loop1p42 oem          ext4     16M c46af7c8-7768-44bf-87e7-4e9e489cba6e
    ├─loop1p43 limits                32K
    ├─loop1p44 dip                    1M
    ├─loop1p45 mdtp                  32M
    ├─loop1p46 mdtpbak               32M
    ├─loop1p47 mcfg                   4M
    ├─loop1p48 apdp                 256K
    ├─loop1p49 msadp                256K
    ├─loop1p50 dpo                    8K
    ├─loop1p51 btlver                 1K
    └─loop1p52 userdata     f2fs    4.7G adee6f87-7155-465d-b933-c85ed3f0c47c

    8GB flash with 4.7GB userdata... Good job Mobvoi