Reply to topic

plasma mobile anwers..

ciro
Registered Member
Posts
1
Karma
0

plasma mobile anwers..

Wed Oct 04, 2017 7:54 am
hey guys,
I'm trying to install Plasma mobile on my nexus 5, but I'm not able to find much help online. There's a ton of unanswered questions, is the project discontinued? (nothing says so but nothing shows it's still going either.)
The error I keep getting is: "failed to create symbolic link 'pm-rootfs-latest.tar.gz': File exists".
I'm no developer nor a computer wiz..
help? anyone?
bshah
Registered Member
Posts
68
Karma
0
OS

Re: plasma mobile anwers..

Wed Oct 04, 2017 10:40 am
This project is very much active :-)

Can you try to remove the cache/pm-rootfs-latest.tar.gz file and retry?

Thanks
gr4n0t4
Registered Member
Posts
3
Karma
0

Re: plasma mobile anwers..

Fri Oct 06, 2017 10:31 am
Hi, I also have problems installing plasma, sorry if i´m not in the proper post or past of the forum.

I tried install plasma on my nexus 5 "hammerhead" on linux mint following the instructions https://plasma-mobile.org/nexus-5/ but when i reach the step 2 (i didn't specify platform) on the phone and appears the TWRP Recovery with a slide option to modify (i tried sliding and not sliding) but the console always show the same:
Code: Select all
$ ./pm-flash -c
+ CACHEDIR=cache
+ echo 'Waiting for device to be in the fastboot mode'
Waiting for device to be in the fastboot mode
+ fastboot getvar product
product: hammerhead
finished. total time: 0.000s
++ fastboot getvar product
++ head -1
++ awk '-F: ' '{print $2}'
+ DEVICE_NAME=hammerhead
+ confirm 'Connected device is hammerhead, is that correct? [y/N]'
+ read -r -p 'Connected device is hammerhead, is that correct? [y/N] ' response
Connected device is hammerhead, is that correct? [y/N] y
+ case $response in
+ true
+ PLATFORM=neon
+ echo 'Continuing ...'
Continuing ...
+ getopts cp: opt
+ case $opt in
+ echo 'Option provided to use cache, not downloading files again'
Option provided to use cache, not downloading files again
+ NOCACHE=1
+ getopts cp: opt
+ '[' -z 1 ']'
+ flash-phone hammerhead
+ '[' 1 -eq 0 ']'
+ echo -n 'Flashing recovery image ... '
Flashing recovery image ... + fastboot flash recovery cache/hammerhead/recovery.img
+ echo -n '[done]'
[done]+ fastboot boot cache/hammerhead/recovery.img
downloading 'boot.img'...
OKAY [  0.745s]
booting...
OKAY [  0.117s]
finished. total time: 0.862s
+ wait_for_device
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z $'1\r'
+ echo

++ readlink -f cache/pm-rootfs-latest.tar.gz
+ ./rootstock-touch-install /home/slimbook/plasma/pm-flashtool/cache/rootfs/pm-rootfs-20171004-112133.tar.gz cache/hammerhead/latest/system.img cache/hammerhead/latest/boot.img
[sudo] password for slimbook:
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
transfering rootfs tarball ... [done]
preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument
[done]
unpacking rootfs tarball to system-image ... tar: write error: No space left on device
[done]
adding android system image to installation ... [done]
cleaning up on device ... [done]
rebooting into bootloader mode and flashing boot.img ... [done]


And the result is nothing is install and i have to flash again android.

Any help would be apreciatted

Than you
joshlukas
Registered Member
Posts
1
Karma
0

Re: plasma mobile anwers..

Thu Oct 12, 2017 11:18 am
Have same problem as gr4n0t4. Stuck at an neverending bootloop after flashing:

Code: Select all
[lukas@antergos pm-flashtool]$ fastboot flash recovery /media/sf_E_DRIVE/01-Downloads/twrp-3.1.1-0-hammerhead.img                 
target reported max download size of 1073741824 bytes
sending 'recovery' (14604 KB)...
OKAY [  3.448s]
writing 'recovery'...
OKAY [  1.126s]
finished. total time: 4.574s
[lukas@antergos pm-flashtool]$ ./pm-flash -p neon
+ CACHEDIR=cache
+ echo 'Waiting for device to be in the fastboot mode'
Waiting for device to be in the fastboot mode
+ fastboot getvar product
product: hammerhead
finished. total time: 0.100s
++ fastboot getvar product
++ head -1
++ awk '-F: ' '{print $2}'
+ DEVICE_NAME=hammerhead
+ confirm 'Connected device is hammerhead, is that correct? [y/N]'
+ read -r -p 'Connected device is hammerhead, is that correct? [y/N] ' response
Connected device is hammerhead, is that correct? [y/N] y
+ case $response in
+ true
+ PLATFORM=neon
+ echo 'Continuing ...'
Continuing ...
+ getopts cp: opt
+ case $opt in
+ PLATFORM=neon
+ getopts cp: opt
+ '[' -z '' ']'
+ download hammerhead neon
+ '[' 2 -eq 0 ']'
+ mkdir -p cache/
+ pushd cache/
~/Documents/pm-flashtool/cache ~/Documents/pm-flashtool
+ echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
+ '[' neon == neon ']'
++ curl http://images.plasma-mobile.org/rootfs_stamp
+ ROOTFS_VERSION=20171011-131506
+ wget -c http://images.plasma-mobile.org/rootfs/pm-rootfs-20171011-131506.tar.gz -P rootfs
--2017-10-12 12:51:02--  http://images.plasma-mobile.org/rootfs/pm-rootfs-20171011-131506.tar.gz
Auflösen des Hostnamens images.plasma-mobile.org… 207.154.251.179
Verbindungsaufbau zu images.plasma-mobile.org|207.154.251.179|:80 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 416 Requested Range Not Satisfiable

    Download der Datei schon vollständig; kein Download notwendig.

