search

rapid7 / metasploit-framework

Metasploit Framework
https://www.metasploit.com/
Other
33.66k stars 13.87k forks source link

msfvenom error (Not sure if this is the right section,sorry) #9391

Closed ProsAnon closed 5 years ago

ProsAnon commented 6 years ago

Sorry in advance if I mistake the section, and sorry for my english.not my main.

I get this error while I try to msfvenom -x facebook.apk with android payload, I must say that it works with an other .apk file. Does anyone know what to do?

Sorry again if I posted this in a wrong place. poza

timwr commented 6 years ago

What version of apktool do you have? Can you provide the apk? I'm sure this used to work...

ProsAnon commented 6 years ago

I have apktool version 2.2.2. What apk do you mean to provide? I downloaded facebook apk from google, I think apkmirror. I said that it works with other apks, i.e. I tried with ES File Explorer and it worked.

ProsAnon commented 6 years ago

Got this error with whatsapp too.. screenshot from 2018-01-10 17-09-46

kula124p commented 6 years ago

Hi There is a problem with apktool it seams. You should use apktool empty-framework-dir to remove outdated framework Also, damn thing won't build even with this. Replacing "/original/res/layout-v26/abc_screen_toolbar.xml" with code below fixed it for me <?xml version="1.0" encoding="utf-8"?> <android.support.v7.widget.ActionBarOverlayLayout android:id="@id/decor_content_parent" android:fitsSystemWindows="true" android:layout_width="fill_parent" android:layout_height="fill_parent" xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto"> <include layout="@layout/abc_screen_content_include" /> <android.support.v7.widget.ActionBarContextView android:theme="?actionBarTheme" android:id="@id/action_context_bar" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="wrap_content" style="?attr/actionModeStyle" /> </android.support.v7.widget.ActionBarOverlayLayout> DID NOT TEST. I don't know if this will install in Android let alone open a session. Will test and report back soon...ish. Few more suggestions: Add logger so we can see where the issue is... took me hours to find this shit and I found it bc it was logged in another tool. Add more control over the process, divide it into steps so if one fails 'cuz of automation (like this one) I can fix it manually and continue from the next step. Even better: add retry option WITHOUT rewriting created files, or redoing done steps. It would do stuff it hasn't done yet and in the meanwhile we can fix whatever causes the error. Would be very useful.

References: https://github.com/iBotPeaches/Apktool/issues/1579 https://github.com/iBotPeaches/Apktool/issues/1697 https://github.com/iBotPeaches/Apktool/issues/1725

timwr commented 5 years ago

This can be fixed with apktool empty-framework-dir --force. I think it occurs when switching between apktool versions.