As Sholander posted
Is not reccomend
However you can through Network make a copy of your Addons Folder in working NE
Save to external media/or desktop.
Then after clean install can replace Addons in Folder or just copy n paste to Addons folder in new install.
Reboot
You should see
Addon migration in progress
Will take some time ,depending on how many Addons you have.
After completion, will have to navigate to Addons in system and Enable Addons
I installed no, but I get a lot of freezes, video shaking artifacts and networking issues.
I tried to prepare back microsd with ng version and it boots with âcould not mount labelâ error. Ne version works, but ng cannot boot anymore.
Did the no maybe change something in the bootloader of the box? I really want to have ng back again, but i canât get it working again. Should I reflash android from scratch on my box to get this working again?
I have been swapping back and forth a lot. I just use the backup option in coreelec. No thumbnails. Standard skin settings.
I use a fresh install ( I use a few 32Gb Samsung sd cards marked for each core type (NG, NE, NO)
I now have a a couple of H96 x2 and a couple of Tox3 X4.
I find NG to be the best option but not always the latest version.
I try out the latest builds from time to time on one card at a time but they are getting more niggly issues mentioned on all the other links for these builds.
I think NG 20241225 was the best one but I have moved on as I like to see what works for me.
I am hot having much luck with NO as I find general playback problems and my choice of remotes will not play ball with NO properly.
NG is always my fallback option.
When I drop the Backup into any build I always reboot a couple of times then go to ALL my addons dropdown and rerun each one even if auto update is on. Sometimes this seems to fix and Input adaptive etc errors. Same with the addon in Video addons on home page always go to its settings and rerun it drivers? from there.
I cannot not get NO on my H96 as it just wont load from scratch so I have stopped trying and only use NG on that.
Tox3 X4 runs best with NG or NE so for general movies etc we use one of those normally on NE.
If you want to try an earlier version of any go here
https://archive.coreelec.org/
The x96 x4 doesnât use a DV licensed SOC, thereâs no DV decoding ability.
I know. As I have a Samsung tv I use HDR.
Bloodhand did not mention DV.
Just responding to his question:
Thanks for your replies.
So why canât I boot ng anymore after having no installed? I will try to fully format the microsd before putting ng on it. If still not working, I will reflash android stock image from scratch, maybe the bootloader was somehow overwritten from the new kernel en so it doesnât accept the older kernel anymore? Boots with black screen no logo just error in mount_storage could not mount LABEL=COREELEC
2 posts were split to a new topic: Running an Ugoos AM6+ with OpenElec
Try CE-NO, nobody wants to invest time anymore in obsolete kernel CE-NG.
I managed to get working ng by first installing working ne and then create .nocompat file in update folder and copy the ng archive and reboot. I then tried fresh made microsd directly with ng and doesnât work I get the same error about mount. I donât want to check if reflashing stock android will help, because itâs to much work to reconfigure android. I hope stable no will soon be done and hope it will work with my box too.
Later edit: I tried this method again and the second time I get the same mount error. This is very weird, I donât understand why is this happening!
Android is fine
Just leave as is.
Grab another uSD Card or USB Flash Drive if you have one
Test NG on one
Test NE on the other
Really should test New Order 5.15.137
Reads like SD card is corrupt or not formatted correctly
Probably not a good idea to place ng tar file in NE update folderâŚ
Different kernelsâŚ
Use Different media to test Different versions of CoreELEC
Clean install only
Thanks for you reply. I just tested using 3 different SD cards.
ng boots ok letâs say 1 out of 20 tries, got some freezes the first 2-3 times, but then no problems anymore, closing HDR movies sends correct SDR signal back to TV so I get good colors without needing to reboot/power off.
ne boots ok everytime, only I need to power off/reboot after closing HDR movies, box goes back to SDR but doesnât send SDR signal back to the tv so I get wrong colors
no (CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250219-Generic) boots ok everytime, only I get frequent freezes so I need to cut the power to reset device and also video artifacts issues. Should I try another version?
I think itâs nothing wrong with the SD cards, maybe the ng kernel doensât work properly on my box, so that booting mostly fails when I try to load that.
I thought when loading fresh installed coreelec on sd card that some injection to the bootloader takes place which messes up trying to load older kernels. This is why I thought reflashing android from scratch would reset that. Or maybe I simply got lucky the first time I booted ng after ne (and before ever booting no) and got no boot issues.
Later edit: I was flashing using USBImager but reading some other topics suggested trying balenaEtcher. I did that and ng booted from first try.
Reading all the issues you have what works for thousands other users without any problem maybe the best solution is to sell the device and buy something working out of the box.
That box I would most definitely return to seller (or sell).
It is a 2 year old x96 x4 box. I had minor issues with this. I tested further ng doesnât boot up every time, guess issues with old kernel and my box, ne works every time. I will settle with ne for now and wait for stable no. Thanks guys for your help with troubleshooting.
Hi , is Dolby True HD working for you ? how did you connect media player - LG eARC - > soundbar. ?
did you set pass through ? or Auto
Please help me i am using LG C4
and also i am also facing freeze lag issues with new 2.2 whats the solution for this ?
which remote do you use for coreELEC LG or any other remote ?
A post was merged into an existing topic: White artifacts with S905X4 video decoder
âItâs dead Jim!â, âNo, it still needs more beating!â
So, i still think there has been not complete answer to what â(*) Generation Amlogic-ne cut-offâ means in coreelec:ce_dev_cycle [CoreELEC Wiki]
Yes, i get that CE-NG and CE-NE are âdeadâ (whatever that means), but the remark (*) is only behind specific SoC such as S905X4, but not after other SoC such as S922X. And S905X4 is not a dead/obsolete SoC, because itâs supported in all CE including CE-NO.
So, what does the (*) specific behind some SoC then mean ?
Is there any better way to file a bug against coreelec:ce_dev_cycle [CoreELEC Wiki] other than posting here ⌠and getting no answers ?
If that was a wiki i guess one could open a discuss three, but its not.
Btw: Just made the unhappy experience that CE-NG may not be the best of kernels (guessing).
Still donât understand how to officiall file bugs, especially when its clear they will not be solved, but just to ensure they are easier found than searching through these really long, confusing discussion threads.
Anyhow:
Suggestion: Try to avoid using the /storage partition on your device for media storage unless you are sure it does work rock solid. I for once had to figure out it does not work rock solid on my Dune-HD Homatics R 4k pro. I tried different USB3 flash drives with fresh installs to revalidate.
Test: write 5 GByte file to /storage/video
example: dd if=/dev/zero of=/storage/video/ZERO bs=10000 count=500000
Then try to read the file back
example: dd if=/storage/video/ZERO of=/dev/zero
This will after a while cause USB disconnect errors, and then of course also the CE partition itself becomes unavailable and you have to reboot.
Sure, this is a brute force test, but iâ've seen enough reports of problems during media ppay back, and you want to be sure that youâre not also having a problem with the storage you use.
Mileage may vary with USB2 sticks. Its slower, so timing problems may not happen there.
Works fine with current CE-NE, aka: pretty sure this has got something to do with linux kernel USB driver ( xhci-hcd).
Not too big an issue for me as i plan to only use NAS.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice