Just updated my nightly for the first time in a couple weeks on my N2 and I am now stuck in a bootloop. I’ve been going through the posts to try and find a solution before posting and saw something briefly mentioned about replacing the KERNEL.img and SYSTEM files with one from a previous build and I’m just making sure that is still the accepted fix or if it’s easier to just reflash the whole image? Sorry if this is a dumb question or not in the right place.
@ AnomanderRake508
You didnt mention what version?
I had boot loop on 22. Downloaded 23 and it worked OK. (H96 max 905x2)
I was actually trying to figure out the version so I didn’t misspeak. I just downloaded the update from the prompt saying that “a new update was available, would you like to download” and I didn’t pay close enough attention at the time to catch it. I’ve been going over the SD Card files to try and find something but couldn’t. I was just going to try the manual update by putting the update .tar in the .update folder but it says that folder is write protected so I’m trying to figure that out now. I’m just on Win 10 so it’s a pain dealing with Linux partitions.
I’d like to ask if something is the expected behaviour for the Ng Nightlies on the latest kernel because I’ve noted a difference from the stable version.
In stable, there is audio output from the jack socket of my S905x2 box as well as HDMI. As far as I can recall, this has always been so. In the nightlies, I can get audio from the jack by setting PCM audio but that stops HDMI sound. I can get HDMI sound by selecting HDMI in the sound settings but that kills the jack output.
I have to admit that the new way is more logical but it makes life with a telly, amp and speakers a bit more difficult. I like to turn my telly off when listening to music and have my amp fed from the telly (HDMI) and from the jack (for music). I’ve found a kodi addon called “audio profiles” that gets round this but it’s not quite as easy as the old way.
As I said at the outset, is the new behaviour the expected behaviour?
You dont need to deal with partitions.
Use Rufus and add the image to an sd card.
It should give a reboot prompt. The upgrade download is a .tar, not an img. Its expanded on boot and replaces the current files.
I always try to use the new image in case it includes changes to the dtb.
Also this way by swapping over SD cards you can go back to the old one if there are issues.
After nightly version, I noticed that the VIM3L LED is off after powering on. It worked in previous versions.
Use 20200226 nightly, x96 max plus 4g/32g box wifi can’t work again, It worked in previous versions.
We reverted that change, because bt doesn’t work stable on another s905x3 boxes.
You could try to update your Android and check if it could fix your issue or use temporary solution from this message:
By the way you said, WIFI works again, but I found that without WIFI driver, the system load is only 1.xx. With WIFI driver, the system load is between 4-5. thank you.
https://discourse.coreelec.org/t/nightly-builds-new/8409/750?u=lalacko
Now I checked, the 20200223 nightly still works fine. in later versions the status LED no longer works. I know it’s not the biggest problem, but if there is a solution it would be good.
Copy the dtb from the old build if you need the status LED.
1 Like
Do you have Android+CoreELEC?
Just CoreELEC on mmc.
Today my VIM3L has been updated with no problems.
mmc update or sd card??
Only mmc, no android just coreelec.
Hm. I have same result multiple times. Tonight i will try again with some directions from Adam.