Plasma Mobile Documentation Website issueshttps://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues2020-12-10T16:03:20Zhttps://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/14Missing rootfs_stamp and other issues with the pm-flash and rootstock-touch-i...2020-12-10T16:03:20ZJames RichardsonMissing rootfs_stamp and other issues with the pm-flash and rootstock-touch-install scripts (Documentation Opportunity)I'm attempting install on a Nexus 5X (bullhead) and when running the pm-flash utility, the script checks for the latest rootfs version by curl-ing the URL: "https://images.plasma-mobile.org/rootfs_stamp" (Line 55)
This step fails becaus...I'm attempting install on a Nexus 5X (bullhead) and when running the pm-flash utility, the script checks for the latest rootfs version by curl-ing the URL: "https://images.plasma-mobile.org/rootfs_stamp" (Line 55)
This step fails because that rootfs_stamp file does not exist in that web folder.
![curl_error](/uploads/a3961f669aac3f85bf421ff74feb9ea5/curl_error.png)
![rootfs_stamp_url](/uploads/e7f81cd4d367a632a5900ee657e4d456/rootfs_stamp_url.png)
I am able to update the script, bypassing the version check and plugging in the latest version manually into the ROOTFS_VERSION variable assignment to get past this hurdle.
![ROOTFS_VERSION](/uploads/e99d686af9fd0a2e70cead4db7385b9f/ROOTFS_VERSION.png)
The next hurdle I hit is when it is done downloading the rootfs, system, recovery, and boot, and it reboots to TWRP recovery. I'm not sure if this is happening because I already had TWRP installed or if your recovery.img is TWRP, but when it boots, the /cache and /data partitions are already mounted. So the mount commands in the rootstock-touch-install script (lines 41-49) fail with a device or resource busy.
![mount_error](/uploads/e64d754b873a898372d0c2e2df070e03/mount_error.png)
If I modify the pm-flash script further by replacing the "wait_for_device" function call at line 93 with a "read -p" pause to give myself a chance to go into TRWP and unmount those two partitions, then when I let the script continue, it gets through those mounting commands and the script continues through to my next hurdle.
For my last hurdle, the fetch-demo.sh script called in the rootstock-touch-install script (lines 159-165) always runs. There does not seem to be any IF statement to let us specify if we want demo content or not. And the fetch fails because of a 404 error.
![demo_fetch_error](/uploads/1efb99f57ca4a7f35be40835eaf09c8f/demo_fetch_error.png)
If I comment out that section of the rootstock-touch-install script to prevent it from downloading the demo data, the pm-flash script completes all steps without any errors. Unfortunately, my bullhead device fails to boot. It is just stuck at the Google boot-logo screen. I can reboot it into recovery but that is it.
Then I found this thread: https://forum.kde.org/viewtopic.php?f=297&t=150546 that pointed me to the flash_vendor script included in the pm-flashtool folder. I ran that script, then re-ran my modified pm-flash script and all is good!https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/3Move FAQ to plasma-mobile.org2019-11-11T07:31:11ZBhushan ShahMove FAQ to plasma-mobile.orgIn general current FAQ we have is more suitable for the plasma-mobile.org repo, move it to websites/plasma-mobile-org> repository which uses jekyll.
We might keep FAQ page for development related queries.In general current FAQ we have is more suitable for the plasma-mobile.org repo, move it to websites/plasma-mobile-org> repository which uses jekyll.
We might keep FAQ page for development related queries.