search

plasma-phone-packaging / pm-flashtool

Tool for Flashing PM as LXC Container on top of CM
44 stars 27 forks source link

Nexus 5x: not booting #20

Open GabMus opened 6 years ago

GabMus commented 6 years ago

I have tried following the tutorial, did the following:

Then the device only gets stuck in a bootloop.

I also tried restoring the latest android 6.0.1 factory image and trying again, with no luck.

Any advice?

jbruechert commented 6 years ago

Did the script print any warnings or errors?

GabMus commented 6 years ago

Not that I remember. It just seems to work all the way to the end.

On Sun, Feb 11, 2018, 7:55 PM JBB notifications@github.com wrote:

Did the script print any warnings or errors?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/plasma-phone-packaging/pm-flashtool/issues/20#issuecomment-364777129, or mute the thread https://github.com/notifications/unsubscribe-auth/ABS6vyDOkMZdz6fCFXLshyosRxv-opxtks5tTzeggaJpZM4SBbr3 .

GabMus commented 6 years ago

Re-ran it, here's the complete log: https://hastebin.com/elupovineb.sql

bhush9 commented 6 years ago

ah mount: mounting /dev/block/dm-0 on /data failed: Device or resource busy

The issue is your /data partiton is encrypted, which doesn't work with the Plasma Mobile unfortunately.. so you need to format it (not just wipe) but format from recovery.

GabMus commented 6 years ago

cool, will try and report back. thanks

GabMus commented 6 years ago

Tried that and still doesn't work, but there is some progress: instead of a bootloop I get the black screen with the "Google" logo on it and the open lock on the bottom. Any attempt of interacting with the phone via adb doesn't work, it doesn't find the device.

bhush9 commented 6 years ago

it is possible that it is because you had android 6 installed previously so vendor image is mismatched, you can use flash-vendor script in same repo to install android 7 version, or install android 7/Lineage OS manually first

GabMus commented 6 years ago

will try, thanks

GabMus commented 6 years ago

Flashed on top of 6.0.1 stock image and it worked. Should I upgrade the vendor image to 7?

jbruechert commented 6 years ago

There is no visible flashing error if you flash on top of Android 6, but the drivers from Android 6 could fail to load in Plasma Mobile's Android 7 based adaption, which could lead to the screen staying black

lazmol commented 6 years ago

Hi, which android 6 factory image to revert to before flashing plasma mobile? https://developers.google.com/android/images#bullhead Thanks!

sluedtke commented 6 years ago

I had success with the last but one 6.0.1 (MTC20F) from

https://developers.google.com/android/images

colltoaction commented 6 years ago

Hi. I don't want to turn this into a support thread, but I'm facing similar issues.

My log looks suspicious (can't mount partitions. tar: write error: No space left on device), but nothing of the following helped:

Any ideas?? Here is the full log:

# ./pm-flash -c
+ 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: bullhead
finished. total time: 0.004s
++ fastboot getvar product
++ awk '-F: ' '{print $2}'
++ head -1
+ 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
+ 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 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.580s]
booting...
OKAY [  0.552s]
finished. total time: 1.132s
+ 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/user/pm-flashtool/cache/rootfs/pm-rootfs-20171005-145555.tar.gz cache/bullhead/latest/system.img cache/bullhead/latest/boot.img
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 ... tar: write error: No space left on device
[done]
adding android system image to installation ... [done]
Setting up default password for phablet user to 1234 ... chroot: can't execute '/usr/sbin/chpasswd': No such file or directory
[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: 111861/128000 files (5.2% non-contiguous), 512000/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]
colltoaction commented 6 years ago

I reverted https://github.com/plasma-phone-packaging/pm-flashtool/commit/04c166602b436370fccee005b6c543dcb0898b8b and my Nexus 5X flashed correctly!