Stuck with "could not unpack /e/ install archive" Easy-installer - FP3 - Windows - fastboot/bootloader

Hi guys how you doin?
Sorry for this but am not an expert and I feel I tried everything.

Everything goes smooth til the end of the wizard…where this message comes and so am I stuck.

Drivers installed (first manually downloading the package from /e/ site)
then via windows update:
“Google, Inc. - Other hardware - Android Bootloader Interface”
“Other Hardware - Android Composite ADB”
which I found out to be necessary or possible solutions.

Settings double checked

Device state - unlocked.

Tried to download a previous version of the package and put into the local folder (not working)

I am not sure about one step in the fastboot options but I can’t see it anymore as the wizard goes through automatically jumping to the final message where it can’t unpack.

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

Hi @spinkee welcome.

Let’s just rule out the drivers issue, there may be more than one set of drivers to update!

Are you aware of this HOWTO page?

Make sure you understood all of the above page first. Some Windows versions seem to behave differently but if you have a Windows Device Manager open while you work with Easy Installer, if your device changes to a “:warning: Update drivers” when you change booting mode, you will be alerted to update the drivers again! :slight_smile:

Do ask again, if it is not a drivers issue.

Hello @spinkee,

could you please provide the log file as described in Howto troubleshoot issues with the easy-installer

“could not unpack /e/ install archive”

I assume the installer stops after this error, right?

That would mean, it was able to detect that your have a FP3(+), download the correct installation archive, verify the download is not corrupted, but then is not able to extract the actual installation files from the install archive.

Without the log my first guess would be that you hard drive might be full? The install archive is around 1 GB. After extraction the files take another 2.2 GB on top.

2021-05-22 12:44:04,406 DEBUG [JavaFX Application Thread] e.e.i.EasyInstaller [null:-1]
OS name = Windows 10
Java Home = C:\Program Files\easy-installer
Current working dir = C:\Program Files\easy-installer
ADB folder path = C:\Program Files\easy-installer\bin\adb
2021-05-22 12:44:04,503 DEBUG [JavaFX Application Thread] e.e.i.EasyInstaller [null:-1] language = en, country = GB
2021-05-22 12:44:04,749 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] initialize()
2021-05-22 12:44:04,762 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(null)
2021-05-22 12:44:04,766 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] view title: before_mTitle
2021-05-22 12:44:05,002 DEBUG [JavaFX Application Thread] e.e.i.EasyInstaller [null:-1] Detected screen’s size = 1536.0 x 824.0
stage’s size = 1536.0 x 824.0
2021-05-22 12:44:21,256 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(beforeYouBeginRoot)
2021-05-22 12:44:21,589 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] view title: connect_mTitle
2021-05-22 12:44:25,925 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(connectDeviceRoot)
2021-05-22 12:44:26,227 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] view title: devMode_mTitle
2021-05-22 12:44:33,749 WARN [JavaFX Application Thread] e.e.i.c.s.EnableADBController [null:-1] imageName = enableADB10.png, error = java.lang.NullPointerException: Input stream must not be null
2021-05-22 12:44:35,538 WARN [JavaFX Application Thread] e.e.i.c.s.EnableADBController [null:-1] imageName = enableADB11.png, error = java.lang.NullPointerException: Input stream must not be null
2021-05-22 12:44:36,162 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] ResetNextButtonEventHandler()
2021-05-22 12:44:36,163 WARN [JavaFX Application Thread] e.e.i.c.s.EnableADBController [null:-1] imageName = enableADB12.png, error = java.lang.NullPointerException: Input stream must not be null
2021-05-22 12:44:36,517 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(enableDevMode)
2021-05-22 12:44:36,819 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] view title: checkDriverInstall_mTitle
2021-05-22 12:44:37,815 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] loadSubScene(checkDriverInstallation)
2021-05-22 12:44:38,130 DEBUG [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] view title: detect_mTitle
2021-05-22 12:44:38,138 INFO [JavaFX Application Thread] e.e.i.c.s.DeviceDetectedController [null:-1] startDetection()
2021-05-22 12:44:38,146 INFO [Thread-4] e.e.i.t.DeviceDetectionTask [null:-1] runADBDevicesCmd(C:\Program Files\easy-installer\bin\adb\adb)
2021-05-22 12:44:38,153 DEBUG [Thread-4] e.e.i.m.Command [null:-1] command: [cmd.exe, /c, ““C:\Program Files\easy-installer\bin\adb\adb”, “devices”, “-l””]
2021-05-22 12:44:38,186 INFO [Thread-4] e.e.i.m.Command [null:-1] Command’s Process started
2021-05-22 12:44:38,305 DEBUG [Thread-4] e.e.i.m.Command [null:-1]
(debug)List of devices attached
2021-05-22 12:44:38,306 DEBUG [Thread-4] e.e.i.m.Command [null:-1]
(debug)
2021-05-22 12:44:38,311 DEBUG [Thread-4] e.e.i.t.DeviceDetectionTask [null:-1] raw shell outputs =

don’t konw is that enough?
78 GB free space on the drive
The wizard doesn’t really stops, I could do “continuo” but nothin happens.
List of devices attached

In an ideal case you could upload the full log. Otherwise I can’t answer if it’s enough or not when I don’t know what comes afterwards.

Actually from your description I don’t really get the problem. In addition to the full log, could you also post a screenshot of the installer when your problem occurs?

In any case, if you have 78 GB free on your C: drive, my first assumption was not correct.

Thanks a lot for your support.
It’s not a driver problem as there is no signal under device manager - FP3, everything is working properly.
I have uploaded the full log on my cloud (I think)
https://ecloud.global/s/PcRmQFtTxogYHJX

how the log ends:

C:\Users>if errorLevel 1 (exit /b 102 )
exit value = 102

2021-05-22 16:16:28,677 WARN [Thread-8] e.e.i.t.FlashThread [null:-1] Exit value means: script_error_installFromFastboot_102
2021-05-22 16:16:28,677 WARN [JavaFX Application Thread] e.e.i.c.s.FlashSceneController [null:-1] onFlashError()
2021-05-22 16:16:28,678 DEBUG [JavaFX Application Thread] e.e.i.c.s.FlashSceneController [null:-1] errorMsgKey = script_error_installFromFastboot_102
2021-05-22 16:16:28,679 INFO [JavaFX Application Thread] e.e.i.c.s.FlashSceneController [null:-1] onFlashStop()
2021-05-22 16:16:28,679 INFO [JavaFX Application Thread] e.e.i.c.MainWindowController [null:-1] ResetNextButtonEventHandler()

Here the screenshot of the wizard

and of the phonephone

I think that Installer doesn’t like the “&” in your Windows user name (“AL&Gio”).
At bottom of log, it is searching for “C:\Users\AL”.

I’ll create another Windows user with a simple name (i.e. “EasyInstall”) and administrative rights, for Easy Installer :wink:

4 Likes

Thanks for providing the full log :slight_smile:

smu44 is fully right in the assessment and workaround.

In addition I’ve created an issue so that this gets fixed in the easy-installer: https://gitlab.e.foundation/e/backlog/-/issues/3228

1 Like

killer. it wooooorks!

2 Likes