Reply to topic

Nexus 5X stuck at Google boot screen

User avatar Ad5001
Registered Member
Posts
4
Karma
0
OS
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
Code: Select all
mount: mounting /dev/block/mmcblk0p40 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p45 on /data failed: Device or resource busy

adding android system image to installation ... __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!


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:
Code: Select all
ad5001@ad5001-Home-PC:~/Install/pm-flashtool$ ./pm-flash
+ 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: bullhead
finished. total time: 0.092s
++ fastboot getvar product
++ head -1
++ awk '-F: ' '{print $2}'
+ DEVICE_NAME=bullhead
+ confirm 'Connected device is bullhead, is that correct? [y/N]'
+ read -r -p 'Connected device is bullhead, is that correct? [y/N] ' response
Connected device is bullhead, is that correct? [y/N] y
+ case $response in
+ true
+ PLATFORM=neon
+ echo 'Continuing ...'
Continuing ...
+ getopts cp: opt
+ '[' -z '' ']'
+ download bullhead neon
+ '[' 2 -eq 0 ']'
+ mkdir -p cache/
+ pushd cache/
~/Install/pm-flashtool/cache ~/Install/pm-flashtool
+ echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
+ '[' neon == neon ']'
++ curl http://images.plasma-mobile.org/rootfs_stamp
+ ROOTFS_VERSION=20171113-152515
+ wget -c http://images.plasma-mobile.org/rootfs/pm-rootfs-20171113-152515.tar.gz -P rootfs
--2017-11-18 17:00:09--  http://images.plasma-mobile.org/rootfs/pm-rootfs-20171113-152515.tar.gz
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ ln -sf rootfs/pm-rootfs-20171113-152515.tar.gz pm-rootfs-latest.tar.gz
+ '[' neon == arch ']'
+ '[' neon == edge ']'
+ echo '[done]'
[done]
+ echo 'Downloading the latest boot, recovery, and system images  ... '
Downloading the latest boot, recovery, and system images  ...
++ curl http://images.plasma-mobile.org/halium/bullhead/halium_stamp
+ HALIUM_VERSION=20171014-100052
+ wget -c http://images.plasma-mobile.org/halium/bullhead/recovery.img -P bullhead
--2017-11-18 17:00:09--  http://images.plasma-mobile.org/halium/bullhead/recovery.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171014-100052/system.img -P bullhead/20171014-100052
--2017-11-18 17:00:09--  http://images.plasma-mobile.org/halium/bullhead/20171014-100052/system.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171014-100052/boot.img -P bullhead/20171014-100052
--2017-11-18 17:00:09--  http://images.plasma-mobile.org/halium/bullhead/20171014-100052/boot.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ ln -sf 20171014-100052 bullhead/latest
+ echo '[done]'
[done]
+ popd
~/Install/pm-flashtool
+ flash-phone bullhead
+ '[' 1 -eq 0 ']'
+ echo -n 'Flashing recovery image ... '
Flashing recovery image ... + fastboot flash recovery cache/bullhead/recovery.img
+ echo -n '[done]'
[done]+ fastboot boot cache/bullhead/recovery.img
downloading 'boot.img'...
OKAY [  0.488s]
booting...
OKAY [  0.551s]
finished. total time: 1.039s
+ 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 $'1\r'
+ echo

