Booting from SD card

[bingo600]

I had update on the Devel channel - and Dev 53 on my PP (eMMC) , and decided to try to boot from SD.


I have just downloaded the latest "Stable" from here  -  It says Stable 53 
https://ci.ubports.com/job/rootfs/job/ro...stemimage/

Unpacked , and wrote the img file to a Sandisk Ultra 32GB card w. etcher , no errors.
Inserted the SD in the PP , and did a started the phone.

When it booted, it asked for my "screen lock code" , and it was connected to my WiFi  
Now i'm in doubt if it has booted from the SD card at all, if it doesn't use the eMMC , how does it know my Screenlock code & wifi passwd ??
I somewhat expected it to boot up as "Factory reset" , or ??


My SIM card was not working, i had to go to Cellular settings and select my "provider number" 23xxxx  (Telia)
It was set to Auto , and 23xxx was listed below. Once i chose the 23xxx it connected to GSM , and showed Telia.

When i went into update settings - , and had a look it now shows stable, so something has happened.
And there was actually an update waiting, even though i just downloaded "latest"  - Where's the SHA-Sum of the file !!!!
The update is named Ubuntu Touch Version 3 , and i think that's the old Dev 53 , that @Luke promoted to Stable 2 days ago.

I guess my question is does the OS/PP have some persistent storage where it saves Screen & WiFi pwd's ?
Or does it "sneak read" from the eMMC, even if it is booted from the SD ?



Right now i'm updating my PP with the Stable 3 , that update said it found OTA.

More to come  

/Bingo

---

Wutt !!
After updating with the OTA , and reboot.

It now seems to be Factory reset.
The first thing i'm asked after the reboot is to set Language

Yupp , i just went through a "Factory reset setup" , Lang,TZ,Screen-pwd, WiFi-pwd".
Strange !!!  , is this intended behaviour , or just a "Quirk" ??

I downloaded Teleport (telegram) , and gets the verification code via sms , but it wont accept it.
I didn't see that issue on the eMMC install , but it could be app related.
Edit: On 2'nd try & SMS , it registered , even if it still said the sms code was too long


Well giving stable 3 a go today, and prob switch to Devel in the afternoon.

Once again thank you for your efforts

/Bingo

---

Hmm ....

Code:

root@ubuntu-phablet:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk2      179:32  0 14,7G  0 disk
├─mmcblk2p8  179:40  0  2,4G  0 part
├─mmcblk2p6  179:38  0 63,9M  0 part
├─mmcblk2p4  179:36  0  64M  0 part
├─mmcblk2p2  179:34  0    1M  0 part
├─mmcblk2p10 179:42  0  8,6G  0 part
├─mmcblk2p9  179:41  0  2,4G  0 part
├─mmcblk2p7  179:39  0 63,9M  0 part
├─mmcblk2p5  179:37  0 64,3M  0 part
├─mmcblk2p3  179:35  0    8M  0 part
└─mmcblk2p1  179:33  0  1,9M  0 part
mmcblk0      179:0    0 29,7G  0 disk
├─mmcblk0p9  179:9    0  2,4G  0 part /
├─mmcblk0p10 179:10  0  8,6G  0 part /userdata
├─mmcblk0p7  179:7    0 63,9M  0 part
├─mmcblk0p5  179:5    0 64,3M  0 part
├─mmcblk0p3  179:3    0    8M  0 part /android/persist
├─mmcblk0p1  179:1    0  1,9M  0 part
├─mmcblk0p8  179:8    0  2,4G  0 part /android/cache
├─mmcblk0p6  179:6    0 63,9M  0 part
├─mmcblk0p4  179:4    0  64M  0 part /android/boot
└─mmcblk0p2  179:2    0    1M  0 part
mmcblk2boot1 179:96  0    4M  1 disk
mmcblk2boot0 179:64  0


root@ubuntu-phablet:~# df -h
Filesystem                      Size  Used Avail Use% Mounted on
udev                            833M  4,0K  833M  1% /dev
tmpfs                          193M  804K  192M  1% /run
/dev/mmcblk0p10                8,4G  134M  7,8G  2% /userdata
/dev/mmcblk0p9                  2,3G  1,6G  596M  73% /
none                            4,0K    0  4,0K  0% /android
tmpfs                          964M  4,0K  964M  1% /etc/fstab
/dev/disk/by-partlabel/cache    2,4G  3,6M  2,3G  1% /android/cache
/dev/disk/by-partlabel/boot_a    45M  39M  2,4M  95% /android/boot
/dev/disk/by-partlabel/persist  476K  24K  428K  6% /android/persist
none                            4,0K    0  4,0K  0% /sys/fs/cgroup
tmpfs                          964M  7,0M  957M  1% /tmp
none                            5,0M  4,0K  5,0M  1% /run/lock
none                            964M  172K  964M  1% /run/shm
none                            100M    0  100M  0% /run/user
tmpfs                          964M    0  964M  0% /media
cgmfs                          100K    0  100K  0% /run/cgmanager/fs
tmpfs                          964M    0  964M  0% /var/lib/openvpn/chroot/tmp
tmpfs                          964M    0  964M  0% /var/lib/sudo
tmpfs                          193M  4,1M  189M  3% /run/user/32011
root@ubuntu-phablet:~#

root@ubuntu-phablet:~# ls /dev/disk/by-partlabel/ -l
total 0
lrwxrwxrwx 1 root root 15 Jun 20 09:13 boot_a -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Jun 20 09:13 boot_b -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 20 09:13 cache -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 20 09:13 loader -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 20 09:13 persist -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Jun 20 09:13 recovery_a -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 20 09:13 recovery_b -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 20 09:13 scr -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 20 09:13 system -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Jun 20 09:13 userdata -> ../../mmcblk0p10

Seems like there is a partition called /android/persist  - that according to lsblk is on the eMMC (if i read that correctly)