If your device isn’t bricked, you are safe and can wait for 9.2.4.2 being released.
2 Likes
In the CE settings it is listed as “9.2.4”.
As soon as you select this entry, you will see the full version number.
1 Like
Thank you relkai. I make a habit of doing a backup every time I change any settings or update my library, even though CoreELEC will not allow me to update the library. I now do that in Android and then perform the backup in both Android and CoreELEC.
Well these are my 2 cents’ worth of experience.
I had a A95X F1 with Android 8 2G+16GB with S905W. Installed 9.2.4.1 wifi not working. 9.2.3 worked well. I then used installtointernal and it did worked. I could then boot from internal emmc. I then tried to update from 9.2.3. to 9.2.4.1 NG using instructions (Copy NG tar 9.2.4.1 in .update e created .compat file on the internal install). It updated but not booting (I read the instructions that no way an update is possible for internal install one minute later than needed).
I could anyway boot from SD 9.2.4.1 NG. I then tried to use the ceemcc -x option to reinstall to internal in single mode (option 3) but this time it failed
Free space of ‘partition CE_FLASH’: 512MB
Warning: Could not find ‘dtbo’ partition!
Warning: Could not find ‘dto’ partition!
Free space of ‘partition CE_STORAGE’: 14352MB
Used space of ‘/flash’: 221MB
Used space of ‘/storage’: 231MB
There is enough free space on eMMC for installation!
Install CoreELEC on eMMC.
Continue? [y]: y
Moved ‘env’ from offset 0x000027400000, size 0x000000800000 to offset 0x000000400000
Moved ‘misc’ from offset 0x000031c00000, size 0x000002000000 to offset 0x000006400000
Moved ‘logo’ from offset 0x000028400000, size 0x000002000000 to offset 0x000008400000
Starting to format the new ‘CE_STORAGE’ partition…
mke2fs 1.45.3 (14-Jul-2019)
Discarding device blocks: done
Creating filesystem with 3674112 4k blocks and 920272 inodes
Filesystem UUID: 3885cd1b-1990-4e5c-8430-e2da54d18b79
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Starting to format the new ‘CE_FLASH’ partition…
mkfs.fat 4.1 (2017-01-24)
Stopping Kodi before start of copy process!
Starting copying of data to the eMMC!
Please do NOT interrupt this progress till it’s finished!
Copy all data from ‘/flash’ to ‘/media/CE_FLASH’
221.30M 100% 16.40MB/s 0:00:12 (xfr#66, to-chk=0/69)
Syncthing, please wait…
Copy all data from ‘/storage’ to ‘/media/CE_STORAGE/coreelec_storage’
231.07M 99% 9.41MB/s 0:00:23 (xfr#4663, to-chk=0/5531)
Syncthing, please wait…
Start Kodi again to have a user interface!
Success!
You can now power off the device, remove the used boot media (SD or USB) and
power on again to boot the device from eMMC!
Well it didn’t BOOT!
======= TRIED AGAIN BOOTING FROM SD 9.2.4.1 NG
CoreElec:/ # ceemmc -x
Starting CoreELEC eMMC installation tool…
System is not supported: gxl_p281_1g!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x0003ab400000 [16GB]
Existing CoreELEC single boot installation found on eMMC
Renew current CoreELEC single boot installation on eMMC
Use CoreELEC data from
[1] current used SD or USB device
[2] existing backup on current used SD or USB device
[3] Make a backup of current CoreELEC single boot installation on eMMC to current used SD or USB device
Please choose one option? [1/2/3]: 1
Usable space of ‘partition CE_FLASH’: 512MB
Used space of ‘/flash’: 221MB
There is enough free space on flash partition on eMMC for installation!
Warning!
ALL existing CoreELEC data on flash partition on eMMC will be lost!
nContinue with [y] or press enter to skip flash partition!
Continue? [y]: y
Starting copying of data to the eMMC!
Please do NOT interrupt this progress till it’s finished!
Copy all data from ‘/flash’ to ‘/media/CE_FLASH’
221.30M 100% 15.54MB/s 0:00:13 (xfr#66, to-chk=0/69)
Syncthing, please wait…
Usable space of ‘partition CE_STORAGE’: 14352MB
Used space of ‘/storage’: 231MB
There is enough free space on storage partition on eMMC for installation!
Warning!
ALL existing CoreELEC data on storage partition on eMMC will be lost!
Continue with [y] or press enter to skip storage partition!
Continue? [y]: y
Stopping Kodi before start of copy process!
Starting copying of data to the eMMC!
Please do NOT interrupt this progress till it’s finished!
Copy all data from ‘/storage’ to ‘/media/CE_STORAGE/coreelec_storage’
231.75M 99% 11.38MB/s 0:00:19 (xfr#4669, to-chk=0/5537)
Syncthing, please wait…
Start Kodi again to have a user interface!
Success!
Please remove current boot media (SD or USB) and
reboot the device to boot from eMMC!
======= REBOOT DOES NOT WORK FROM INTERNAL ONLY SD
======= REBOOT WITH 9.2.3 SD OK
======= TRIED INSTALLTOINTERNAL NOT WORKING ANYMORE (partitions broken?)
CoreELEC (official): 9.2.3 (Amlogic.arm)
CoreELEC:~ # installtointernal
One of BOOT, SYTEM, DATA or DTB partitions is missing.
Make sure that you are using a correct device tree and a device with internal me mory!
Not all devices are compatible with installtointernal due to unsupported NAND/eM MC
chips being used by some manufacturers.
LESSON LEARNED: READ CAREFULLY INSTRUCTIONS!
Anyway I enjoyed the effort and I’ll continue to read for future improvements. I ended up with a box without Android but I don’t care as long as the SD with 9.2.4.1. NG boots and works. Then when in a future ceemcc -x will be improved I will try again.
p.s. sorry for the long post!
p.s.s. I don’t blame the developers nor any other posting but me
I have no problem with ceemmc -x to install on a w95 box with 2GB Ram and 16GB Flash. I have also make the same error like you. i have install a -ng file over a non -ng build. -ng was installed but didn’t boot. After that, i boot via SD and install via ceemmc -x and corelec runs fine.
And i think you must install android first to use installtointeral again.
Hope this helps:
Requisites:
CoreELEC installed to eMMC in dual boot mode.
Procedure:
- Boot CoreELEC from same media (SD or USB) used for dual boot installation.
- From shell, execute ceemmc -x
After completion the box should boot to Android again.
Warning:
If single boot mode installation was used, the Android firmware has to be flashed back to the box.
More details can be found HERE.
I used installtointernal that cancel android first. I know I should have had an android firmware available to go back but I didn’t find any (can anybody direct me to a working a95x F1 firmware?).
All subsequent tries starting from SD simply didn’t work either using 9.2.3 and 9.2.4.1 NG.
I’m interest to know if you reinstall Android first before retrying with NG on SD.
I didn’t install the andoird before. I make a fresh install via ceemmc -x over my old defect update.
Thanks I found it. I’m installing Android and then I will try again starting with the NG version.
Please recover your Android image on the device and boot CE from uSD or USB.
Then run this cmd please:
dmesg | grep mmc | paste
Maybe on your Android device the dtb partition do have another unknown name.
When you had a internal install before on eMMC by the unsupported script installtointernal Android must be recovered to restore the original partition layout.
Thanks to all. I succeed in having 9.2.4.1 NG on internal only boot in a A95X F1 S905W 2+16GB.
As for your comment I don’t know if it’s still relevant. Let me know if you wish me to check it anyway.
Next task will be to see what I can do for a fake X96 mini that has S950L 1+16GB (instead of S905W 2+16GB) that at the moment is working on SD either with 9.2.4.1 without wifi and 9.2.3. with wifi. I wish to see if I can succeed in installing CE 9.2.4.1.NG internally. I’ll let you know.
I noticed the ‘Syncthing’ too - must be a typo surely?
Minor stuff but maybe someone might like to correct it while doing other work in there
FYI
I have a NextBox A95x- B7N 2/16 and got syspend working
Note:- I have previously flash an atvxperience rom (which I don’t use)
I enabled “inject bl301 blob” via Coreelect config menu, then
added the wake up code to config.ini
remotewakeup=‘0xe31cdf00’
decode_type=‘0x0’
remotewakeupmask=‘0xffffffff’
There is a software called Syncthing. But indeed this is a typo, although a good one.
1 Like
Awesome, thank you cycle8898 for passing this on.
I tested atvXperience on that box also. It was running pretty smooth to my recollection.
@Portisch maybe this is something for the next build?
I have a NextBox A95x- B7N 2/16 and got syspend working
Note:- I have previously flash an atvxperience rom (which I don’t use)I enabled “inject bl301 blob” via Coreelect config menu, then
added the wake up code to config.iniremotewakeup=‘0xe31cdf00’
decode_type=‘0x0’
remotewakeupmask=‘0xffffffff’
I posted earlier in the nightly thread that I’m sometimes having issues resuming playback from the main menu (Movies or Files dialog). The screen just freezes, nothing happens and after a while, Kodi returns to the main screen so it has crashed.
I was able to reproduce this problem by starting and resuming various items with debug logging enabled. The logfile is over 7MB so I just cut the last bit of it to https://pastebin.com/6bBCNMk4. That part has some playback, then I stopped the video and chose another one to resume but then Kodi crashed.
My box is a Odroid N2, Kodi 9.2.4.1.
Have you tried updating to 9.2.4.2 as a number of issues were fixed, including one regarding CEC that seemed to be be causing some lockups and slowness of operation at times.
I have seen what you had on my S905X2 box but they seem not to have come back after the update to 9.2.4.2.
1 Like
Yes the CEC bug slowed down the interface. Please update to 9.2.4.2.
Didn’t update yet, it probably wasn’t out yesterday evening as autoupdate didn’t prompt me. Of course, I’ll retest this one and it’s quite easy to reproduce since it seems to occur very often.
Does the bug also affect systems without CEC? And is it now possible to disable CEC in the settings? Previously it wouldn’t stay disabled.