i believe i found the answer: config PHYS_OFFSET in my device kernel code. [kernel code dir]/arch/arm/Kconfig: config PHYS_OFFSET hex "Physical address of main memory" if MMU depends on !ARM_PATCH_PHYS_VIRT default DRAM_BASE if !MMU default 0x00000000 if ARCH_EBSA110 || \ ARCH_FOOTBRIDGE || \ ARCH_INTEGRATOR || \ ARCH_IOP13XX || \ ARCH_KS8695 || \ ARCH_REALVIEW default 0x10000000 if ARCH_OMAP1 || ARCH_RPC default 0x20000000 if ARCH_S5PV210 default 0xc0000000 if ARCH_SA1100 help Please provide the physical address corresponding to the location of main memory in your system.

@tg78 It seems that your device is not connecting to ubports installer through adb. Did you unlocked phone bootloader ? Did you install adb drivers on PC ? Did you use a data capable usb cable ? Did you use USB 2.0 port on PC ? USB 3.0 is to avoid if possible. Did you try another usb cable/usb port ?

I would start here: https://gitlab.com/ubports/community-ports/android9/xiaomi-mi-a2/xiaomi-jasmine_sprout

@errors Glad you sorted it out, sorry again for my lack of coding knowledge.

@flohack I see... then it's not a complete necessity, thank you very much.

with respect to simg stuff, I think the only one you ever need is simg2img. see https://gitlab.com/JBBgameich/halium-install/-/blob/master/functions/core.sh#L21 with respect to android tools, I assume what you need is adb and fastboot tools PS: actually not everyone might needs simg2img. I think some android trees already create the image in ext fs format, then no conversion is needed. halium-install detects this, but in either case current halium-install will still check for the existance of simg2img upfront. Also, I think Samsung ports that install via heimdall don't use halium-install alltogether ... I don't know too much about Samsung ports. they may or may not need simg2img. Similar for fastboot. I think some vendors don't support fastboot but do smt else. Bottom line, if there is a way to fix instructions to provide simg2img, adb and fastboot, that would fix it for everyone without sweating the details

@lighty I solved only wi-fi problem right now

@darkc0der Do you know the code name of your device? If it is lancelot, then it's compatible... If not I guess it won't work unfortunately...

@moem First issue solved (hopefully) just the rest.

@gvine @gvine said in New(ish) Nokia Lumia Bootloader Exploit: Perhaps this will open the door for ubuntu touch to be ported over to the Lumia. ? see guide. >> http://allaboutwindowsphone.com/features/item/24245_Aguideforunlockingthebootloade.php It is a first step I guess. But there's still a long way to go before such a thing is even worth thinking about. The article does not intimate that there is even any other OS to be installed on the device after the bootloader is unlocked. No alternative OS means no work done on drivers, means nothing to talk to the hardware for Ubuntu Touch to use.

@carlo I surrender for now. Probably some dependencies are missing.

Now I'm stuck at a new point. Which is that android lxc won't start. The device gives me the following error when trying to start it manually: root@ubuntu-phablet:~# lxc-start -n android -F lxc-start: conf.c: mount_entry: 1858 No such file or directory - Failed to mount "tmpfs" on "/usr/lib/aarch64-linux-gnu/lxc/dev" lxc-start: conf.c: lxc_setup: 3335 failed to setup the mount entries for 'android' lxc-start: start.c: do_start: 1248 Failed to setup container "android". lxc-start: sync.c: __sync_wait: 59 An error occurred in another process (expected sequence number 5) lxc-start: start.c: __lxc_start: 1802 Failed to spawn container "android". The container failed to start. Additional information can be obtained by setting the --logfile and --logpriority options. In the dmesg log I already saw that the camera and audio will not work. But that is really something for later. First I want to get the GUI running or just the system in general. I also can't reboot the device through the shell anymore. Making your own system image definitely is the harder way to port UT.

@nero355 yes, twrp does f2fs

I search on github and found CyanogenMod/android_device_samsung_p5113. From this repo and cm.dependencies therein I suggest your manifest should look like <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="github" fetch="https://github.com/CyanogenMod/" /> <project name="android_device_samsung_p5113" path="device/samsung/p5113" remote="github" revision="cm" /> <project name="android_device_samsung_p5100" path="device/samsung/p5100" remote="github" revision="cm" /> <project name="android_kernel_samsung_espresso10" path="kernel/samsung/espresso10" remote="github" revision="cm" /> <project name="android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm" /> </manifest> I'm not sure if it has properly settle down sources needed for your devices, please check it carefully. Btw, note that the docs you mentioned works for halium>=7.1, which based on cm>=14. However the latest support for your device is cm12.1. It seems that you should at first adapt your source to fix some new features provided from cm14. It is a huge work ... （Yay... in fact that is what I have experienced on my device... lol)

@geoeducativa said in a query about the device: zte nubia z5s mini nx406e: Use Halium 7.1 or Halium 9.0 Depending on the version of android shipped with your device. If your device once shipped with Android 9 you better use Halium 9. If your device is newer you'll have to try Halium 10 but it's not mature as far as I know. For older devices unsupported when Android 9 was released you should use Halium 7.1 for Android 7. If your device is even older than that I will not recommand to port...

@makeixo There are non halium ports, like my MX4, and halium 5, 7 and 9. There is not already halium 10 ports.