I'm not sure how this replies to my question but.. are you saying flashing this ends up in brick?!
TicWatch Pro 3 development
- Thread starter theOriginalSuperl2
- Start date
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?
Attachments
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.
TUSITA Cargador Compatible con TicWatch Pro, Ticwatch Pro 2020, TicWatch Pro 4G/LTE Smartwatch - Cable de carga USB Clip Cradle 3,3ft 100cm - Accesorios para Reloj Bluetooth : Amazon.es: Electrónica
Compra online TUSITA Cargador Compatible con TicWatch Pro, Ticwatch Pro 2020, TicWatch Pro 4G/LTE Smartwatch - Cable de carga USB Clip Cradle 3,3ft 100cm - Accesorios para Reloj Bluetooth. Envío en 1 día GRATIS con Amazon Prime.
www.amazon.es
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.
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.
Hi, ultra lte uses the same as normal lte so it's rover. Instructions and twrp zip found here https://wear.revtechs.me/en/help
Hi there. Did you successfully flash this oneOS on pro3 ultra LTE (aka rover)? I'v tried twice and all end up in bootloop & stuck in bootloader.
Hi. Did you successfully root by flashing magisk on pro3 ultra LTE (aka rover)? I'v tried twice and all end up in bootloop & stuck in bootloader.
Last edited:
Stock OS could be good as well as I did on that firs. But definitely needed a step to disable vbmeta verification on their help page.
Disable vbmeta verification (download vbmeta): "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
We'll get the stock rom soonIn my version, Ticwatch pro 3 Ultra, it is not possible change the second screen background color ... Most functions are the same but there are some differences... If some one have my watch version, it will be great have the properly ROM
3
I've just gone through the steps. Yes, disabler is needed on /sdcard, so I'll update the guide. Otherwise, I've got a clean boot straightaway with Magisk. Is your watch GPS/LTE/Ultra GPS/LTE?Hello, thanks for the update
On my side I've followed exactly your article exactly how you explained it,
About the verification I've done the command :
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" and all says OKAY
(This one I was struggling because it was copying "–disable-verity" from the article instead of "--disable-verity")
After Sideload :
- OS : Ok
- Mobvoi Package : Ok
- Magisk : Ok
- Disabler : Not working with sideload (Volume Button Error ?)
Only working from local zip install but get infinite loop
( I've done everything at least 10 times and waited a lot to see if it was booting but never booted )
Right now, I've simply installed the OS + Mobvoi Package to get back to normal waiting if there's any idea behind this step, I see a lot of people struggling too on this step, like col_forbin did too
Let me know if you need me to test anything else if it can help other people in the future, but after +50 tries in 48hours I'll take a break
Thanks a lot for all the help
Cheers3
You're welcome! Adding the instructions to flash NH to xda tonight, in case support is needed
32
No worries, I'll add the manual disable encryption-dm step tonight. Seems that zip is causing issues. Also need to run a fresh install with the latest zip next week or so
-
18Hi 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:
- Boot TWRP or obtain temporary root access in another way. Some kernel sources are available.
- Extract images of every partition on the device (excluding userdata) so we have a way to restore everything if anything goes wrong,
- 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.
- Root the device with Magisk, and document the process so users can do it.
- 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.
- 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.
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
9Hey 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
- Typefastboot oem unlockin 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:
- Typefastboot flash recovery magisk_recovery_model.imgin a command prompt (replace
model with your version of TWP3)
- Boot recovery via the fastboot mode7
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 34I'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
