Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[suzu] Stuck at final reboot #1589

Open
jonnius opened this issue Nov 30, 2020 · 7 comments
Open

[suzu] Stuck at final reboot #1589

jonnius opened this issue Nov 30, 2020 · 7 comments
Labels
needs confirmation a bug that has not yet been confirmed or reproduced

Comments

@jonnius
Copy link

jonnius commented Nov 30, 2020

UBports Installer 0.8.0-beta (deb)
Environment: Ubuntu 20.04.1 LTS Focal Fossa linux 5.4.0-54-generic x64 NodeJS v12.16.3
Device: suzu
Target OS: (target os not yet set)
Settings: undefined
OPEN-CUTS run: https://ubports.open-cuts.org/run/5fc4e0299702a600079df026
Log: https://paste.ubuntu.com/p/M7mbd9QRnZ/

I installed the system on an Xperia X. I reach this screen:

Bildschirmfoto vom 2020-11-30 13-00-57

Why does it say "Rebooting to Recovery" if it was already successful? The phone is stuck at the Sony screen and does not reboot. After rebooting by holding the power key the system settings tell me I have the latest version installed though.

@NeoTheThird NeoTheThird added the needs confirmation a bug that has not yet been confirmed or reproduced label Nov 30, 2020
@NeoTheThird NeoTheThird changed the title Stuck at final reboot [suzu] Stuck at final reboot Dec 1, 2020
@NeoTheThird
Copy link
Member

Hmm, this is annoying, adb reboot recovery executed without error:

debug: running step: {"type":"adb:reboot","to_state":"recovery","fallback_user_action":"recovery"}
command: exec: {"cmd":["adb","-P",5037,"reboot","recovery"]}
debug: adb:reboot done

I'm assuming the point of failure is in the recovery on the device, so the installer pushed all the files to install over there, rebooted to recovery to start the install process on the device, and the recovery failed to reboot to system after it was done. Does that sound plausible? Was there any animation on the device screen before it got stuck? @fredldotme have you seen this behavior before?

Why does it say "Rebooting to Recovery" if it was already successful

That is a separate ui issue #1426.

@jonnius
Copy link
Author

jonnius commented Dec 1, 2020

Your theory might be correct. Unfortunately I didn't watch the device during the process, so can't tell whether it showed the install animation.

@NeoTheThird
Copy link
Member

I hope that's what it is. Because if we can't rely on the device to actually reboot if adb reboot gave us exit code 0, that's going to be really annoying.

@jonnius
Copy link
Author

jonnius commented Dec 1, 2020

I just tried again and could reproduce the issue. And yes, there was the Yumi install animation before it rebooted into the white SONY screen with (no LED), where it gets stuck.

@NeoTheThird
Copy link
Member

Hmm, the installer can't really detect when it's finished, so we can't do a hack. we'll have to fix the recovery.

@robiwan1
Copy link

Any hints in this issue? Installer finished successfully, but after the device shows ubuntu touch logo "Installing updates" it reboots and hangs in a boot loop with the white SONY screen...

@jonnius
Copy link
Author

jonnius commented Dec 15, 2020

Hold Pow, Vol+ and Vol- until it reboots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs confirmation a bug that has not yet been confirmed or reproduced
Projects
None yet
Development

No branches or pull requests

3 participants