plasma-phone-packaging / pm-flashtool

Tool for Flashing PM as LXC Container on top of CM
44 stars 27 forks source link

ACBF.INFO error trying to flash #47

Open wy1z opened 4 years ago

wy1z commented 4 years ago

Tried a few times to flash my Nexus 5, and switching between neon and arch - same results with acbf.info. I did contact the acbf.info webmaster who noted IBM forced the site down and the webmaster noted they would need to find time to rebuild it as python - but does it need to impact the initial install process at all?

Why not delay the last five lines of the process until after the initial install is done?

Also, per https://forum.kde.org/viewtopic.php?f=309&t=167287 other people have reported the same with their devices.

This is a show stopper.

Thanks.

./pm-flash -p neon

The file is already fully retrieved; nothing to do.

The file is already fully retrieved; nothing to do.

The file is already fully retrieved; nothing to do.

The file is already fully retrieved; nothing to do.

++ readlink -f cache/pm-rootfs-latest.tar.gz

[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.

wy1z commented 4 years ago

I got past it by installing apache2 on my Ubuntu system, then copying the ~/pm-flashtool/OUTPUT/Documents/PepperCarrotVol__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.

NebulaBC commented 3 years ago

I am having the same issue, and I tried the fix and it didn't work

michaelarz commented 3 years ago

Hi! Workaround of having the file on local web server worked for me. Thanks for the hint! For the google boot loop you could try ./flash-vendor I performed this step before, trying to solve the other issue, so after getting the acbf.info sorted everything worked.

michaelarz commented 3 years ago

Well, after update from Discover and reboot it stuck on Google screen. ./flash-vendor is not helping this time. Probably, flashing one more time will help, but only up to next update... Seems, plasma mobile on Nexus 5x is abandoned, going to flash latest lineageos now.