@rocket2nfinity That fixed the problem. There were some orphaned inodes found by e2fsck so that was exactly the problem you suggested. Thanks a lot.

@rocket2nfinity That fixed the problem. There were some orphaned inodes found by e2fsck so that was exactly the problem you suggested. Thanks a lot.

Hi,

I would like to ask you for a help.

My PinePhone UBports edition does not boot the OS - the PINE64 logo is displayed but then there is only black backlit screen and nothing happends for even 10 minutes. With power up button when starting the phone I get ubports logo with installing updates message. WIll I need to reflash the emmc or how should I proceed?

Thanks

@beegee
No problem, glad that it worked for you also in the end. By the way ubports community recently uploaded video on its official youtube channel where can be seen how it is supposed to be done:

https://www.youtube.com/watch?v=zuLFTGkuD68

@beegee...and click to start the process. The installer should start the recovery mode and do everything automatically.

@beegee Hi not sure if you install from windows or Linux but you should probably give admen rights to the tools you use purports-installer or fastboot). Remember to oem unlock the phone - see what tupp posted to thins thread. If the phone is unlocked you should see lock pictured under Google logo at boot. If the above is solved then IIRC you should get the phone to fast boot screen and run ubports-installer with admen rights. Choose the correct device if it is not auto selected

Then it is probably there - I only used ubports-flasher in the end. Maybe I am getting a little off topic here - but why are there so many mmcblk0p partitions from mmcblk0p1 to mmcblk0p29? Most of them are pretty small (used lsblk in terminal to get the list)..Also there seems to be separate 4M disk called mmcblk0rpmb--

@unisuperbox
Thank you for that information. I am happy that I did not try it before I saw your post. By the way does it mean that android binaries are still there on another partition? I just wonder if it booted to android if I locked it.

By the way can I and should I OEM lock the phone now?

Thank you so much. I am happily writing this message,from Ubuntu touch. The process was fast and automatic from that point. Everything seems to work. I had only one problem with browser the at first it was not accepting ssl certificates. Then I found out that time was not synchronized from wifi maybe it is synchronized only from operator by default. But I first booted without sim card. Because of wrong time browser considered certificate dates as invalid so the problem was easily fixed.

Thanks again for great support.
Andrej

I just want to add - the phone itself always shows only the google logo with a lock at the bottom just as tupp reported previously.

Thanks again
Andrej