I will check that and if I have same problem, i will change it to update to the nightly from the 13th as well.
So I just checked. On the device that I used to test my script to update from the broken 20190911, I can run my script to update to 20190912, then shortly after rebooting into 20190912, I get an update notification for 20190913. I reboot to allow the new update to take place and it has no issue updating to 20190913.
edit: one thing to note about my script, is that it was only meant to update from the 20190911 build, so it leaves out several parts of the update process that just where just not needed between those two releases. If you modify it to update to other builds that may require these extra parts of the update process you may cause yourself problems.
when auto or putting file in .update folder wont update just sits on coreelec splash screen with no words in top left corner just sits and does nothing
See my post above regarding updates from 20190911 nightly build Post #1362
OK, thanks for the info.
What I will try now then is to copy the latest .tar file to the box and see if it fully updates when booted.
Update: No that didnât work.
Looking at your script though, it seems to replicate the original advice, which was to replace system and kernel.
Iâm struggling to know what will be the way forward to enable automatic updating to work, short of starting from scratch.
The only thing that does sit in my mind is that the original advice talked of going back to a build earlier than 11, so maybe that is the change required.
Canât hurt to try.
Update:
I thought that I would try to be clever (but failed).
I modified the script to pull down the normal nightly tar, starting with 10, rebooting and then with 12.
After 12 had been applied and the reboot complete I went through the process to do the automatic update to 13 via the prompt but things stuck again at the splash screen,
Modifying the script to point at 13 worked and it says I have 13, so for the time being Iâll pull updates down this way. It seems to do what a normal update does and can easily live with it.
How do u ssh
After last update, on 905x before show boot splash i see /init: line 986 tee not found and stack on splash
UPD: use 911fix.sh resolve this trouble.
Glad to say I formatted, installed stable and then installed 0912, then today updated to 0913 without issue. Good work.
1 Like
use WinSCP or Putty
I have updated to 0912 with the script, but now I have the same problem to update to 13 nightly
original script updated
https://discourse.coreelec.org/t/nightly-builds/1465/1362
and after all reboots please upload uname -a output and feedback if it works correctly for you
@gmx_201_2G
Linux CoreELEC 3.14.29 #1 SMP Fri Sep 13 00:31:14 CEST 2019 aarch64 GNU/Linux
THX A LOT WORKED
can we edit the scrip for 913 ?
it should download and update after next reboot correctly to 1309
Here you have the uname -a output:
CoreELEC:~ # uname -a
Linux CoreELEC 3.14.29 #1 SMP Thu Sep 12 00:32:18 CEST 2019 aarch64 GNU/Linux
CoreELEC:~ #
It updates to 0912, I have the notification of 0913 update but it doesnât install and freezes on bootlogo again
Bonjour,
I can not find the covers/infos of my new movies, do you know why? I did not change any settings âŚ
Vim3
What box do you have?
And does CE installed on sd/usb card?
I have a Tanix TX7 (s905x) 2/32 running CE from internal memory
So for anybody using internal memory with old style install2internal, (you know that thing some of the developers keep saying is not officially supported, and donât recommend doing), you have probably found that my script wonât work right with it, since the kernel lives in a different location on devices setup that way. If you have such an install you need to either manually update or run my script and then manually move /flash/kernel.img to correct location for your device.
And whatâs the correct location for kernel.img?
Can someone else confirm that once this broken kernel is embedded on your emmc you can no longer boot from USB. Makes expunging it a little tricky.
Shoog