Join GitHub today
UBports installation failure - help wanted #593
Steps to reproduce
Every time I run the installer, it stalls after flashing and installing the UBports Recovery Menu
Your 2018 video shows that at this point it should push a few more files to the phone and flash the system image.
The UBports Recovery menu comes up on the device, but in the installer, the circle spins and the text says:
"Waiting for device to enter recovery mode. Flashing recovery and boot images."
It will stay that way all night.
Logfiles and additional information
Every time the log reads the same way:
Pug interceptor registered successfully
(From here it looped back to the line:
debug: adb shell: echo 1
again. The loop will run all night. Each loop takes about 1 second.)
One time it got to a dialog box that I had never seen before. It contained this message:
Fastboot: Unknown error:
chmod u+x ubports-installer-0.1.21-beta-x86_64.AppImage
In this method the installer works as designed with the phone automatically detected, identified, and rebooted into Downloader mode. Curiously on starting the installer, the phone put up the dialog box asking to accept the USB debugging connection again even though the phone had previously accepted this computer. Perhaps it detected the su session as a unique device.
I'll leave this issue open a few days in case anyone wants to add comments.
I tried get the ubports-installer-0.1.21-beta-x86_64.AppImage working the way you described, but my hammerhead shows the old error behavior from above. Ending up in den UBports Recovery Menu and the Installer "waiting for device to enter recovery mode".
(Ubuntu 18.10 / ubports-installer-0.1.21-beta-x86_64.AppImage / hammerhead)
To your question: Yes, after the sudo -s i was logged in as root, but the same behavior.
The same problem occurred with Fedora 29, Windows 7 and Ubuntu 18.10.
SOLUTION (for my device): After some more research i installed lineageOS 14.1 on the hammerhead device and activated the developer mode again. After that the installation process with the ubports-installer-0.1.21-beta-x86_64.AppImage worked normally on Ubuntu 18.10. The last time I activated it the same way, but this time it worked correctly.
That's interesting. I figured my first failures were due to hammerhead being on LineageOS, so a UBPorts volunteer on Telegram recommended I flash back to stock. That didn't help either. I figured there were some permissions issues going on that caused the installer to halt. That's what gave me the idea to run the AppImage version as su. So there's something about switching back and forth between LineageOS and stock that is affecting the install. I also read a post that said the device isn't responding to the adb requests because app host does not have sufficient permission. Hence the su elevation, that for you, LineageOS liked, and for me, stock liked. I also had inconsistency with the Android device requesting the USB Debugging link due to the adb permissions.