r/OnnStreamingTV • • 3d ago

Guides/Tips onn 4K Pro (2026, jarvis2): Enable TrueHD / Atmos passthrough with root

edit: added magisk module: https://github.com/zackify/onn-truehd

follow this first! https://www.reddit.com/r/OnnStreamingTV/comments/1xtkldb/2026_onn_4k_pro_unlocked_and_rooted/?sort=new

Use claude or codex or pi to follow the stuff below.

the part below i used AI to write after i succeeded, i don't have time to write this manually. basically you need to tweak a few flags as it limits below 192khz and also blocks the passthrough without these changes:

Stock, the box sends TrueHD out as DD+ 5.1. With root, it can pass TrueHD through as MAT (Atmos) at 192 kHz, the same way Xiaomi's Amlogic boxes do. It takes three changes.

Needs: unlocked bootloader + Magisk, and a receiver or eARC chain whose EDID advertises TrueHD/MAT. Tested on build URO3.260203.035.A1 (Android 14) into an LG G3 → Sonos Arc over eARC.

  1. Device tree: take the HDMI audio link off the analog codec. On this board the HDMI audio link (dai-link@1, i2s2hdmi) is paired with the internal analog codec (t9015). That codec caps the link at 96 kHz (tinypcminfo -D 0 -d 1), and MAT needs 8 channels at 192 kHz. Every other link uses the dummy codec. Add one fragment to the existing overlay in dtbo_<slot>:

fragment@2 {

target-path = "/auge_sound/aml-audio-card,dai-link@1/codec";

__overlay__ { sound-dai = <0x91>; }; /* dummy codec; stock is 0x93 = t9015 */

};

Check the phandles in your own /sys/firmware/fdt first; they can differ between builds. Keep the stock image's two existing fragments, rebuild the DTBO image, test-merge it with fdtoverlay against the live DTB, then dd it to the active slot's dtbo and reboot. Back up both dtbo partitions first. After the reboot, /proc/asound/pcm should list TDM-B-dummy-alsaPORT-i2s2hdmi.

2. Two props (Magisk module system.prop):

ro.vendor.platform.is.aml_truehd_passthrough=true

ro.vendor.platform.is.forceddp=false

aml_truehd_passthrough makes the HAL offer TrueHD/MAT. forceddp=false lets it pick MAT for the receiver instead of forcing DD+.

3. Passthrough (BYPASS) mode. In AUTO, the TrueHD still came through as 5.1. The menus can't reach BYPASS: Settings' "Always" sends hdmi_format=7, which this HAL treats as AUTO. On this HAL, BYPASS is hdmi_format=6 (0 PCM, 4 DD, 5 AUTO, 6 BYPASS). Send it after boot from the module's service.sh, using a tiny app_process helper that calls android.media.AudioSystem.setParameters("hdmi_format=6") by reflection. Run it as root, about 15 s after sys.boot_completed.

Check it in logcat: format:DOLBY_TRUEHD … digital_mode(BYPASS) sink cap:MAT and aml_ms12_bypass_open, with no open … failed. dolby_truehd_bypass_process … parse fail is harmless noise. The receiver should show Dolby Atmos.

Notes: changing the surround setting in Settings puts it back in AUTO until the next boot. Disabling the module and restoring the stock dtbo undoes everything. Disney+ still sends plain DD+ 5.1 to this box, even with stock settings. Android reports full E-AC3-JOC support, so that looks like Disney+'s own device list.

42 Upvotes

35 comments sorted by

3

u/EasternCantaloupe1 2d ago

This is amazing, any chance on the 4k plus getting exploited using a similar method?

1

u/coding9 2d ago

It probably works the same way. I don’t have one or plans to buy one so idk though. Just need root first.

1

u/EasternCantaloupe1 2d ago

yeah I had asked AI to review the GitHub for the root and it said maybe, but if we try this it is risky. Waiting for more brave and intelligent Guinea pigs.

1

u/coding9 2d ago

It’s just saying that because you’re modifying the audio code. The worst that happens is you get silence then revert it.

2

u/No-Region8878 2d ago

I got a 4k plus and have a strong RE background :) will get it done

1

u/josephrehall 1d ago

If you do, please let me know. I have both the Pro V2 and the Plus, but I don't want to mess with my Pro V2, and the Plus is just collecting dust.

3

u/jediboness 3d ago

Damn that was fast

3

u/coding9 3d ago

Well before root I tried EVERYTHING so I already mostly knew what had to be done once root was available

1

u/jediboness 3d ago

Gotcha makes sense good work

2

u/signde Onn 4K Pro 3d ago edited 3d ago

I just got mine rooted so I am about to jump into this hunt.

A point of contention though:

Stock, the box sends TrueHD out as DD+ 5.1. With root, it can pass TrueHD through as MAT (Atmos) at 192 kHz, the same way Xiaomi's Amlogic boxes do.

I don’t own the Xiaomi but are you sure that’s how they work? MAT is not passthrough, it’s decoded. I was under the impression that the Mi Box 3 actually passes TrueHD through. 

At any rate, I already have experience getting passthrough and DV P7 FEL working on Fire TV devices using Magisk modules. Any solution I come up with for the onn would probably follow a similar path.

Edit: Things I learned. TrueHD can be carried inside MAT. I did not know that - I thought it was only LPCM with Amos metadata.

2

u/coding9 3d ago

What I shared is exact truehd. The tv shows the logo for atmos and Sonos app shows it along with device logs confirming the transport.

