-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to extract API level from build.prop #128
Comments
Damn it another fuse related bug (Ubuntu 16.04.5 box). I'm so frustrated with the poor quality of Linux ext4 fuse tools. Seems that in the case of this angler image ext4fuse (current default extract method for Linux) screws-up with some inode numbers, so the build.prop file is effectively an oat file.
debugfs, fuse-ext2 & debugfs alternative method appear to work for this image. If I have time I'll try to isolate the bug and report it to upstream ext4fuse project. |
Thanks, confirming it works with fuse-ext2 so I'll stick with that for the time being. |
I believe I'm running into this on Ubuntu /w bullhead:
|
fuse-ext2 fails to mount for some reason:
debugfs works well :) |
I'm having problems extracting vendor from latest angler image (https://dl.google.com/dl/android/aosp/angler-opm6.171019.030.h1-factory-00138df6.zip)
Here is the output I get when running extract-all script (my repo is fully up-to-date):
Am I missing something here?
The text was updated successfully, but these errors were encountered: