Display MoreYa thats cool...
Still tho, even when loading CE or AE on a sd or stick to enable that those original installs on the box altered the existing factory bootloader ONCE to allow the device on reboot to now check for a bootable OS someplace other then just the internal flash... from the factory normally a box just boots up into Android but does have the ability to load outside sources which is how the Android recovery works...
To enable a off box bootable source tho there is a script in most builds that will alter the internal bootloaders setup to check elsewhere... essentially your telling the manufacturers u-boot to check other places then just internal memory and then saving those new settings into u-boots storage area so it can be used from that point forward anytime the device reboots. So even tho your still running CE or AE on external media they at one point in their original 1st boot made those alterations to u-boot on the device...
Once that intially happens normally you never need worry bout that anymore and just need to worry bout things like the proper dtb file for the device with its matching build...
With that in mind what i am getting at is that the method CE/AE and LE go about making the alteration to u-boots startup environment is no longer the SAME...
For along time seeing as historically CE/AE and others started life as Forks of LE that once any One of them were initially setup to run internally or externally the could all take advantage of U-boots altered environment...
As CE/AE now insist they aren't really LE forks anymore their way is Not supported by Balbes (LE) builds anymore as his scripts work slightly differently... tho i quess if one wanted to spend enough time analyzing the differences a common method could be done...
Personally even tho i have followed along for years and built all of the Distro's going back to and predating even OpenELEC which kinda started all of these types of frame works. I have a tool i created years ago that i use to create boot loaders for all of my projects on pretty much any Arm based device as i develop on ST and TI as well as the typical Amlogic or Rockchip SoC's that use Arm cores... I do RE work so i do a lot of messing around with proprietary Devices and SoC's but essentially they function in similar manners at the core...
Thank you very much for the reply.
You can explain to me then how is the process that you say Balbes:
"you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems."
What is "the USB Burn Tool"? Do I have to flash the Android? If so, it is too much for me to lose everything I have mounted in the box with Android. Is there another recovery method for boot boot?
Sorry for my ignorance.
Best regards.
