Nexus 5: Not Booting #30
Comments
|
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Device or resource busy Same here it's not boot. Any advice? |
|
For now, plasma mobile image is broken on Nexus 5 (or any halium 5 device for that matter), I'll get around fixing it in upcoming days, sorry |
|
I await it |
|
Would like to give it a try as well. |
|
Hi there. Found following --> workaround <-- (not a solution!): REMEMBER: This is a bloody amateur workaround...sorry for this one ;-) WORKAROUND FOR MOUNTING-PROBLEM: PHASE A - in a shell: PHASE B - on your nexus 5 / hammerhead: PHASE C - back in the shell: --> at least the mounting errors should have disappeared. But I believe that this is not even the problem. WORKAROUND FOR BROKEN ROOTFS-IMAGE PROBLEM: In the 'pm-flash' script, you'll find lines like: On my nexus 5 I found working ROOTFS_VERSION=20180524-110808 Hope it works for you! Best regards, p.s.: Do not forget to format cache and userdata first and remove pm-flashes cached files: edit: |
|
Seems to work, thank you! |
|
What happen to new image, that's from may is pretty old. |
|
Hi, I have just bough a Nexus 5 and I'm trying to install plasma mobile for about 5 hours so far but nothing seems to work... I have tried using default script and also with "ROOTFS_VERSION=20180524-110808" workaround (always unmounting /data and /cache from TWRP before root password) from "5.1.1 (LMY48M)", "4.4.4 (KTU84P)", "6.0.1 (M4B30Z, Dec 2016)" (this one as OTA install too) as factory flash as explained here https://developers.google.com/android/images#hammerhead and even trying from a custom Android Oreo rom and also from Ubports Ubuntu Touch just to always end up in an infinite booting loop with "Google" and a lock image on the screen. I'm really surprised this haven't been fixed after 5 months being such a critical flaw, I mean, I don't intend to offend nor want to give you guys any pressure but there will be no new users willing to test, use, or anything within plasma mobile if they can't even install it in the first place. Does this mean hammerhead will be discontinued as supported device? or just a hard to fix bug, maybe? Any other workaround will be really appreciated. PS: I'm really interested on using plasma mobile for a really long time and now it seems I can't due this bug :'( |
|
Here are my kernel logs after a test. Looking a it, it seems it wasn't unable to mount root with any file system type, maybe a format issue? |
|
Okay, I found a way to make it boot by basically downgrading both First make sure you have Then follow @webwurli workaround (#30 (comment)) to downgrade if [ "$2" == "neon" ]; then
#ROOTFS_VERSION=`curl https://images.plasma-mobile.org/rootfs_stamp 2> /dev/null`
ROOTFS_VERSION='20180524-110808'Continue modifying this file and look for # This will change in future
echo "Downloading the latest boot, recovery, and system images ... "
#HALIUM_VERSION=`curl https://images.plasma-mobile.org/halium/$1/halium_stamp 2> /dev/null`
HALIUM_VERSION='20170623-085147'Once that is done, you can execute I guess Plasma's Hallium newest image broke Nexus 5 compatibility, might need to check latest changes to see what happens, maybe Lineage OS missing commit or something? who knows Hope you all enjoy your plasma experience as I'm doing right now! xD |
|
Thank you! Hopefully they update the official build guide with this workaround (or actually just fix the compatibility) soon. But question: is there a particular firmware version we should be using for D820? Or should we use the neon platform flag with the flash script? At least PM will boot on my device now, but it hangs after I open just 1 or 2 apps. I believe I’m on the latest 6.0.1, but I’ll reflash just to make sure. Or is PM really just that buggy? |
|
my way: add "sleep 30;" in pm-flash after and replace ROOTFS_VERSION, HALIUM_VERSION thank @ tato11
run pm-flash as root and unmount cache, data in twrp while waiting 30 seconds wait for the process to complete profit |
|
confirmed @Skit81 instructions work flawlessly with a stock out of the box refurbished nexus 5. Once you have an unlocked the nexus 5 and turned on the USB debugger then boot into fastboot and exec the following from the terminal after making the changed outlined by @Skit81 👍 sudo fastboot format cache; sudo fastboot format userdata; sudo ./pm-flash |
|
hi all, just wanted to add to this that after reverting to the latest 6.0.1 factory image (i was on 8) using the Google provided factory images, and after using the instructions above (not starting pm-flash as a superuser but as a normal user, so you can deselect the options under "mount" and then add your password), it worked! As soon as i updated the software in Discover though, i ended up in a bootloop, so had to reflash, so probably that's not supported yet (as many other functions, it's still a work in progress, but a great work in progress!) |
|
@bhush9 are we still don't have new images? |
|
Tried several installs on NEXUS 5 but all ended in a Google logo bootloop.... Any tricks anyone? |
|
One suggestion. postmarket os seems to indicate support for this device and
I believe they have a plasma varient.
…On Sun, Jan 5, 2020, 4:50 PM magdesign ***@***.***> wrote:
Tried several installs on NEXUS 5 but all ended in a Google logo
bootloop....
Tried with first installing:
Android 6
UBports
Any tricks anyone?
I guess the last working image was: 20180524-110808
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#30?email_source=notifications&email_token=ADT24WTSUBGLDKE2AWR6ZPDQ4JI2FA5CNFSM4FLNPBW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIEANLQ#issuecomment-570951342>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADT24WUO24Y5FCP7OFTMWRLQ4JI2FANCNFSM4FLNPBWQ>
.
|
|
@thenomemac |
|
No luck as well |
|
The Nexus 5 is not supported by the Plasma Mobile image based on KDE Neon anymore. The Website only mentions the nexus 5X for that reason. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, i try to flash plasma-mobile with pm-flash, the problem is stuck as google logo, without boot on plasma
Flash with android 6.0.0, 6.0.1 and LineageOS latest (android 7)
`
./pm-flash -p neon ✔ 258 19:00:31
CACHEDIR=cache
echo 'Waiting for device to be in the fastboot mode'
Waiting for device to be in the fastboot mode
fastboot getvar product
product: hammerhead
finished. total time: 0.000s
++ 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
PLATFORM=neon
getopts cp: opt
'[' -z '' ']'
download hammerhead neon
'[' 2 -eq 0 ']'
mkdir -p cache/
pushd cache/
~/Local/pm-flashtool/cache ~/Local/pm-flashtool
echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
'[' neon == neon ']'
++ curl https://images.plasma-mobile.org/rootfs_stamp
ROOTFS_VERSION=20180717-064515
wget -c https://images.plasma-mobile.org/rootfs/pm-rootfs-20180717-064515.tar.gz -P rootfs
--2018-07-23 19:00:40-- https://images.plasma-mobile.org/rootfs/pm-rootfs-20180717-064515.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|:443… 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-20180717-064515.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 https://images.plasma-mobile.org/halium/hammerhead/halium_stamp
HALIUM_VERSION=20170623-085147
wget -c https://images.plasma-mobile.org/halium/hammerhead/recovery.img -P hammerhead
--2018-07-23 19:00:40-- https://images.plasma-mobile.org/halium/hammerhead/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|:443… 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 https://images.plasma-mobile.org/halium/hammerhead/20170623-085147/system.img -P hammerhead/20170623-085147
--2018-07-23 19:00:40-- https://images.plasma-mobile.org/halium/hammerhead/20170623-085147/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|:443… 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 https://images.plasma-mobile.org/halium/hammerhead/20170623-085147/boot.img -P hammerhead/20170623-085147
--2018-07-23 19:00:41-- https://images.plasma-mobile.org/halium/hammerhead/20170623-085147/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|:443… 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.
rm -f hammerhead/latest
ln -sf 20170623-085147 hammerhead/latest
echo '[done]'
[done]
popd
~/Local/pm-flashtool
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.691s]
booting...
OKAY [ 0.117s]
finished. total time: 0.808s
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
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), 417052/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]
`
thanks.
The text was updated successfully, but these errors were encountered: