[{"data":1,"prerenderedAt":980},["ShallowReactive",2],{"post-/2026/20260320-1":3,"surround-/2026/20260320-1":969},{"id":4,"title":5,"body":6,"categories":938,"date":940,"description":941,"draft":942,"extension":943,"image":944,"meta":945,"navigation":947,"path":948,"permalink":949,"podcastAudio":950,"podcastLyric":951,"podcastTitle":952,"published":949,"readingTime":953,"recommend":907,"references":949,"seo":958,"sitemap":959,"stem":960,"tags":961,"type":967,"updated":940,"__hash__":968},"content/posts/2026/20260320-1.md","高通平台免解 BL 临时 Root 实战",{"type":7,"value":8,"toc":906},"minimark",[9,14,34,47,84,88,91,127,130,133,140,146,151,154,157,182,185,198,201,204,319,330,334,340,344,347,352,355,383,387,427,432,439,443,453,457,477,481,491,498,502,505,509,523,527,531,534,541,544,548,552,555,589,595,599,605,609,619,631,635,639,670,674,678,685,688,703,707,710,741,745,757,760,786,795,826,835,838,841,861,867,870,873],[10,11,13],"h1",{"id":12},"高通平台免解-bl-临时-root-实战以-redmi-k70-pro-为例","高通平台免解 BL 临时 Root 实战：以 Redmi K70 Pro 为例",[15,16,17],"blockquote",{},[18,19,20,21,25,26,29,30,33],"p",{},"本文以 ",[22,23,24],"code",{"code":24},"Redmi K70 Pro"," 为示例机型，记录一次基于 ",[22,27,28],{"code":28},"KernelSU"," 的临时 Root 实操流程，并进一步完成 ",[22,31,32],{"code":32},"LSPosed"," 的安装。全文以“能复现、能排错、能直接上手”为目标进行整理，适合作为个人备忘和入门参考。",[35,36,39],"alert",{"title":37,"type":38},"风险提示","warning",[18,40,41,42,46],{},"Root、SELinux 宽容、模块注入以及第三方脚本操作都存在风险，可能带来系统异常、数据丢失、应用风控、保修争议或无法开机等后果。请务必提前备份重要数据，并且仅在",[43,44,45],"strong",{},"本人拥有且已明确授权","的设备上操作。",[48,49,52],"folding",{":open":50,"title":51},"true","免责声明与适用范围",[53,54,55,59,66,73,78],"ol",{},[56,57,58],"li",{},"本文内容仅用于个人技术研究、学习记录与经验整理，不提供任何破解服务、远程代刷或商业用途支持。",[56,60,61,62,65],{},"本文所述方案为",[43,63,64],{},"临时 Root","，重启后权限通常会失效；若需要再次使用，一般需要重新执行相应提权流程。",[56,67,68,69,72],{},"免解 BL 的临时提权方案对机型、芯片平台、系统版本、内核状态、驱动环境与脚本版本都有较强依赖，",[43,70,71],{},"并不保证所有高通机型都能成功复现","。",[56,74,20,75,77],{},[22,76,24],{"code":24}," 为例进行说明；其他高通骁龙 8 Gen 系列机型请根据自身设备情况自行判断兼容性。",[56,79,80,81,72],{},"隐藏环境、规避风控、对抗检测等内容",[43,82,83],{},"不在本文讨论范围内",[85,86,87],"h2",{"id":87},"前言",[18,89,90],{},"近一段时间，围绕“免解 BL 获取临时 Root”的讨论热度很高，核心原因在于这类方案既保留了原系统的大部分状态，又能在特定条件下临时获得更高权限，从而完成模块安装、框架加载和更深入的系统调试。",[18,92,93,94,96,97,100,101,104,105,107,108,111,112,114,115,118,119,122,123,126],{},"从官方资料来看，",[22,95,28],{"code":28}," 本质上是一套",[43,98,99],{},"基于内核的 Android Root 方案","；",[22,102,103],{"code":103},"Zygisk Next"," 则提供了适配 ",[22,106,28],{"code":28}," 的 ",[22,109,110],{"code":110},"Zygisk API"," 实现；",[22,113,32],{"code":32}," 则是面向现代 Android 的 ",[22,116,117],{"code":117},"ART Hook"," 框架，兼容相当一部分 ",[22,120,121],{"code":121},"Xposed"," 模块生态。也正因为如此，在部分设备上，哪怕没有解开 Bootloader，也可能借助特定脚本和环境完成一次",[43,124,125],{},"临时提权 + 框架加载","的组合操作。",[18,128,129],{},"不过需要强调的是，“能提权”不等于“适合长期稳定日用”。这类方案往往更适合作为测试、研究、临时使用或单次操作场景。若你更看重长期稳定性、可维护性和可预期的系统行为，那么在动手之前，最好先明确自己的目标，再决定是否继续。",[85,131,132],{"id":132},"相关项目",[134,135],"link-card",{"description":136,"icon":137,"link":138,"title":139},"了解 KernelSU 的定位、适用范围与官方说明。","https://kernelsu.org/favicon.ico","https://kernelsu.org/guide/what-is-kernelsu.html","KernelSU 官方文档",[134,141],{"description":142,"icon":143,"link":144,"title":145},"查看 LSPosed 的框架说明、支持版本与发布页面。","https://github.com/favicon.ico","https://github.com/LSPosed/LSPosed","LSPosed 官方项目",[134,147],{"description":148,"icon":143,"link":149,"title":150},"适配 KernelSU 的独立 Zygisk 实现，用于承接 LSPosed 等依赖。","https://github.com/Dr-TSNG/ZygiskNext","Zygisk Next 官方项目",[85,152,153],{"id":153},"最终效果说明",[18,155,156],{},"完成本文流程后，你大致可以获得以下效果：",[158,159,160,165,176],"ul",{},[56,161,162,163,72],{},"在不解开 BL 的前提下，于当前会话内获得一次",[43,164,64],{},[56,166,167,168,170,171,173,174,72],{},"在 ",[22,169,28],{"code":28}," 环境下刷入 ",[22,172,103],{"code":103}," 与 ",[22,175,32],{"code":32},[56,177,178,179,181],{},"通过补充脚本修复 ",[22,180,32],{"code":32}," 的运行状态，使其在当前提权会话中正常工作。",[18,183,184],{},"同时也要明确：",[158,186,187,192,195],{},[56,188,189,72],{},[43,190,191],{},"重启后 Root 大概率会失效",[56,193,194],{},"若后续还要继续使用 Root / LSP 功能，通常需要重新执行临时提权流程。",[56,196,197],{},"本文不包含 Play Integrity、隐藏 Root、模块防检测等扩展内容。",[85,199,200],{"id":200},"准备工作",[18,202,203],{},"在正式开始前，请先把需要的文件准备齐全，避免做到一半中断。",[48,205,207],{":open":50,"title":206},"所需文件与下载地址",[158,208,209,233,251,267,285],{},[56,210,211,212],{},"教程完整文件夹（包含本文提到的全部网盘文件）\n",[158,213,214,224,230],{},[56,215,216,217],{},"网盘下载：",[218,219,223],"a",{"href":220,"rel":221},"https://pan.jiugg.top/s/ZovqLh6ovj",[222],"nofollow","点击打开",[56,225,226,227],{},"提取码：",[22,228,229],{"code":229},"PngT",[56,231,232],{},"说明：如果你不想逐个下载本文里的文件，直接保存这个总文件夹即可。",[56,234,235,237,238],{},[22,236,28],{"code":28}," 管理器安装包\n",[158,239,240,246],{},[56,241,216,242],{},[218,243,223],{"href":244,"rel":245},"https://pan.jiugg.top/s/VZ9mVVB5KK",[222],[56,247,226,248],{},[22,249,250],{"code":250},"r9iz",[56,252,253,254],{},"临时提权脚本包\n",[158,255,256,262],{},[56,257,216,258],{},[218,259,223],{"href":260,"rel":261},"https://pan.jiugg.top/s/e4gSjRxUCE",[222],[56,263,226,264],{},[22,265,266],{"code":266},"nLPz",[56,268,269,271,272],{},[22,270,32],{"code":32}," 套件压缩包\n",[158,273,274,280],{},[56,275,216,276],{},[218,277,223],{"href":278,"rel":279},"https://pan.jiugg.top/s/e4pgwsipSH",[222],[56,281,226,282],{},[22,283,284],{"code":284},"XcnS",[56,286,287,288,291],{},"小米 / 红米驱动工具：",[22,289,290],{"code":290},"MiFlash",[158,292,293,300,308,313],{},[56,294,295,296],{},"官网：",[218,297,298],{"href":298,"rel":299},"https://miuiver.com/miflash/",[222],[56,301,302,303,307],{},"若官网直链下载较慢，可前往本站网盘 ",[218,304,305],{"href":305,"rel":306},"https://pan.jiugg.top/",[222]," 输入对应信息取件",[56,309,226,310],{},[22,311,312],{"code":312},"UzzG",[56,314,315,316],{},"取件码：",[22,317,318],{"code":318},"036435",[320,321,328],"pre",{"className":322,"code":324,"filename":325,"language":326,"meta":327},[323],"language-txt","Zygisk-Next-1.3.2-688-2c60cdd-release.zip\nLSPosed-v1.9.2-it-7467-release.zip\nfix_lspd.sh\n","LSPosed 套件内的关键文件","txt","",[22,329,324],{"__ignoreMap":327},[85,331,333],{"id":332},"第一步手机端安装-kernelsu-管理器","第一步：手机端安装 KernelSU 管理器",[18,335,336,337,339],{},"先将下载好的 ",[22,338,28],{"code":28}," 管理器 APK 安装到手机中，后续临时提权完成后，需要在手机端打开它进行最终授权与状态确认。",[85,341,343],{"id":342},"第二步开启开发者模式与-usb-调试","第二步：开启开发者模式与 USB 调试",[18,345,346],{},"这一步建议做得细一些，因为很多“脚本没反应”“设备不识别”的问题，其实都卡在这里。",[348,349,351],"h3",{"id":350},"_21-打开开发者模式","2.1 打开开发者模式",[18,353,354],{},"以小米 / 红米系机型为例：",[53,356,357,363,373],{},[56,358,359,360,72],{},"打开手机 ",[43,361,362],{},"设置",[56,364,365,366,369,370,72],{},"进入 ",[43,367,368],{},"我的设备"," 或 ",[43,371,372],{},"关于手机",[56,374,375,376,369,379,382],{},"连续点击 ",[43,377,378],{},"OS 版本",[43,380,381],{},"MIUI 版本"," 多次，直到提示“您已处于开发者模式”。",[348,384,386],{"id":385},"_22-打开-usb-调试","2.2 打开 USB 调试",[53,388,389,392,397,403,409,420],{},[56,390,391],{},"返回设置首页。",[56,393,365,394,72],{},[43,395,396],{},"更多设置",[56,398,399,400,72],{},"找到 ",[43,401,402],{},"开发者选项",[56,404,405,406,72],{},"开启 ",[43,407,408],{},"USB 调试",[56,410,411,412,415,416,419],{},"如果系统中存在 ",[43,413,414],{},"USB 调试（安全设置）","、",[43,417,418],{},"USB 安装"," 等相关选项，可根据脚本提示按需开启。",[56,421,422,423,426],{},"手机通过 USB 连接电脑后，若弹出“是否允许此电脑进行 USB 调试”，请选择 ",[43,424,425],{},"允许","，并可勾选“始终允许”。",[428,429],"pic",{"caption":430,"src":431},"手机端提前安装 KernelSU 管理器，方便后续完成临时提权","https://dev.jiugg.top/i/dd7c6b71-358e-418f-8f1a-f860d1642fb9.webp",[35,433,436],{"title":434,"type":435},"建议","info",[18,437,438],{},"数据线尽量使用稳定的原装线或质量较好的数据线，电脑端尽量直连主机 USB 接口，避免通过扩展坞或前置接口操作，以减少驱动识别失败的概率。",[85,440,442],{"id":441},"第三步电脑端安装驱动并确认设备识别","第三步：电脑端安装驱动并确认设备识别",[18,444,445,446,448,449,452],{},"对于小米 / 红米机型，建议先在电脑上安装 ",[22,447,290],{"code":290},"，本质上是借它补齐常用驱动环境，避免 ",[22,450,451],{"code":451},"ADB / Fastboot"," 无法识别设备。",[348,454,456],{"id":455},"_31-安装-miflash","3.1 安装 MiFlash",[53,458,459,465,471,474],{},[56,460,461,462],{},"前往官网下载安装包：",[218,463,298],{"href":298,"rel":464},[222],[56,466,467,468,72],{},"解压并打开 ",[22,469,470],{"code":470},"XiaoMiFlash.exe",[56,472,473],{},"按安装向导完成驱动安装。",[56,475,476],{},"安装完成后，重新连接手机。",[348,478,480],{"id":479},"_32-确认电脑能够识别设备","3.2 确认电脑能够识别设备",[18,482,483,484,486,487,490],{},"打开 ",[22,485,290],{"code":290}," 后，点击 ",[43,488,489],{},"加载设备","。如果界面中能够看到你的设备信息，说明当前驱动基本正常，后续脚本执行会顺利很多。",[18,492,493,494],{},"驱动安装界面示意：",[218,495,496],{"href":496,"rel":497},"https://dev.jiugg.top/i/a9d2f9b8-6822-4422-9e2e-a77207df31d7.",[222],[85,499,501],{"id":500},"第四步执行脚本获取临时-root","第四步：执行脚本获取临时 Root",[18,503,504],{},"这一步是全文最关键的部分，请严格按照顺序执行。",[348,506,508],{"id":507},"_41-连接设备并打开脚本包","4.1 连接设备并打开脚本包",[53,510,511,514,517,520],{},[56,512,513],{},"保持手机正常开机状态。",[56,515,516],{},"用 USB 将手机连接到电脑。",[56,518,519],{},"确认手机已经弹出并同意 USB 调试授权。",[56,521,522],{},"打开此前下载好的临时提权脚本文件夹。",[428,524],{"caption":525,"src":526},"电脑端打开脚本包，准备执行临时提权流程","https://dev.jiugg.top/i/8a861ba9-1b0a-4c73-a487-4cd341230335.webp",[348,528,530],{"id":529},"_42-运行-fastboot-selinux-宽容脚本","4.2 运行 Fastboot + SELinux 宽容脚本",[18,532,533],{},"在脚本目录中运行下面这个批处理文件：",[320,535,539],{"className":536,"code":537,"filename":538,"language":326,"meta":327},[323],"1、开机状态进入Fastboot并执行SELinux宽容.bat\n","执行文件",[22,540,537],{"__ignoreMap":327},[18,542,543],{},"这个脚本的作用可以理解为：在开机状态下把设备切换到对应环境，并执行后续提权所需的宽容设置。",[428,545],{"caption":546,"src":547},"脚本执行到 SELinux 宽容阶段的流程示意","https://dev.jiugg.top/i/c5bf80a1-30bd-40f9-8f3f-1c6ff4a51e0c.webp",[348,549,551],{"id":550},"_43-回到手机端完成-kernelsu-提权","4.3 回到手机端完成 KernelSU 提权",[18,553,554],{},"当设备自动重启后：",[53,556,557,563,570,577,583],{},[56,558,559,560,562],{},"打开手机中的 ",[22,561,28],{"code":28}," 管理器。",[56,564,565,566,569],{},"点击界面中的 ",[43,567,568],{},"越狱"," 按钮。",[56,571,572,573,576],{},"等待大约 ",[22,574,575],{"code":575},"2"," 分钟左右，直到加载完成。",[56,578,579,580,582],{},"将 ",[22,581,28],{"code":28}," 从后台划掉后重新进入。",[56,584,585,586,72],{},"如果界面状态显示已经进入对应模式，就说明这次",[43,587,588],{},"临时 Root 已经完成",[35,590,592],{"title":591,"type":38},"重要说明",[18,593,594],{},"这里获得的是临时权限。设备一旦重启，Root 状态通常就会丢失；后续如果需要继续使用 Root 或 LSP，往往还需要重新执行本节步骤。",[85,596,598],{"id":597},"第五步安装-lsposed-与相关依赖","第五步：安装 LSPosed 与相关依赖",[18,600,601,602,604],{},"完成临时 Root 后，就可以继续安装 ",[22,603,32],{"code":32}," 相关内容了。",[348,606,608],{"id":607},"_51-解压-lsposed-套件","5.1 解压 LSPosed 套件",[18,610,611,612,615,616,618],{},"将下载好的 ",[22,613,614],{"code":614},"LSPosed.zip"," 放到手机中并解压。解压后，重点会用到前面列出的三个文件，其中真正需要在 ",[22,617,28],{"code":28}," 中刷入的是下面两个模块包：",[158,620,621,626],{},[56,622,623],{},[22,624,625],{"code":625},"Zygisk-Next-1.3.2-688-2c60cdd-release.zip",[56,627,628],{},[22,629,630],{"code":630},"LSPosed-v1.9.2-it-7467-release.zip",[428,632],{"caption":633,"src":634},"LSPosed 套件解压后的文件示意","https://dev.jiugg.top/i/d9d050b1-f1aa-473a-b8d2-e15a16e31097.webp",[348,636,638],{"id":637},"_52-在-kernelsu-中添加模块","5.2 在 KernelSU 中添加模块",[53,640,641,645,651,657],{},[56,642,483,643,72],{},[22,644,28],{"code":28},[56,646,365,647,650],{},[43,648,649],{},"模块"," 页面。",[56,652,653,654,72],{},"点击右下角 ",[43,655,656],{},"加号",[56,658,659,660],{},"依次添加：\n",[158,661,662,666],{},[56,663,664],{},[22,665,625],{"code":625},[56,667,668],{},[22,669,630],{"code":630},[428,671],{"caption":672,"src":673},"在 KernelSU 中依次刷入 Zygisk Next 与 LSPosed","https://dev.jiugg.top/i/84876919-5f51-412c-b20e-300db6fcb1bf.webp",[348,675,677],{"id":676},"_53-重启后重新获取临时-root","5.3 重启后重新获取临时 Root",[18,679,680,681,684],{},"模块刷入完成后，系统通常会提示重启。这一步请",[43,682,683],{},"正常重启","即可。",[18,686,687],{},"但要注意，重启以后之前的临时 Root 一般已经失效，所以这里还需要：",[53,689,690,697],{},[56,691,692,693,696],{},"按照本文 ",[43,694,695],{},"第四步"," 的方法，再次执行临时提权流程。",[56,698,699,700,702],{},"确认 ",[22,701,28],{"code":28}," 已重新进入可用状态。",[85,704,706],{"id":705},"第六步执行修复脚本让-lsposed-正常工作","第六步：执行修复脚本让 LSPosed 正常工作",[18,708,709],{},"重新完成临时提权后，还差最后一步修复。",[53,711,712,723,732,735],{},[56,713,714,715,718,719,722],{},"给 ",[22,716,717],{"code":717},"MT 管理器"," 授予 ",[22,720,721],{"code":721},"root"," 权限。",[56,724,725,726,728,729,72],{},"以 ",[22,727,721],{"code":721}," 身份执行 ",[22,730,731],{"code":731},"fix_lspd.sh",[56,733,734],{},"执行结束后，设备会自动重启。",[56,736,737,738,740],{},"开机后，",[22,739,32],{"code":32}," 一般即可恢复正常运行。",[428,742],{"caption":743,"src":744},"通过 MT 管理器以 root 执行 fix_lspd.sh","https://dev.jiugg.top/i/7ad7252b-c494-46b8-af83-5e70d5031314.webp",[35,746,748],{"title":747,"type":435},"补充说明",[18,749,750,751,753,754,756],{},"如果以后再次重启设备，发现 ",[22,752,32],{"code":32}," 状态异常，通常可以在重新获取临时 Root 后，再次执行一次 ",[22,755,731],{"code":731}," 进行恢复。",[85,758,759],{"id":759},"常见问题",[48,761,763],{":open":50,"title":762},"1. 电脑识别不到手机怎么办？",[158,764,765,771,774,780],{},[56,766,767,768,770],{},"先确认手机是否已打开 ",[22,769,408],{"code":408},"，并允许当前电脑的调试授权。",[56,772,773],{},"重新插拔数据线，优先更换主机后置 USB 接口。",[56,775,776,777,779],{},"重新安装 ",[22,778,290],{"code":290}," 驱动。",[56,781,782,783,785],{},"若 ",[22,784,290],{"code":290}," 中点击“加载设备”仍没有反应，可先排查线材和接口问题，再检查是否被系统驱动拦截。",[48,787,789],{":open":50,"title":788},"2. 提权完成后重启就掉 Root，是不是失败了？",[18,790,791,792,794],{},"这通常不是失败，而是",[43,793,64],{},"的正常表现。只要当前会话内已经拿到权限、可以完成后续操作，就说明流程本身是有效的。需要再次使用时，重新执行提权步骤即可。",[48,796,798],{":open":50,"title":797},"3. LSPosed 显示未安装或模块不生效怎么办？",[158,799,800,809,815,823],{},[56,801,802,803,805,806,808],{},"确认已经刷入 ",[22,804,103],{"code":103}," 和 ",[22,807,32],{"code":32}," 两个模块。",[56,810,811,812,72],{},"确认重启后已经",[43,813,814],{},"重新获取过临时 Root",[56,816,699,817,819,820,822],{},[22,818,731],{"code":731}," 是在 ",[22,821,721],{"code":721}," 权限下执行的。",[56,824,825],{},"如果仍异常，可以重复“重启 → 重新提权 → 执行 fix_lspd.sh”的流程再试一次。",[48,827,829],{":open":50,"title":828},"4. 本文有没有隐藏环境教程？",[18,830,831,832,834],{},"没有。本文只整理临时 Root 与 ",[22,833,32],{"code":32}," 的安装流程，不讨论隐藏环境、对抗检测和风控绕过相关内容。",[85,836,837],{"id":837},"总结",[18,839,840],{},"如果你的目标只是：",[158,842,843,849,855],{},[56,844,845,846],{},"在特定设备上临时获取一次 ",[22,847,848],{"code":848},"Root",[56,850,851,852,854],{},"装上 ",[22,853,28],{"code":28}," 生态下的模块",[56,856,857,858,860],{},"进一步把 ",[22,859,32],{"code":32}," 跑起来",[18,862,863,864,72],{},"那么这套流程基本已经够用。它的优点是思路直接、效率较高，不必把整机改造成长期解锁状态；缺点也同样明显，那就是",[43,865,866],{},"依赖脚本、依赖环境、依赖机型适配，且重启即失效",[18,868,869],{},"因此，更推荐把它视作一套“研究型、临时型、操作型”的方案，而不是无脑长期日用方案。只要你提前理解了这个边界，整个流程的预期就会清晰很多。",[85,871,872],{"id":872},"参考链接",[158,874,875,881,888,894,900],{},[56,876,877,878],{},"KernelSU 官方文档：",[218,879,138],{"href":138,"rel":880},[222],[56,882,883,884],{},"KernelSU 官方仓库：",[218,885,886],{"href":886,"rel":887},"https://github.com/tiann/KernelSU",[222],[56,889,890,891],{},"LSPosed 官方仓库：",[218,892,144],{"href":144,"rel":893},[222],[56,895,896,897],{},"Zygisk Next 官方仓库：",[218,898,149],{"href":149,"rel":899},[222],[56,901,902,903],{},"MiFlash 下载页：",[218,904,298],{"href":298,"rel":905},[222],{"title":327,"searchDepth":907,"depth":907,"links":908},4,[909,911,912,913,914,915,920,924,929,934,935,936,937],{"id":87,"depth":910,"text":87},2,{"id":132,"depth":910,"text":132},{"id":153,"depth":910,"text":153},{"id":200,"depth":910,"text":200},{"id":332,"depth":910,"text":333},{"id":342,"depth":910,"text":343,"children":916},[917,919],{"id":350,"depth":918,"text":351},3,{"id":385,"depth":918,"text":386},{"id":441,"depth":910,"text":442,"children":921},[922,923],{"id":455,"depth":918,"text":456},{"id":479,"depth":918,"text":480},{"id":500,"depth":910,"text":501,"children":925},[926,927,928],{"id":507,"depth":918,"text":508},{"id":529,"depth":918,"text":530},{"id":550,"depth":918,"text":551},{"id":597,"depth":910,"text":598,"children":930},[931,932,933],{"id":607,"depth":918,"text":608},{"id":637,"depth":918,"text":638},{"id":676,"depth":918,"text":677},{"id":705,"depth":910,"text":706},{"id":759,"depth":910,"text":759},{"id":837,"depth":910,"text":837},{"id":872,"depth":910,"text":872},[939],"技术","2026-03-20 23:24:28","本文以 Redmi K70 Pro 为例，整理免解 BL 获取临时 Root、安装 KernelSU 与 LSPosed 的完整流程",false,"md","https://dev.jiugg.top/i/9f19bb3e-98fd-4b68-8416-89b8255c2682.webp",{"slots":946},{},true,"/2026/20260320-1",null,"https://cdn.jiugg.top/boke/免解+BL+临时获取+Root+教程.mp3","https://cdn.jiugg.top/boke/免解+BL+临时获取+Root+教程.lrc","AI播客",{"text":954,"minutes":955,"time":956,"words":957},"13 min read",12.83,769800,2566,{"title":5,"description":941},{"loc":948},"posts/2026/20260320-1",[28,962,32,963,964,965,966],"临时Root","Redmi","K70","Pro","高通","tech","VLxlt0l1ZMCWaQ9DbCPfMjKih3Exs0aSCazM8pJBRTY",[970,975],{"title":971,"path":972,"stem":973,"date":974,"type":967,"children":-1},"侧边栏地区欢迎卡片教程","/2026/20260314-1","posts/2026/20260314-1","2026-03-14 21:50:09",{"title":976,"path":977,"stem":978,"date":979,"type":967,"children":-1},"在 Anheyu 博客中接入 Live2D 看板娘","/2026/20260323-1","posts/2026/20260323-1","2026-03-23 18:04:13",1775556257714]