++ readlink -f cache/pm-rootfs-latest.tar.gz
+ ./rootstock-touch-install /home/ad5001/Install/pm-flashtool/cache/rootfs/pm-rootfs-20171113-152515.tar.gz cache/bullhead/latest/system.img cache/bullhead/latest/boot.img
[sudo] Mot de passe de ad5001 :
mount: mounting /dev/block/mmcblk0p40 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p45 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 ... __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxrwxr-x    2 system   system        4096 Feb 11  2016 anr
drwxrwx--x    2 system   system        4096 Feb 11  2016 app
drwx------    2 root     root          4096 Feb 11  2016 app-asec
drwxrwx--x    2 system   system        4096 Feb 11  2016 app-ephemeral
drwxrwx--x    2 system   system        4096 Feb 11  2016 app-lib
drwxrwx--x    2 system   system        4096 Feb 11  2016 app-private
drwx------    2 system   system        4096 Feb 11  2016 backup
drwxr-xr-x    2 shell    shell         4096 Feb 11  2016 bootchart
drwxrwx---    5 system   cache         4096 Feb 11  2016 cache
drwxrwx--x    2 system   system        4096 Feb 11  2016 connectivity
drwxrwx--x    2 root     root          4096 Feb 11  2016 dalvik-cache
drwxrwx--x    2 system   system        4096 Feb 11  2016 data
drwxrwxrwx    2 system   system        4096 Feb 11  2016 diag_logs
drwxrwx---    2 drm      drm           4096 Feb 11  2016 drm
drwxrwx---    2 system   system        4096 Feb 11  2016 fpc
drwxrwx---    2 system   system        4096 Feb 11  2016 fpc_tpl
drwxr-x--x    3 root     root          4096 Feb 11  2016 local
drwxrwx---    2 root     root          4096 Jan  1  1970 lost+found
drwxrwx---    4 media_rw media_rw      4096 Feb 11  2016 media
drwxrwx---    2 mediadrm mediadrm      4096 Feb 11  2016 mediadrm
drwxrwx--t   33 system   misc          4096 Feb 11  2016 misc
drwxrwx--t    2 system   misc          4096 Feb 11  2016 misc_ce
drwxrwx--t    2 system   misc          4096 Feb 11  2016 misc_de
drwxrwx---    3 nfc      nfc           4096 Feb 11  2016 nfc
drwxrwx--x    2 root     root          4096 Feb 11  2016 ota
drwxrwx---    2 system   cache         4096 Feb 11  2016 ota_package
drwx------    2 root     root          4096 Feb 11  2016 property
drwx------    2 root     root          4096 Feb 11  2016 ramdump
drwxrwx--x    2 system   system        4096 Feb 11  2016 resource-cache
-rw-rw-rw-    1 root     root     2097152000 Sep  5 10:08 rootfs.img
drwx--x--x    2 system   system        4096 Feb 11  2016 security
drwx------    2 system   system        4096 Feb 11  2016 ss
drwxrwxr-x    4 system   system        4096 Feb 11  2016 system
-rw-rw-rw-    1 root     root     194719744 Oct 14  2017 system.img
drwxrwx---    2 system   system        4096 Feb 11  2016 system_ce
drwxrwx---    2 system   system        4096 Feb 11  2016 system_de
drwx------    2 system   system        4096 Feb 11  2016 time
drwxrwx--x    2 system   system        4096 Feb 11  2016 tombstones
drwx--x--x    2 system   system        4096 Feb 11  2016 user
drwx--x--x    2 system   system        4096 Feb 11  2016 user_de
[done]
cleaning up on device ... [done]
rebooting into bootloader mode and flashing boot.img ... [done]
bshah
Registered Member
Posts
76
Karma
0
OS
Before you installed Plasma Mobile, Did you had Android 6 installed on device? If so, can you run the
Code: Select all
flash-vendor
script from flashtool repository?
User avatar Ad5001
Registered Member
Posts
4
Karma
0
OS
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.
User avatar Ad5001
Registered Member
Posts
4
Karma
0
OS
@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!
joergw
Registered Member
Posts
22
Karma
0
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
zambel
Registered Member
Posts
2
Karma
0
When your Android phone stuck on boot screen, first step you need to enter the Recovery Mode, then wipe cache partition, then you need to do a factory reset of your phone, at last try to reboot your phone.
mrbansal
Registered Member
Posts
1
Karma
0
Ad5001 wrote: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
Code: Select all
mount: mounting /dev/block/mmcblk0p40 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p45 on /data failed: Device or resource busy

adding android system image to installation ... __bionic_open_tzdata: couldn't find any tzdata when looking for GMT!


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


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.
jennifierfox
Registered Member
Posts
1
Karma
0
Wow, Really great post i enjoy it very much here I appreciating your knowledge keep sharing kindly check it out hanuman ji
User avatar cefre00
Registered Member
Posts
2
Karma
0
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]
User avatar cefre00
Registered Member
Posts
2
Karma
0
cefre00 wrote: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]


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. :(
fdotman
Registered Member
Posts
2
Karma
0
I have only experienced this once with my Infinix Note 4. The solution that helped me was downgrading the OS. You may want to try this on your Nexus when it cannot boot beyond the logo interface.
Showbox | Tutuapp |Gadgetswright.com |
Savetubes
rayadav
Registered Member
Posts
1
Karma
0
Just downgrade your operating system and the problem shouldb be solved. I faced this with my moto g5.
download nox

 
Reply to topic

Bookmarks



Who is online

Registered users: Akela, Baidu [Spider], Bing [Bot], daret, Exabot [Bot], farid, Google [Bot], Lachu, mhacthoun, nogge, sevendogsbsd, tbd, Yahoo [Bot]