Apols for the mega-post but I’m reposting this issue in a separate thread in the hope of obtaining more visibilty for NO no longer working on a supported box, and it appears the diagnosis may be involved.
Plus I don’t seem to get any notifications for any forum replies and it’'s very difficult to follow the -no mega-thread.
My Minix Neo U22-XJ boots into a white noise screen (static) with CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img.gz and using g12b_s922x_minix_u22xj.dtb.
I copied g12b_s922x_minix_u22xj.dtb from CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241220\3rdparty\bootloader\device_trees into root of the original CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img.gz image sd-card - and it booted!
In detail, the Minix splash screen showed, then the familiar white noise screen briefly, then the Corelec ‘New Order’ logo with the partition resizing progress txt, then it rebooted again, and the setup process started.
A suggestion was to use the revA dtb but the only ‘rev_a’ I could see in devicetree of CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250526-Generic.img was g12b_s922x_minix_u22xj_max_rev_a.dtb and mine is not the Max model.
My MINIX Neo U22-XJ downloaded the latest nightly (20250607), overwrote dtb.img with the its g12b_s922x_minix_u22xj.dtb and of course I got the static screen of death, so obvs it’s not yet fixed.
Is there anywhere else that I should be logging this, given this box is on the supported list at coreelec:minix [CoreELEC Wiki]? As before, if someone can advise how I can obtain useful debugging info, bearing in mind the SSOD appears before the CE logo, then I’ll do my best.
The only possibly useful piece of info was that I booted into the built-in Android to show the Neo U22-XJ firmware version - which is Build 20211105 - V008.
When back in CE I was rewarded by a green tint to everything, which I understand is something to do with Dolby Vision being activated by the built-in Android. But it went away after some more reboots.
The above works fine with CE21.2.
Happy to try any builds, but surely someone must know what has changed in the device tree since 20241220 build to prevent it booting?
@atirage21 helpfully extracted some of the relevant info:
Also there’s no issue with my TV as it displays 4k@60Hz fine with CE21.2.
Only as experiment try change this VOUT mode (with delete of “#”) in config.ini to and use newer dtb: In my case this test not helped me with short time noise.
vout=‘1080p60hz’
I tried this but no change was observed i.e. a still static noise screen on boot.
I also tried out a separate 4k monitor with the same results.
Next step is to try out the newer old builds as suggested by @vpeter below
1 - I only just saw your suggested post that was buried in the mega thread
2 - I didn’t relish the prospect of downloading up to 90 builds, extracting the dtb from each, having to go fiddle about with sd-cards and booting each to find out which one prevented the boot
3 - even the build which did boot successfully, I discovered had video and audio issues, which had not received any response
I was hoping that someone would chime in who had access to the changelist and do a quick search to find where changes were made to this model’s dtb.
As I said before I’m happy to provide logs etc. but thought that there would be an easier way of narrowing down the issues.
Try copy .tar file from archive (withou extraction) to .update and restart device. But you must started of trying step by step from 20. december 2024 and try all to 31.12.2024. In this week had many devices issues.
Tx for the help. (I will ignore the rudeness from elsewhere as I came here for support, and not to be sworn at and ridiculed.)
However please can you explain “copy .tar file from archive to .update and restart store”.
I can download the nightly build .tar file fine but I’ve no idea where .update is (I don’t see any folder on the CE sd-card except for ‘device_trees’) nor how to restart “store”.
No store, but device. Keyboard in my smartphone like changing words. Sorry. You are right, after create new sdcard booting system you see only one partition on sd cased, but after first start of coreelec is also second partion with hidded folder .update
In linux you need enable viewing of hidded folder. In windows is maybe need to use total commander or opensource double commander for viewing this folder.
The second partition is ext4 so not visible to Windows by default.
I followed the CE Update wiki page above and used the update folder SMB share as it seemed easiest. The only snag was that it said to use “the CoreELEC image or update file” but there’s no image and could only find an update.sh in the fodler structure, which didn’t seem likely. Then I recall you mentioned using the tar file (downloaded from Index of /Amlogic-no/CE-22/) so I copied that to the share, restarted CE and it updated fine!
After some trialling I found out that running the builds (and not just the dtb.img) from 20241220 to 20241230 not only booted but the audio and video were working again. It is the 20241230 update which prevents it booting (not even a static image screen) and presumably breaks audio and video too. I noted the g12b_s922x_minix_u22xj.dtb file went from 73K to 75K.
