Nexus 5X stuck at Google boot screen
Registered Member 
|
Having a fresh install of Plasma Mobile on a Nexus 5X, but after the process completes, the phones starts to boot, but gets stuck at the "Google" boot screen.
Thought I noticed some errors in the console, but they don't seem to be really fatal
I've tried reinstalling a few times, including trying to use arch instead of neon as distro to flash in plasma, I also tried clearing the cache. I don't have access to adb exept in the TWRP screen, but I can get the access to fastboot in fastboot mode. Do anyone know how to resolve theses issues ? Thanks in advance Btw, my full output:
|
Registered Member
|
Before you installed Plasma Mobile, Did you had Android 6 installed on device? If so, can you run the
|
|
Registered Member
|
No, it wasn't Android 6 but the 8 version. Does that change anything? Anyway, I reinstalled it afterwards but I'll try running the script tomorrow.
|
|
Registered Member
|
@bshah Well, after running this command, I got an another error screen (this time in red) telling me that my device is corrupted. I installed android 6.0 on it and then just retried. And then it worked! Thank you!
|
|
Registered Member
|
You may have a look at my solution, that I've described in the last post of this thread: viewtopic.php?f=297&t=139325&start=30
|
|
Registered Member
|
I was encountering this error while testing it on android 8 but that I downgraded to android 6 it worked smoothly. Must be some compatibility issues. |
|
Registered Member
|
Ok, so this is garbage:
https://www.plasma-mobile.org/neon-arch ... ce-rootfs/ I did the installation multiple times, without errors and my Nexus 5 is stuck at the boot screen. After wiping the cache partition and performing a factory reset, it tries to move from boot to the system, but gets back to the boot screen every time. Can someone please help to work this out to have this system working on Nexus 5? Thank you! Terminal: sudo ./pm-flash -c [sudo] password for [...]: + CACHEDIR=cache + echo 'Waiting for device to be in the fastboot mode' Waiting for device to be in the fastboot mode + fastboot getvar product < waiting for any device > product: hammerhead finished. total time: 0.042s ++ 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 + echo 'Option provided to use cache, not downloading files again' Option provided to use cache, not downloading files again + NOCACHE=1 + getopts cp: opt + '[' -z 1 ']' + 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 downloading 'boot.img'... OKAY [ 0.784s] booting... OKAY [ 0.117s] finished. total time: 0.900s + 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/w0lverin3/pm-flashtool/cache/rootfs/pm-rootfs-20180717-064515.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/mmcblk0p28 on /data failed: Device or resource busy transfering rootfs tarball ... [done] preparing system-image on device ... [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] cleaning up on device ... [done] Increasing the rootfs size to 4G ... 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: ***** FILE SYSTEM WAS MODIFIED ***** /data/rootfs.img: 66916/128000 files (4.1% non-contiguous), 417034/512000 blocks resize2fs 1.42.9 (28-Dec-2013) Resizing the filesystem on /data/rootfs.img to 1024000 (4k) blocks. The filesystem on /data/rootfs.img is now 1024000 blocks long. [done] [100%] /data/time/timekeep [done] rebooting into bootloader mode and flashing boot.img ... [done] |
|
Registered Member
|
I installed back the factory image and tried again, as somebody suggested, but the result is the same. If somebody could help build a system image I could install the components one-by-one with fastboot, but I don't know how to do that. 
|
|
Registered Member
|
Hi all,
I have tried today for the first time to install KDE Plasma and now I am facing the issue described in this topic (I had android 8.1 installed). My biggest problem right now is that when I connect my nexus 5x to PC via USB it is no longer detected by adb. When I run "adb devices" it shows that there are no devices attached. Is there any way to recover from this? All solutions I found online assume that you can use adb somehow to connect to the phone. In my case this is not working. Thanks |
Registered Member
|
Use
to list your phone. |
|
Registered Member
|
Came from LineageOS, same story. I even followed the install script by eye and hand executed the install steps. I could even chroot into the system image I had built from that tar. But on reboot, just "Google" boot screen. So I suspect the install only works for the one single case of Android 6, and I'm really not sure I want to go to the trouble of finding 6 (that's Marshmallow, right?) just so I can run this install on top of it....
|
|
Registered Member
|
You don't need to bother. It doesn't work for me from Android 6, either. I tried everything possible by now and yet nothing seems to work. Plasma Mobile is broken. I've given up on it. The developers have to address these huge issues to make it work. |
|
Registered Member
|
If anybody ends up at the bottom of this thread, I found out after all my other install efforts, the flash-vendor tool runs, pulls some bits from India, and then it booted!
|
|
Registered Member
|
It probably would be very helpful if you could elaborate on your experience in much more detail... |
|
Registered Member
|
Not sure what to add. If you follow the instructions, you'll end up with pm-flashtool from: https://github.com/plasma-phone-packagi ... shtool.git and after doing the install steps, that directory has: flash-vendor Run it, and it pulls some bits and flashes your phone (the vendor partition). Once I ran this step, my 5x booted into a working Plasma Mobile (well, the whole environment is pretty flaky and broken, but it successfully boots). |
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], kesang, Yahoo [Bot]