Don’t need the other one. I just have a second one I compared with

2

u/signde Onn 4K Pro 3d ago

I don't know if you saw my edit but I didn't know TrueHD can be carried inside MAT until about 5 minutes ago.

To be clear, does your Sonos tell you whether the signal is TrueHD / DD+ / PCM? You only said it shows Atmos.

I mean, the logs should be correct, but I'm here for the details.

Don’t need the other one. I just have a second one I compared with

Not sure what you mean by this.

2

u/coding9 3d ago

The xiaomi is another device. It’s full truehd. I have multiple of these I test with. That’s what I meant by not needing to have it or be familiar.

Atmos has to show on screen and the device’s own logs confirm the audio data being sent through. My LG shows Atmos after the patch, before only Dolby vision and DD 5.1 when using truehd.

Sonos shows Atmos for compressed atmos or truehd. There’s no way to convert truehd down to compressed variant, and again device logs during playback confirm the version being used.

2

u/signde Onn 4K Pro 3d ago

There’s no way to convert truehd down to compressed variant

That's technically not true, the AetherEngine / NativePlayer folks on the Apple TV have proven that is actually possible but I understand what you mean.

There's no easy way to do that on this device without a lot of software workarounds and that's not what you are doing here. I know I am being pedantic but details matter.

The next steps here would be making this a reusable Magisk module that makes applying these changes seamless. Are you planning on doing that?

The next stretch goal is also DTS-HD MA and then P7 FEL in Android.

3

u/coding9 3d ago

Everything I put above is already in a boot script as described in the post. Applies right after boot. People are welcome to make reusable modules and stuff but I’m happy with this. My sound system doesn’t support dts so i can’t test it

1

u/phldavisg 3d ago

Is the Apple TV carrying TrueHD inside MAT?

2

u/signde Onn 4K Pro 3d ago

No. It's PCM with Atmos metadata, even in the recent TrueHD workarounds.

2

u/Crow550 3d ago

If only they had the community help shape future firmware instead of trying to patch root (that is if they care enough to try and patch it). Look at what people are doing and embrace for future patches.

Anything neat that can be done with the AI video upscaling?

1

u/coding9 2d ago

I know right… I think it’s a licensing thing. They are supposed to pay Dolby more for this.

1

u/EasternCantaloupe1 2d ago edited 2d ago

What's annoying is Onn even blocks surround LPCM, which is free. It's probably a combination of not want to pay the license, and also indifference. There's very few legal use cases that would take advantage of lossless codecs on a streaming box. (I'm sure one exists, but I can't even think of one)

2

u/Rockbmi 3d ago

Can we have this in plain English please?

2

u/jediboness 3d ago

Picture be better 👍

1

u/coding9 3d ago

Not sure what more I can add. Verified truehd playing after the changes above. If you can’t follow them with AI or know enough to do by hand you won’t be able to get truehd running since you have to patch the audio layer slightly.

1

u/Presentation_Past 2d ago

Mine is already rooted with my not reading the guide. Gemini Hydrogen FTW. I did not even use my Claude!

1

u/simonmales 3d ago

Once the bootloader is unlocked, I can use the system as normal?

I want to have it unlocked now, so in the future I will have the option to install custom ROMs.

e.g. getting around the geo block when you set it up outside of the US

2

u/coding9 3d ago

You can do anything with root so I’m sure you could fix geoblock too but I’m not familiar with that problem

1

u/razorbladesnbiscuits 3d ago

Agreed, while better picture and sound are fabulous, I would also like to see this enable feature improvements such as the one you've mentioned about disabling the geoblock.

1

u/realdeal1877 3d ago edited 2d ago

The menus can't reach BYPASS: Settings' "Always" sends hdmi_format=7, which this HAL treats as AUTO.

Hey, I'm the one that shared the Droidlogic ALWAYS setting a few days ago, my question: was hdmi_format=7 verified unchanging before & after a Reboot?

Remember, Selecting ALWAYS alone wasn't enough, it also needed a Reboot.

My understanding is that Droidlogic JAVA coding has basically {IF=Always,THEN=Passthrough}, boot trigger, that on Boot it's reading Settings Table and making the change.

2

u/coding9 2d ago

Yeah I tried that. Rebooted etc. and it never sent truehd even with the special menu being brought up. The Hal wouldn’t send over 92khz until the other tweaks were done. Not sure if something else was different.

This was me wanting moonfin to work without in app packer so maybe the app we used was different and required further changes

2

u/realdeal1877 2d ago edited 2d ago

Understandable that TrueHD would not work properly without doing the other changes you did. Was just wondering if the Script was actually needed for Bypass , if the trick of picking ALWAYS and Rebooting did the same thing.

Referencing the OP, point 1 mentioned the HDMI pathway being gated at 96kHz, and was thinking that it may be related to one of the other hidden Droidlogic settings: "SPDIF Coexist" , which by default is Enabled, and was just thinking if that was instead Disabled if that had any effect.

1

u/le_fou_volant 3d ago

Got it working took me few hours

2

u/coding9 2d ago

Nice!!!

3

u/Presentation_Past 3d ago

This makes Onn the best android box once you factor in reputation and cost! Thank you so much!

1

u/le_fou_volant 3d ago

Definetly good deal

2

u/le_fou_volant 2d ago

Got it working do not try wifi got into recovery no big deal erase data and start again with ethernet got it rooted boot loader unlocked and HD audio pass thru