适用于 Windows Vista+ 的 ADB 和 Fastboot 驱动
内付一键安装脚本

注意：
索尼和三星设备的驱动并不包含，他们搞特殊
安装时询问是否 信任/安装 需要手动点一下 确认/安装/信任（我也不知道为什么有些驱动不签名

====

ADB and Fastboot Driver For Windows Vista+
There is a script inside for easy installation

Attention:
Drivers for Sony and Samsung devices are not included, they are special
When installing, it asks whether to trust/install and you need to manually click Confirm/Install/Trust (I don't know why some drivers are not signed)

log抓取模块
要求Magisk 20.4+
同时支持抓取内核日志
默认保存在/cache/bootlog
cache分区不存在就保存到/data/local/bootlog
解锁设备且未检测到/data/local/logcatcher/boot.lcs时会打包到/sdcard/Download/bootlog-**.tar.gz
如果你想在进入系统后不停止抓取，你可以创建/data/local/logcatcher/boot.lcs文件
2026年2月6日更新：
支持读取Magisk以外的比如KernelSU的版本号
支持抓取完整内核日志而不是仅仅dmesg
如果解锁后不停止抓取日志也支持保留上次启动的旧日志
在抓取日志时如果logd重启会自动恢复日志抓取
A Magisk module that can help you save the log
required Magisk 20.4+
The log is saved to /cache/bootlog by default
If /cache does not exist, save to /data/local/bootlog
If you don't want to stop logcat after boot completed, you can create an empty file /data/local/logcatcher/boot.lcs
When the system boot normally and /data/local/logcatcher/boot.lcs is not detected, the logs will be packaged to /sdcard/Download
2026/2/6 updates:
Add support for reading versions from non-Magisk roots like KernelSU.
Capture full kernel logs (not just dmesg).
Preserve previous boot logs when log capture continues after unlock.
Auto-recover log capture if logd restarts.
Source Code

ADB 抓取日志小工具

1、USB调试怎么开自己搜索，如果卡在 wait for device 请检查数据线连接和驱动

2、在能开机的时候运行 su.bat 确保授权（注意手机上的权限申请弹窗，对于KernelSU请到管理器为Shell授权）
返回OK就是成功了

3、在开机第一屏出现厂商 logo 时运行 logcat.bat
两个窗口会出现
一个抓取系统日志，另一个是内核日志

4、复现问题并获取到log后，可以直接拔数据线，中止抓取日志，然后打包 log 文件夹上传

-----

1. Make sure the ADB driver is installed and USB debug mode is turned on
The answer to how to use ADB can be found on Google.

2. run su.bat when you can normally boot into the system to ensure that the authorization is successful (Watch for the permission request pop-up on your phone screen, for KernelSU please grant root to shell using manager.)
When it says OK is successful.

3. Run logcat.bat when the manufacturer logo appears on the first screen
Two windows will appear.
Catching system logs. AND Catching kmsg.

4. Please go to the folder named log , package it into an zip archive, then upload.

Source
Recent Updates:
- Updated to SQLite 3.35.5.
- Updated for Magisk v20.4 template format.

This module allows you to disable the Magisk module if the data partition cannot be decrypted and cannot be restored to normal by entering Safe Mode.

---

## How To Use

Create a file named disable_all_modules in /data/unencrypted or /cache to disable all modules.

If the system is successfully booted and the screen is unlocked properly these two files are automatically deleted to prevent all modules from being disabled each time the system is booted.

Create a file named disable.list in /data/unencrypted or /cache and write module ids (one module per line) in it to disable specific modules.

Tips: The module id is the name of the module's directory

Example: The module id of Log-Catcher is hwr_logcat

https://github.com/yujincheng08/unlock-cn-gms/
LoveSy: Add support to Q and R
Howard:
Detect file location directly
Prevent the Play Store from failing to get the list of installed apps

解除多用户数量限制

The public link to this channel @hzrtools has been removed by Telegram
new link
new channel name @hwrtools

Fix for MIUI 14 and ColorOS

Fix for ColorOS 13 in 1+11

https://github.com/Howard20181/unlock-cn-gms/releases/tag/v6.1
Compatible with KernelSU
Proper use of the REMOVE marker

Enable GNSS time detection for Android 12+

为 Android 12 及以上设备启用 GNSS 时间源

Q&A:

Q: Do I need this module?
A: The AOSP default clock source is to prioritize from the NTP server, while the Carrier Network Time is used as a secondary clock source. GNSS is supported as a clock source starting with Android 12, but is not enabled by default.
It is recommended to install this module if you care about time accuracy and your location is not connected to AOSP's default NTP server. AOSP's default NTP server is time.android.com, android.com domain is not reachable in some regions (adb shell settings put global ntp_server pool.ntp.org should fix this) and thus cannot synchronize the time. If the NTP time cannot be synchronized and the time cannot be obtained from the carrier's network (For example, using a cell phone without inserting a SIM card), the device's clock will be incorrect.

Q: How do I verify that the GNSS clock source is enabled?
Check the result of the command
adb shell cmd time_detector dump

The GNSS time source is enabled if the result is as follows:

TimeDetectorStrategy:
mCurrentConfigurationInternal=ConfigurationInternal{...mOriginPriorities=[network,telephony,gnss]...}...
.
.
.
Gnss suggestion history:
....

GNSS time synchronization history can be viewed from Gnss suggestion history

Q: When gnss time update service suggest a GNSS time?
A: GNSS time will be passively update when another app or service in the system requesting location updates.

Q: How to force update NTP time?
A: adb shell cmd network_time_update_service force_refresh

Update: Fix Installation in Magisk App

CRC64: 2641787DC0C0AA02

Change GNSS time priority to the first

翻新模块 https://t.iss.one/BDovo_Channel/5316
移植国际版系统的 eSIM 管理到国内版
更新 LPA 到 3.0.0
可能仅支持 HyperOS 2.0，所以仅允许 Android 15 安装（假定有 HyperOS 2.0 且国际版支持 eSIM 的设备已经是 Android 15）

Module updated.

Because of the character limit, many separators have been removed, so while it looks like there are many characters, it's actually less than before. This is because I previously had Telegram Premium, but I don't have it anymore, which reduced the character limit.