Android 15 Framework Support

[codylund]

With Android 15 GA on the horizon, can you provide an ETA for the corresponding framework support in ApkTool?

[iBotPeaches]

I'm basically waiting on a smali fix (the only hard-blocker I consider). The Android 15 aspect (with beta frameworks) appears to be fine.

I'm converting this to a discussion

[iBotPeaches]

@Tofalvy why can't you see the 2.10.0 release?

[Tofalvy]

Based on the release description 2.10.0 doesn't support android 35 yet, it supports android API 34:
https://apktool.org/blog/apktool-2.10.0

That's why I thought that 2.10.x means x>0.

[iBotPeaches]

Hmm I guess I honestly switched up API34/35 in my head. Which means there is no release out that supports API 35 and meanwhile I'm working on 2.11.0 that supports API 36 - f85f9b3. So 35 was just missed.

So if you can run a bleeding edge build and just confirm API 35 works - I'll have to rush the timeline on API 2.11.0 or hotfix 2.10.x with whatever I need for API 35.

Build here - https://github.com/iBotPeaches/Apktool/actions/runs/12010277904/artifacts/2232878590

[starbucks2010]

Hi,

I decompiled/recompiled framework.jar from the S928B (S24 ultra) rooted with latest beta 3 OneUI7 Android 15 and flashed via twrp but the device doesn't boot. Let me know if any file/trace is needed.

I used apktool-v2.10.0-18-f8e1a596-SNAPSHOT.jar and the latest smali 3.0.9 20241219.

Thank you.

[iBotPeaches]

Yes please provide a trace, because 3.0.9 smali should have had the fix that I was waiting for. I was about to cut Apktool 2.11 this weekend, so to hear it doesn't work is frightening.

[starbucks2010]

dropboxrc2.zip
here are the dropbox files from device
do you need also the framework-res.apk and framework.jar I used ?

[Emulond]

@starbucks2010 (Andrei), hello there! I'm a fellow custom user, such as you are.
Me and my dear friend ExtremeXT have stumbled upon your dropbox archive. We have noticed that there are native crashes in your logs array.
You see, we are investigating some tremendously complicated issue with OneUI runtime in [OneUI] Native crashes #127, and we need some information about your current setup.

1. Which root solution do you use?
2. Do you use Zygisk? If so, which implementation?
3. Do you use LSPosed? If so, which implementation?
   Best regards

[starbucks2010]

I used batchapktool 3.8.0 with this config if it has any importance

[starbucks2010]

@iBotPeaches any progress on the apktool supporting android 15?

[iBotPeaches]

I believe its going out tonight. I ran out of time last night.

[starbucks2010]

it will be a test version for testing android 15 compatibility ?

[iBotPeaches]

Its completed my basic tests so it will be an official release of 2.11.0

[ExtremeXT]

APKTool compiled from latest master branch successfully booted S24's OneUI 7 Beta 3 here.

[ExtremeXT]

Samsung OneUI 7 (based on Android 15, AP3A) still uses DEX version 039 in the header which APKTool doesn't seem to know how to handle right now. I'm guessing it should function just fine on AOSP or other OEM skins.

UN1CA method works for me: salvogiangri/UN1CA@d3ad136

Using APKTool and Smali/BakSmali built from latest master branch in both sources. With this way I managed to boot just fine without removing invoke-custom calls in smali.

JARs:

Decompile with API 35 via APKTool, but with --no-src to not decompile DEX files:
java -jar apktool.jar decode --api-level 35 --no-debug-info --no-src framework.jar --output framework.jar.out

Decompile each DEX file via Google Smali, with API 29:

java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes.dex framework.jar.out\classes
java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes2.dex framework.jar.out\classes2
java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes3.dex framework.jar.out\classes3
java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes4.dex framework.jar.out\classes4
java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes5.dex framework.jar.out\classes5
java -jar baksmali-3.0.9-fat.jar disassemble --api 29 --accessor-comments false --debug-info false --use-locals --output framework.jar.out\classes6.dex framework.jar.out\classes6

Remove old DEX files:

del framework.jar.out\classes.dex
del framework.jar.out\classes2.dex
del framework.jar.out\classes3.dex
del framework.jar.out\classes4.dex
del framework.jar.out\classes5.dex
del framework.jar.out\classes6.dex

After changing the DEX files - compile them:

java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes.dex framework.jar.out\classes
java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes2.dex framework.jar.out\classes2
java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes3.dex framework.jar.out\classes3
java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes4.dex framework.jar.out\classes4
java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes5.dex framework.jar.out\classes5
java -jar smali-3.0.9-fat.jar assemble --api 29 --output framework.jar.out\classes6.dex framework.jar.out\classes6

Compile JAR with APKTool:
java -jar apktool.jar build --copy-original framework.jar.out

Zipalign JAR:
zipalign -p 4 framework.jar.out\dist\framework.jar framework_mod.jar

*APKs: *

TBD, but I think it's the same, just with the framework-res file loaded.

Make sure oat/arm64/arm files in system/framework, along with boot-*.odex are removed. Push to phone, wipe dalvik cache and reboot.

Commands use Windows' PATH separator, but there's no reason for it to not work on Linux as well, provided that the path is adapted.

@starbucks2010 @iBotPeaches

[starbucks2010]

it seems quite a tedious job following this procedure but thank you for the details
I hope Connor will find a better solution for A15

[ExtremeXT]

Well, this isn't an APKTool issue per se, just Samsung being Samsung. But yes, it would be nice for APKTool to gain an official workaround.

[iBotPeaches]

With v2.11.0 release last night - I want to close this and track any regressions/further issues in their own tickets.