Merged
Conversation
Contributor
Reviewer's GuideAdds a new blog post about tinkering with a Ticwatch Pro 3 Ultra, along with all referenced images for the article. Flow diagram for upgrading Ticwatch Pro 3 Ultra to WearOS 3 as described in the postgraph TD
A_Start[Start: Have_Ticwatch_Pro_3_Ultra_on_chinese_firmware] --> B_Check_model[Check_model_and_firmware_version]
B_Check_model --> C_Is_Ultra{Is_device_Ticwatch_Pro_3_Ultra?}
C_Is_Ultra -->|No| Z_EndStop[Stop: Do_not_follow_this_flow]
C_Is_Ultra -->|Yes| D_Flash_PMRA[Flash_firmware_version_PMRB_220703_001]
D_Flash_PMRA --> E_Unlock_bootloader[Unlock_bootloader_via_fastboot_oem_unlock]
E_Unlock_bootloader --> F_Boot_system_once[Boot_system_once_to_confirm_version]
F_Boot_system_once --> G_Flash_system_img[Flash_system_img_from_231020_package]
G_Flash_system_img --> H_Lock_bootloader[Lock_bootloader_via_fastboot_oem_lock]
H_Lock_bootloader --> I_Boot_to_recovery[Boot_to_recovery_after_factory_reset]
I_Boot_to_recovery --> J_Mount_system[Select_Mount_system_in_recovery]
J_Mount_system --> K_Apply_update_via_adb[Select_Apply_Update_via_ADB]
K_Apply_update_via_adb --> L_Sideload_update[adb_sideload_WearOS3_update_zip]
L_Sideload_update --> M_Update_progress{Install_successful?}
M_Update_progress -->|No| Y_Troubleshoot[Troubleshoot_firmware_and_retry]
Y_Troubleshoot --> D_Flash_PMRA
M_Update_progress -->|Yes| N_Reboot_system[Reboot_to_system]
N_Reboot_system --> O_Run_WearOS3[WearOS3_running_on_watch]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
✅ 构建检查完全通过！
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Hey - I've found 4 issues, and left some high level feedback:
- The link placeholder
[bugjaeger的界面]()currently has an empty URL and renders as a broken link; either fill in the correct target or remove the link formatting. - Several image files (e.g. the
.jfif,.png, and non-_compressedvariants) are not referenced in the post; consider removing unused assets to keep the repo size smaller and avoid confusion about which versions are intended for use.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The link placeholder `[bugjaeger的界面]()` currently has an empty URL and renders as a broken link; either fill in the correct target or remove the link formatting.
- Several image files (e.g. the `.jfif`, `.png`, and non-`_compressed` variants) are not referenced in the post; consider removing unused assets to keep the repo size smaller and avoid confusion about which versions are intended for use.
## Individual Comments
### Comment 1
<location path="source/_posts/ticwatch-ruby-fishy.md" line_range="51-53" />
<code_context>
+
+熬过下午的大水课之后回宿舍给表充电...
+
+从四点充到八点，就冲进去40%。好嘛，我adb一看，就25毫安的电流。
+
+```
</code_context>
<issue_to_address>
**nitpick (typo):** “冲/充”用字和中英文间空格可能是小笔误
前面是“从四点充到八点”，后面建议统一改成“就充进去40%”。另外“我adb一看”里，建议改为“我 adb 一看”，在“我”和“adb”之间加一个空格。
```suggestion
熬过下午的大水课之后回宿舍给表充电...
从四点充到八点，就充进去40%。好嘛，我 adb 一看，就25毫安的电流。
```
</issue_to_address>
### Comment 2
<location path="source/_posts/ticwatch-ruby-fishy.md" line_range="74-75" />
<code_context>
+```
+
+卖家送的什么垃圾线。被迫下单等新数据线。
+今晚只能放着冲了。淦。
+
+## 怎么还有第二关？
</code_context>
<issue_to_address>
**suggestion (typo):** “冲了”疑似应为“充了”
从上下文看这里在描述给表充电，“放着冲了”应为“放着充了”，建议改成“充”。
```suggestion
卖家送的什么垃圾线。被迫下单等新数据线。
今晚只能放着充了。淦。
```
</issue_to_address>
### Comment 3
<location path="source/_posts/ticwatch-ruby-fishy.md" line_range="173" />
<code_context>
+
+## 怎么这么卡
+
+一般来说，只要手机保持网络畅通，手表蓝牙连接的手机，手表的网络也是通的，不需要特地留学。
+
+但是，在我这，即使网络通畅， Google 地图也偏移到姥姥家了，钱包也没啥用，我也不需要talkback和小问关怀
</code_context>
<issue_to_address>
**issue (typo):** “留学”应为“留心/留意”等，属于错字
这里“留学”语义不通，应是输入法误选。建议改为更贴切的词，如“留心”或“留意”。
```suggestion
一般来说，只要手机保持网络畅通，手表蓝牙连接的手机，手表的网络也是通的，不需要特地留心。
```
</issue_to_address>
### Comment 4
<location path="source/_posts/ticwatch-ruby-fishy.md" line_range="125" />
<code_context>
+
+事实证明Gemini不开思考模型纯⑨，没话讲。
+
+把[4pda上关于这块表的讨论](https://4pda.to/forum/index.php?showtopic=1005330)发给Codex并给它装上playwright（虽然应该用来调试浏览器，不过怎么用不是用是吧🤧），帮它过掉人机验证然后登录论坛账号让它搜索关键词（毕竟我不懂俄语），codex找到了这么一个解决方案：
+
+遵照[这篇XDA帖子](https://xdaforums.com/t/guide-ticwatch-pro-3-gps-wearos-3-5-for-open-bootloader.4647312/post-89364621)，但是如果是Ticwatch Pro 3 Ultra，可以跳过3-7步，总的来说，你要：
</code_context>
<issue_to_address>
**nitpick (typo):** Codex/Playwright 等专有名词大小写不一致
此处建议将“playwright”改为“Playwright”，并统一前后都使用“Codex”，以保持专有名词大小写一致，便于阅读。
```suggestion
把[4pda上关于这块表的讨论](https://4pda.to/forum/index.php?showtopic=1005330)发给Codex并给它装上Playwright（虽然应该用来调试浏览器，不过怎么用不是用是吧🤧），帮它过掉人机验证然后登录论坛账号让它搜索关键词（毕竟我不懂俄语），Codex找到了这么一个解决方案：
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Comment on lines
+51
to
+53
| 熬过下午的大水课之后回宿舍给表充电... | ||
|
|
||
| 从四点充到八点，就冲进去40%。好嘛，我adb一看，就25毫安的电流。 |
Contributor
There was a problem hiding this comment.
nitpick (typo): “冲/充”用字和中英文间空格可能是小笔误
前面是“从四点充到八点”，后面建议统一改成“就充进去40%”。另外“我adb一看”里，建议改为“我 adb 一看”，在“我”和“adb”之间加一个空格。
Suggested change
| 熬过下午的大水课之后回宿舍给表充电... | |
| 从四点充到八点，就冲进去40%。好嘛，我adb一看，就25毫安的电流。 | |
| 熬过下午的大水课之后回宿舍给表充电... | |
| 从四点充到八点，就充进去40%。好嘛，我 adb 一看，就25毫安的电流。 |
Comment on lines
+74
to
+75
| 卖家送的什么垃圾线。被迫下单等新数据线。 | ||
| 今晚只能放着冲了。淦。 |
Contributor
There was a problem hiding this comment.
suggestion (typo): “冲了”疑似应为“充了”
从上下文看这里在描述给表充电，“放着冲了”应为“放着充了”，建议改成“充”。
Suggested change
| 卖家送的什么垃圾线。被迫下单等新数据线。 | |
| 今晚只能放着冲了。淦。 | |
| 卖家送的什么垃圾线。被迫下单等新数据线。 | |
| 今晚只能放着充了。淦。 |
|
|
||
| ## 怎么这么卡 | ||
|
|
||
| 一般来说，只要手机保持网络畅通，手表蓝牙连接的手机，手表的网络也是通的，不需要特地留学。 |
Contributor
There was a problem hiding this comment.
issue (typo): “留学”应为“留心/留意”等，属于错字
这里“留学”语义不通，应是输入法误选。建议改为更贴切的词，如“留心”或“留意”。
Suggested change
| 一般来说，只要手机保持网络畅通，手表蓝牙连接的手机，手表的网络也是通的，不需要特地留学。 | |
| 一般来说，只要手机保持网络畅通，手表蓝牙连接的手机，手表的网络也是通的，不需要特地留心。 |
|
|
||
| 事实证明Gemini不开思考模型纯⑨，没话讲。 | ||
|
|
||
| 把[4pda上关于这块表的讨论](https://4pda.to/forum/index.php?showtopic=1005330)发给Codex并给它装上playwright（虽然应该用来调试浏览器，不过怎么用不是用是吧🤧），帮它过掉人机验证然后登录论坛账号让它搜索关键词（毕竟我不懂俄语），codex找到了这么一个解决方案： |
Contributor
There was a problem hiding this comment.
nitpick (typo): Codex/Playwright 等专有名词大小写不一致
此处建议将“playwright”改为“Playwright”，并统一前后都使用“Codex”，以保持专有名词大小写一致，便于阅读。
Suggested change
| 把[4pda上关于这块表的讨论](https://4pda.to/forum/index.php?showtopic=1005330)发给Codex并给它装上playwright（虽然应该用来调试浏览器，不过怎么用不是用是吧🤧），帮它过掉人机验证然后登录论坛账号让它搜索关键词（毕竟我不懂俄语），codex找到了这么一个解决方案： | |
| 把[4pda上关于这块表的讨论](https://4pda.to/forum/index.php?showtopic=1005330)发给Codex并给它装上Playwright（虽然应该用来调试浏览器，不过怎么用不是用是吧🤧），帮它过掉人机验证然后登录论坛账号让它搜索关键词（毕竟我不懂俄语），Codex找到了这么一个解决方案： |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated submission from editor.
Files:
Summary by Sourcery
Add a new blog post about hacking and upgrading a Ticwatch Pro 3 Ultra smartwatch, including its troubleshooting journey and custom tooling.
New Features:
Documentation: