Not sure what you've done in the res folder but don't compress resources.arsc when you copy it over.
Not sure what you've done in the res folder but don't compress resources.arsc when you copy it over.
This isn't really an apktool issue.
You can use any zip app you like, but don't compress resources.arsc (or any pngs) when you copy them - use compression level: store for these files.I just copy the resources.arsc File from moded systemui to original with 7zip.
i think this problem for 7zip, can I use another app like winrar?
You can use any zip app you like, but don't compress resources.arsc (or any pngs) when you copy them - use compression level: store for these files.
This isn't an apktool issue though, so this is the wrong place for your question.
I do this way in oreo & pie now
Decompile your systemui.apk then recompile it again , now open decompiled systemui.apk with winrar & extract res / resources.arsc & classes , now again open stock systemui.apk & drag & drop the res folder & resources.arsc & classes to stock sysui with winrar store compresses way & u can u push it system/prev-app/systemui / or even u can tested in clean install to be sure everything is working fine , now u can decompile ur new systemui.apk & do ur edited anywhere there then drag & drop ur edited xml or resources.arsc or classes to ur new sysui & everything is will work just fine , this way i use it to be sure everything is work & also u can do this way with any apk that u gonna edited ..
Edit 1 = this way will fix all the issues that will happen in clean install roms , edited ur fram-res.apk , in normal way it will give u fc with direct lock or fingerprint issues, by this way no more any fc or issues with any apk edited like fram-res.apk or secsetting or systemui.apk ...
For Samsung TouchWiz it's the best , as no any other workaround founded to fix no sysui in a clean install or fc in direct lock when u decompile recompile fram-res.apk or fp fc when u do decompile recompile SecSetting.apk , only by this way it's fixed whole issues for me on TW oreo & pie ..Use the build folder files not ones in the build apk. You are moving compressed files to compressed. Not a that great idea.
For Samsung TouchWiz it's the best , as no any other workaround founded to fix no sysui in a clean install or fc in direct lock when u decompile recompile fram-res.apk or fp fc when u do decompile recompile SecSetting.apk , only by this way it's fixed whole issues for me on TW oreo & pie ..
Well I wouldn't worry about the size of the build as much as finding why it's not working. The size isn't the issue. But since your method isn't working you could try using the build folder. Don't drop entire res just drop any files you edited inside. I've themed Samsung many times and never had to do anything like you said.
When I use the normal way of using the sysui apk was in the build folder, my status bar was lost.
As I put the meta, manifest for sign and permissions, I don't know why this issue shown?
thanks my friend ,Fram-res.apk it's need old versions of apktool ( the version it's not in my mind right now ) & u need to delete some duplicates lines in style.xml & that's it ..
thanks my friend ,
i already tried 2.2.2 version and i deleted the duplicated lines but doesn't help .. there are other problems after ...
do you know which version of apktool i can use?
It's a known issue with building in windows at the moment. Could you send me the latest compiled version? I don't have a Linux setup.@iBotPeaches
My OS is Windows 7 64bit and Java JDK is 1.8.0 build 202.
I tried to compile apktool downloading the code from github, but after some of the latest updates I got several errors during test.
52 tests passed 12 tests with error.
If I compiled using the same github code under Linux (VMWare machine) is working fine.
Thanks.
thanks my friend ,
i already tried 2.2.2 version and i deleted the duplicated lines but doesn't help .. there are other problems after ...
do you know which version of apktool i can use?
Trying compile systemui.apk getting this error
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method [...]
How do I fix this?
- [#3492] Fix #GHSA-vgwr-4w3p-xmjv (Arbitrary file writes on Windows). (Thanks Cl0udG0d)
e28e4b4a413a252617d92b657a33c947
7956eb04194300ce0d0a84ad18771eebc94b89fb8d1ddcce8ea4c056818646f4
- Android 5.1 Support
- New Apktool website since Googlecode is shutting down.
- #658- Fixed issue with double escaping of & and <. (Thanks jhornber)
- #840 - Add support for BCP-47 tags.
- #878 - Fixed issue with unknown files not respecting compression method. (Thanks simtel12)
- #890 - Fixed issue with apktool branding apks with platformBuildName.
- #904 - Fixed issue with multiple dex files skipped when using -s.
- #636 - Fixed issue with @string references in <provider> attributes.
- Increased performance. (Thanks thuxnder & rover12421)
- Fixed issue decoding `.spi` files as 9 patch images. (Thanks Furniel)
Note - This changelog contains changes since 2.0.0 RC4. For full changes in 2.0.0 see here
On my immediate radar is now
- Smali updated to 2.1.2
- #1220 - Fixed issue where APK would wrongly identify as wrong packageId.
- #1224 - Added AndroidManifest.xml file into frameworks to satisfy stock aapt constraints. (Thanks BurgerZ)
- #1235 - Restore -d / --debug-mode to set android:debuggable to true. (Thanks Benjamin-Dobell)
- #1234 - Insert literal versionName if its a reference to satisfy aapt. (Thanks padlar)
- #1131 - Fix Samsung APKs that have an unknown 4 bytes of padding.
- #1240 - Fixed manifest rename for Adobe AIR applications.
- #1005 - Fixed issues with apks that used .9.xml files which improperly triggered 9patch decoder.
- #1020 - Fixed issues with compressing resources that shouldn't be. (Thanks agrieve)
- #1023 - Fixed issue with reference attributes being decoded improperly. (Thanks phhusson)
- #928 - Fixed issue with version qualifiers being added on build.
- #999 - Added support for Android Marshmallow.
- Updated smali/baksmali to 2.0.8