+ ln -sf rootfs/pm-rootfs-20171011-131506.tar.gz pm-rootfs-latest.tar.gz
+ '[' neon == arch ']'
+ echo '[done]'
[done]
+ echo 'Downloading the latest boot, recovery, and system images  ... '
Downloading the latest boot, recovery, and system images  ...
++ curl http://images.plasma-mobile.org/halium/hammerhead/halium_stamp
+ HALIUM_VERSION=20170623-085147
+ wget -c http://images.plasma-mobile.org/halium/hammerhead/recovery.img -P hammerhead
--2017-10-12 12:51:03--  http://images.plasma-mobile.org/halium/hammerhead/recovery.img
Auflösen des Hostnamens images.plasma-mobile.org… 207.154.251.179
Verbindungsaufbau zu images.plasma-mobile.org|207.154.251.179|:80 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 416 Requested Range Not Satisfiable

    Download der Datei schon vollständig; kein Download notwendig.

+ wget -c http://images.plasma-mobile.org/halium/hammerhead/20170623-085147/system.img -P hammerhead/20170623-085147
--2017-10-12 12:51:03--  http://images.plasma-mobile.org/halium/hammerhead/20170623-085147/system.img
Auflösen des Hostnamens images.plasma-mobile.org… 207.154.251.179
Verbindungsaufbau zu images.plasma-mobile.org|207.154.251.179|:80 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 416 Requested Range Not Satisfiable

    Download der Datei schon vollständig; kein Download notwendig.

+ wget -c http://images.plasma-mobile.org/halium/hammerhead/20170623-085147/boot.img -P hammerhead/20170623-085147
--2017-10-12 12:51:03--  http://images.plasma-mobile.org/halium/hammerhead/20170623-085147/boot.img
Auflösen des Hostnamens images.plasma-mobile.org… 207.154.251.179
Verbindungsaufbau zu images.plasma-mobile.org|207.154.251.179|:80 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 416 Requested Range Not Satisfiable

    Download der Datei schon vollständig; kein Download notwendig.

+ ln -sf 20170623-085147 hammerhead/latest
+ echo '[done]'
[done]
+ popd
~/Documents/pm-flashtool
+ flash-phone hammerhead
+ '[' 1 -eq 0 ']'
+ echo -n 'Flashing recovery image ... '
Flashing recovery image ... + fastboot flash recovery cache/hammerhead/recovery.img
+ echo -n '[done]'
[done]+ fastboot boot cache/hammerhead/recovery.img
downloading 'boot.img'...
OKAY [  3.505s]
booting...
OKAY [  0.117s]
finished. total time: 3.621s
+ wait_for_device
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z $'1\r'
+ echo

++ readlink -f cache/pm-rootfs-latest.tar.gz
+ ./rootstock-touch-install /home/lukas/Documents/pm-flashtool/cache/rootfs/pm-rootfs-20171011-131506.tar.gz cache/hammerhead/latest/system.img cache/hammerhead/latest/boot.img
[sudo] Passwort für lukas:
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
transfering rootfs tarball ... [done]
preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument
[done]
unpacking rootfs tarball to system-image ... tar: write error: No space left on device
[done]
adding android system image to installation ... [done]
cleaning up on device ... [done]
rebooting into bootloader mode and flashing boot.img ... [done]

[lukas@antergos pm-flashtool]$
RichieM
Registered Member
Posts
1
Karma
0

Re: plasma mobile anwers..

Sat Oct 14, 2017 1:07 pm
I have the same error flashing tonight (14th Oct 2017 using the latest downloads) and the device is constantly rebooting as a result

Code: Select all
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
transfering rootfs tarball ... [done]
preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument
[done]
unpacking rootfs tarball to system-image ... tar: write error: No space left on device
[done]
adding android system image to installation ... [done]
cleaning up on device ... [done]
rebooting into bootloader mode and flashing boot.img ... [done]
gr4n0t4
Registered Member
Posts
3
Karma
0

Re: plasma mobile anwers..

Mon Oct 23, 2017 2:18 pm
It seems that we all have the same problem


Code: Select all
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy

preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument

unpacking rootfs tarball to system-image ... tar: write error: No space left on device
bshah
Registered Member
Posts
68
Karma
0
OS

Re: plasma mobile anwers..

Mon Oct 23, 2017 2:43 pm
gr4n0t4 wrote:It seems that we all have the same problem


Code: Select all
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy

preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument

unpacking rootfs tarball to system-image ... tar: write error: No space left on device


Can you edit this line to have bs=4096 instead of bs=8192 and retry?

https://github.com/plasma-phone-packagi ... nstall#L68

Thanks
gr4n0t4
Registered Member
Posts
3
Karma
0

Re: plasma mobile anwers..

Mon Oct 23, 2017 4:58 pm
bshah wrote:
gr4n0t4 wrote:It seems that we all have the same problem


Code: Select all
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy

preparing system-image on device ... mount: mounting /dev/block/loop0 on /cache/system/ failed: Invalid argument

unpacking rootfs tarball to system-image ... tar: write error: No space left on device


Can you edit this line to have bs=4096 instead of bs=8192 and retry?

https://github.com/plasma-phone-packagi ... nstall#L68

Thanks


It worked, still getting the message
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy

But not the
unpacking rootfs tarball to system-image ... tar: write error: No space left on device

So now it is installed. Thank you very much

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], bartoloni, Bing [Bot], CnZhx, dougjones, Exabot [Bot], fralex, ggael, Google [Bot], Gummidge, jehojakim2, metzman, noitibmar, Sogou [Bot], Yahoo [Bot]