Android emulator Error:- executing /system/bin/e2fsck failed: No such file or directory

前端 未结 5 1145
半阙折子戏
半阙折子戏 2021-01-15 03:09

I am trying to run my first Android App on Android Emulator on API 19. The Emulator get started but nothing comes up, means Home scree

相关标签:
5条回答
  • 2021-01-15 03:39

    I updated my SDK but still same problem.

    Only solution I found is :- I updated my SDK for lower API's and switched over to lover API like 17 and my emulator get started. But still can not get the features of API 19.

    0 讨论(0)
  • 2021-01-15 03:41

    It looks like the emulator was unable to mount the file system because of errors. The underlying file system for the emulator was changed to ext4 and e2fsprogs utilities were not included. These utilities are required by the kernel for proper operation. On OSX and Linux you can use the standard e2fsprogs utilities to repair the file system.

    # Navigate to AVD
    cd ~/.android/avd/Nexus5
    e2fsck -f userdata-qemu.img
    

    There is a e2fsprogs package available for Cygwin but I haven't tested it. This issue has been corrected for future distributions. See: e2fsck missing from emulator.

    If you still cannot boot the emulator after running e2fsck post the kernel log by adding -show-kernel to the emulator command line.

    0 讨论(0)
  • 2021-01-15 03:53

    I found the solution my self that I had to edit the AVD skin to use “skin with dynamic hardware controls”

    0 讨论(0)
  • 2021-01-15 03:55

    After checking your issue, I tried it too , to check whether emulator is opening the home page or not. I am sharing what I tried, it might work for you too.

    1. First install all android SDK Build Tools for 19 API

    See the below Image for reference :

    enter image description here

    2. Go To AVD Manager and click New , and select API level 19 and screen size as per your need. See below image for reference what I took in my case.

    enter image description here

    3.And then start your emulator created, It worked in my case.

    0 讨论(0)
  • 2021-01-15 04:01

    I found the answer AJ,

    a change in the file format was applied to android OS images in Dec, but e2fsck was not included in build..

    update your sdk ie the android OS emulator images and re create your AVDs and that should resolve the problem.

    0 讨论(0)
提交回复
热议问题