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

[Fatal Error] :1:1: Content is not allowed in prolog. #1634

Closed
WilsonCP opened this Issue Oct 3, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@WilsonCP

WilsonCP commented Oct 3, 2017

Information

  1. Apktool Version (apktool -version) - 2.3.0
  2. Operating System (Mac, Linux, Windows) - Linux
  3. APK From? (Playstore, ROM, Other) -

Stacktrace/Logcat

apktool b framework-res
I: Using Apktool 2.3.0
W: Could not find sources
[Fatal Error] :1:1: Content is not allowed in prolog.
I: Checking whether resources has changed...
I: Building apk file...
I: Copying unknown files/dir...

Steps to Reproduce

  1. apktool b frameword-res

Frameworks

If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)

APK

If this APK can be freely shared, please upload/attach a link to it.

Questions to ask before submission

  1. Have you tried apktool d, apktool b without changing anything? YES
  2. If you are trying to install a modified apk, did you resign it?
  3. Are you using the latest apktool version? YES

Hi, I've pasted above the message I'm getting when building framework-res folder. On Decompiling, I have no problem whatsoever. The only change I did with the folder is changing default_wallpaper and nothing else. Hope you could help me with this.

By the way, Thanks for this awesome project.

@iBotPeaches

This comment has been minimized.

Show comment
Hide comment
@iBotPeaches

iBotPeaches Oct 3, 2017

Owner

Seems like the build completed, what commands did you use for the decode? It seems the decoding of the resources was skipped or a binary manifest was provided, hence why it threw that strange error.

Owner

iBotPeaches commented Oct 3, 2017

Seems like the build completed, what commands did you use for the decode? It seems the decoding of the resources was skipped or a binary manifest was provided, hence why it threw that strange error.

@WilsonCP

This comment has been minimized.

Show comment
Hide comment
@WilsonCP

WilsonCP Oct 4, 2017

apktool d framwork-res.apk

Yeah, but after the building I don't get updated apk.
Will the built apk reside on another path on it will appear on the active dir?
Thanks!

WilsonCP commented Oct 4, 2017

apktool d framwork-res.apk

Yeah, but after the building I don't get updated apk.
Will the built apk reside on another path on it will appear on the active dir?
Thanks!

@iBotPeaches

This comment has been minimized.

Show comment
Hide comment
@iBotPeaches

iBotPeaches Oct 4, 2017

Owner

Hmm. I still can't replicate this. Since no apk provided I just tried a random set of applications and never got that warning with those steps.

Any ideas?

Owner

iBotPeaches commented Oct 4, 2017

Hmm. I still can't replicate this. Since no apk provided I just tried a random set of applications and never got that warning with those steps.

Any ideas?

@WilsonCP

This comment has been minimized.

Show comment
Hide comment
@WilsonCP

WilsonCP Oct 6, 2017

Sorry If I can't provide the exact framework-res.apk

Right now, I was able to recompile it, dunno what I did, but it worked, the problem is (maybe this should be a different issue), my device is stucked at boot screen when I put the edited framework-res.apk, again, I've only changed the default_wallpaper.jpg.

Thanks man for the response

WilsonCP commented Oct 6, 2017

Sorry If I can't provide the exact framework-res.apk

Right now, I was able to recompile it, dunno what I did, but it worked, the problem is (maybe this should be a different issue), my device is stucked at boot screen when I put the edited framework-res.apk, again, I've only changed the default_wallpaper.jpg.

Thanks man for the response

@iBotPeaches

This comment has been minimized.

Show comment
Hide comment
@iBotPeaches

iBotPeaches Nov 1, 2017

Owner

Devices stuck at boot screen point to a different issue. Usually the log-cat will have more information for this. It could be anything from a missing signature or wrong key, system rejected, etc.

I am going to confirm this for the warning "Prolog" error, which has nothing to do with your error.

Owner

iBotPeaches commented Nov 1, 2017

Devices stuck at boot screen point to a different issue. Usually the log-cat will have more information for this. It could be anything from a missing signature or wrong key, system rejected, etc.

I am going to confirm this for the warning "Prolog" error, which has nothing to do with your error.

@iBotPeaches iBotPeaches changed the title from Recompiling fatal error to [Fatal Error] :1:1: Content is not allowed in prolog. Nov 1, 2017

@iBotPeaches iBotPeaches added Bug and removed Waiting for issuer labels Nov 1, 2017

iBotPeaches added a commit that referenced this issue Dec 1, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment