Tried a few times to flash my Nexus 5, and switching between neon and arch - same results with acbf.info. Might that site work tomorrow? See last two lines.

With out success of that site, my flashing fails.

Thanks.


./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.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
+ PLATFORM=neon
+ getopts cp: opt
+ '[' -z '' ']'
+ download hammerhead neon
+ '[' 2 -eq 0 ']'
+ mkdir -p cache/
+ pushd cache/
~/Downloads/plasma/pm-flashtool/cache ~/Downloads/plasma/pm-flashtool
+ echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
+ '[' neon == neon ']'
++ curl https://images.plasma-mobile.org/rootfs_stamp
+ ROOTFS_VERSION=20200212-130311
+ wget -c https://images.plasma-mobile.org/rootfs ... 311.tar.gz -P rootfs
--2020-08-03 18:36:47-- https://images.plasma-mobile.org/rootfs ... 311.tar.gz
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

The file is already fully retrieved; nothing to do.

+ ln -sf rootfs/pm-rootfs-20200212-130311.tar.gz pm-rootfs-latest.tar.gz
+ '[' neon == arch ']'
+ '[' neon == edge ']'
+ echo '[done]'
[done]
+ echo 'Downloading the latest boot, recovery, and system images ... '
Downloading the latest boot, recovery, and system images ...
++ curl https://images.plasma-mobile.org/halium ... lium_stamp
+ HALIUM_VERSION=20181029-111411
+ wget -c https://images.plasma-mobile.org/halium ... covery.img -P hammerhead
--2020-08-03 18:36:48-- https://images.plasma-mobile.org/halium ... covery.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

The file is already fully retrieved; nothing to do.

+ wget -c https://images.plasma-mobile.org/halium ... system.img -P hammerhead/20181029-111411
--2020-08-03 18:36:48-- https://images.plasma-mobile.org/halium ... system.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

The file is already fully retrieved; nothing to do.

+ wget -c https://images.plasma-mobile.org/halium ... 1/boot.img -P hammerhead/20181029-111411
--2020-08-03 18:36:49-- https://images.plasma-mobile.org/halium ... 1/boot.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

The file is already fully retrieved; nothing to do.

+ rm -rf hammerhead/latest
+ ln -sf 20181029-111411 hammerhead/latest
+ echo '[done]'
[done]
+ popd
~/Downloads/plasma/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
Sending 'boot.img' (14524 KB) OKAY [ 0.680s]
Booting OKAY [ 0.117s]
Finished. Total time: 0.818s
+ 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/scott/Downloads/plasma/pm-flashtool/cache/rootfs/pm-rootfs-20200212-130311.tar.gz cache/hammerhead/latest/system.img cache/hammerhead/latest/boot.img
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p29 on /data failed: Device or resource busy
transfering rootfs tarball ... [done]
preparing system-image on device ... e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/data/rootfs.img: 11/128000 files (0.0% non-contiguous), 8049/512000 blocks
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /data/rootfs.img to 4096000 (4k) blocks.
The filesystem on /data/rootfs.img is now 4096000 blocks long.

[done]
unpacking rootfs tarball to system-image ... [done]
adding android system image to installation ... [done]
Setting up default password for phablet user to 1234 ... [done]
Cloning into 'fetch-demo-data'...
remote: Enumerating objects: 15, done.
remote: Counting objects: 100% (15/15), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 15 (delta 1), reused 15 (delta 1), pack-reused 0
Unpacking objects: 100% (15/15), done.
--2020-08-03 18:43:59-- http://acbf.info/download?id=0016
Resolving acbf.info (acbf.info)... 5.10.124.141
Connecting to acbf.info (acbf.info)|5.10.124.141|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-08-03 18:43:59 ERROR 404: Not Found.

Hey, I just ran into the same problem, just now trying out flashing KDE Mobile to my 5x. Finally worked through various bugs, and finally arrived here, to have a 404 webpage break the install.
I can troubleshoot scripts and files, but I can't do much about a webpage being down. Time to start investigating if that url is a typo for something else, perhaps?

The error is valid - I made contact with the webmaster who noted an issue with IBM and said they needed to find time to rewrite the web site with Python.

Until that gets done or the installer writer(s) find a way to possibly bypass the files the script requires of the abcf.info contact, it looks like we are stuck until the webmaster rewrites the web site with Python.

buhuuu.... typically IBM, same troubles here and today it's the 18th...
what to do? when bypassing the script-part I'm getting finally stuck up in a boot-loop (with ./flash-vendor)!

Same here on the 27/08/2020

Looks like it's forgotten for good now the pinephone is the new princess!!

I just messaged kdeneon on Facebook of the acbf problem - we'll see if they respond and with what.

I proposed the installer be reworked to possibly have the acbf removed and give the user the option to do it later.

We'll see if the FB message goes anywhere.

Same here, I am waiting for the fix.

I've ordered a Pinephone. giving up on the Nexus

I got past it by installing apache2 on my Ubuntu system, then copying the ~/pm-flashtool/OUTPUT/Documents/Pepper___Carrot___Vol__1.cbz which is created when the ./pm-flash tool is run in full, to /var/www/html/Download where the installer looks for the file.

Then, I updated my /etc/hosts file and created an entry of 127.0.0.1 acbf.info and the script completed fine.

It just left the Nexus 5 in the Google boot loop.

This being the year 2020, unless someone knows how to fix the boot loop, I've gone back to stock Android 6 to use the phone as a VLC player, and use my iPhone for the real stuff, at least for now.