android api 29 上的 adb remount 是否损坏?

Is adb remount broken on android api 29?(android api 29 上的 adb remount 是否损坏?)

问题描述

adb remount 在 api 29 上无法正常工作.该命令在所有其他已尝试过的模拟器(18、23、25、26、27 和 28)上运行良好.

adb remount does not work correctly on api 29 when running from the emulator. The command works fine on all other emulators that have been tried (18, 23, 25, 26, 27 and 28).

任何想法为什么会这样?

Any ideas why this might be?

Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
W Disabling verity for /system
E Skipping /system
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
/system/bin/remount exited with status 7
remount failed

推荐答案

更新:

查看@KiddTang 的答案，这似乎是一个实际的解决方案

Update:

See @KiddTang answer which seems to be an actual solution

• 即使使用 API 30 (API R)，这个问题现在仍然存在！甚至在使用 writable-system 选项启动模拟器时:(emulator -writable-system -avd NAME_OF_DEVICE)！

• 我发现 Google 的问题跟踪器中有一个现有问题.

我尝试遵循这些 说明在重新安装之前禁用验证并重新启动

I tried following these instructions to disable-verity and reboot before remounting

• 但是这个解决方案导致我的模拟器死机/挂起，并且永远无法启动.

注意:我在使用带有AVD"的模拟器时遇到了当前问题.提供了Android Sdk 图片".然而，这种图像可能会有所限制.所以其他类型的 Android 图片可能不会发生这种情况

Note: I am experiencing the current issue when using the emulator with the "AVD" provided "Android Sdk Images". Its possible however that this kind of images are limited somewhat. So it might not occur for other types of Android Images

• 此代码不适用于我的情况，因为它会导致模拟器冻结并且在重新启动后无法启动，但是，它们可能适用于其他人.
  • 查看链接了解更多详情和注意事项.
  • This code did not work for my situation, as it causes the emulator to freeze and wont start after rebooting, however, they may work others.
    • See the link for additional details and caveats.

    $ adb root
    $ adb disable-verity
    $ adb reboot
    $ adb wait-for-device
    $ adb root
    $ adb remount
    

    • 然后输入以下序列之一:

    $ adb shell stop
    $ adb sync
    $ adb shell start
    $ adb reboot
    

    • 或

    $ adb push <source> <destination>
    $ adb reboot
    

    • 请注意，您可以按上述顺序替换这两行:

    $ adb disable-verity
    $ adb reboot
    

    • 用这一行:

    $ adb remount -R
    

    注意:如果设备已经处于 adb remount 状态，adb remount -R 不会重启.

    Note: adb remount -R won’t reboot if the device is already in the adb remount state.

    这篇关于android api 29 上的 adb remount 是否损坏?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！