Consider this my "log" how I've transferred data from phone to phone (worked between two nexus 5 devices) without SD card
I hope it will be helpful for somebody - but I've basically used combination of two methods described before plus some man pages
NOTE: both devices have ubports image installed and are prepared for adb access ()

Source device

After connecting source device on PC commands in terminal as follows:

1. Reboot phone into recovery: adb reboot recovery
2. Acquire root: adb root
3. Activate shell: adb shell (command prompt will change to # sign)
4. Backup system-data (this will also create log files, that can be examined for possible errors) :
   tar -czpv -f /system-data.tgz /data/system-data/ >/system-data.out 2>/system-data.err
   NOTE: I've just put these files into root directory and it went just fine and pulled just one file into connected computer since adb has much better chance to transfer one big file without errors than many small ones
5. logout from shell to your terminal (Ctrl+D)
   NOTE: I am assuming computer is linux with root access etc.
   this sub-step can be done before step 3
   5.1 go to directory where backup data are to be stored in PC (using cd and mkdir commands)
6. transfer data from phone to PC adb pull /system-data.tgz
   6.1 it is good idea to have logs copied too adb pull /system-data.out and adb pull /system-data.err but it is not necessary
7. steps 3. to 6. repeat but with user-data instead of system-data excluding .cache folder
   (so commands will look like tar -czpv -f /user-data.tgz /data/user-data/ --exclude='*data/user-data/phablet/.cache*' >/user-data.out 2>/user-data.err, adb pull /user-data.tgzetc.)
   NOTE: data which can be transferred by MTP should be moved that way since process of packing can take quite long for user data and may even stop/fail (e.g. not stopping process, just waiting and overheating battery, because all outputs are transferred to log files) if there is not enough space for package

Destination device

1. Reboot phone into recovery: adb reboot recovery
2. Acquire root: adb root
3. Push archived data from PC to phone (root folder) adb push ./system-data.tgz / and adb push ./user-data.tgz /
   NOTE: in case of failure pushing both files and then unpacking both in adb shell it is possible to work the process "per partes" so following steps 4. and 5. will be done after each push and removing archive from phone (rm ./system-data.tgz in adb shell and then returning by Ctrl+D to PC shell)
4. Activate shell: adb shell (command prompt will change to # sign)
5. Extract archives tar -xzv -f /system-data.tgz and tar -xzv -f /user-data.tgz
6. Restart phone, unplug, recharge (battery will be probably rather low ) check data and switch SIM card

PS:

After finishing and documenting the process, I'we found out that WiFi settings has not been transferred to destination device those must be somewhere in .cache folder then (I don't really mind, messages, apps, contacts and other settings are quite enough for me)

@unisuperbox
thank you for all your decisions I could witness over these years of my more-less passive presence in this community, I consider them being very wise and bold (including this one), take care

Hi all,
the name is Peter Valachovič I am IT teacher from Slovakia, some years ago after finishing FIIT in Bratislava I've decided that I want to work on making world a better place, so I quit ERP systems maintaining and development and I teach on high school and help kids with studies in free time.

My phone of everyday use is Ubuntu BQ 5 HD, I was thinking about translations to Slovak even earlier, although I haven´t started yet. I´ll gladly help with testing apps and if I´ll have time (which is not really often) I can help with some apps development too

there is a possibility to use script /usr/share/ofono/scripts/offline-modem with parameter /ril_0 which will stop receiving signals from network, so typing in terminal:

/usr/share/ofono/scripts/offline-modem /ril_0

will turn off SIM1 ... and to say B-side as well

/usr/share/ofono/scripts/online-modem /ril_0 will trun it back on

if you want to manipulate SIM2 just use /ril_1 parameter for those scripts

use naming convention Tethering (which is "terminus technicus") instead of hotspot in system settings etc

@thepeter just to add that if /data doesn't contain system-data and user-data (better said it is just empty) thing that might help is on phone side mounting it by:

mount /data

that should help (thanks to people in telegram group for quick help)

There is a feature in android phones (motorola) which I would like to see in UT, it's starting a flashlight by shaking the phone.

I imagine that it would have to be probably implemented somewhere on layer of kernel, but don't know enough to say that it is doable or not ... is there anybody who does know? (and would agree on implementing this kind of feature)

PS: using sargo as daily driver, interested in jasmine_sprout and hammerhead as well

@billboy5690
this may shed at least bit of light (mostly part about being in recovery mode)
https://forums.ubports.com/topic/1683/migrate-data-from-device-to-device/19?_=1644615177730

@unisuperbox
thank you for all your decisions I could witness over these years of my more-less passive presence in this community, I consider them being very wise and bold (including this one), take care

Consider this my "log" how I've transferred data from phone to phone (worked between two nexus 5 devices) without SD card
I hope it will be helpful for somebody - but I've basically used combination of two methods described before plus some man pages
NOTE: both devices have ubports image installed and are prepared for adb access ()

Source device

After connecting source device on PC commands in terminal as follows:

1. Reboot phone into recovery: adb reboot recovery
2. Acquire root: adb root
3. Activate shell: adb shell (command prompt will change to # sign)
4. Backup system-data (this will also create log files, that can be examined for possible errors) :
   tar -czpv -f /system-data.tgz /data/system-data/ >/system-data.out 2>/system-data.err
   NOTE: I've just put these files into root directory and it went just fine and pulled just one file into connected computer since adb has much better chance to transfer one big file without errors than many small ones
5. logout from shell to your terminal (Ctrl+D)
   NOTE: I am assuming computer is linux with root access etc.
   this sub-step can be done before step 3
   5.1 go to directory where backup data are to be stored in PC (using cd and mkdir commands)
6. transfer data from phone to PC adb pull /system-data.tgz
   6.1 it is good idea to have logs copied too adb pull /system-data.out and adb pull /system-data.err but it is not necessary
7. steps 3. to 6. repeat but with user-data instead of system-data excluding .cache folder
   (so commands will look like tar -czpv -f /user-data.tgz /data/user-data/ --exclude='*data/user-data/phablet/.cache*' >/user-data.out 2>/user-data.err, adb pull /user-data.tgzetc.)
   NOTE: data which can be transferred by MTP should be moved that way since process of packing can take quite long for user data and may even stop/fail (e.g. not stopping process, just waiting and overheating battery, because all outputs are transferred to log files) if there is not enough space for package

Destination device

1. Reboot phone into recovery: adb reboot recovery
2. Acquire root: adb root
3. Push archived data from PC to phone (root folder) adb push ./system-data.tgz / and adb push ./user-data.tgz /
   NOTE: in case of failure pushing both files and then unpacking both in adb shell it is possible to work the process "per partes" so following steps 4. and 5. will be done after each push and removing archive from phone (rm ./system-data.tgz in adb shell and then returning by Ctrl+D to PC shell)
4. Activate shell: adb shell (command prompt will change to # sign)
5. Extract archives tar -xzv -f /system-data.tgz and tar -xzv -f /user-data.tgz
6. Restart phone, unplug, recharge (battery will be probably rather low ) check data and switch SIM card

PS:

After finishing and documenting the process, I'we found out that WiFi settings has not been transferred to destination device those must be somewhere in .cache folder then (I don't really mind, messages, apps, contacts and other settings are quite enough for me)

I just want to be sure, before investing money, that on nexus 5 I can have two bluetooth devices at the same time working together (meaning keyboard and mouse) because I already have BT keyboard and working Slimport adapter ... last thing from HW perspective I am missing is mouse

Did you get your Gemini PDA? I am considering that device, so if you have usable insigthts I would like to know as much as possible

use naming convention Tethering (which is "terminus technicus") instead of hotspot in system settings etc

on it (from scratch - be patient with me plz )

answer could be libertine manager (scope called desktop apps) into which you can install software running on PC (you have to have one) by this I would get VNC client on phone and running server on raspi and wifi, you can use phone as screen for it

the "PC" can as well be the same raspi where you can run some ubuntu distro if you have temporarily different screen and move vnc client to phone