ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #10133
Re: Unresponsive Nexus 4 after running ubuntu-device-flash this afternoon
As a workaround to get you going, have you tried forcing it back into the
bootloader with volumedown+power from an off state? From there you can
retry the command. I've had a similar experience recently, but retrying
seems to work most of the time.
On Thu, Oct 9, 2014 at 4:29 PM, Charles Kerr <charles.kerr@xxxxxxxxxxxxx>
wrote:
> Nexus 4 mako.
>
> It's stuck at the "Google" boot screen, can't even get it into the
> bootloader.
>
> Here were the commands leading up to this:
>
> charles@ghidorah:~$ adb reboot bootloader
> charles@ghidorah:~$ XDG_CACHE_HOME=/tmp ubuntu-device-flash
> --developer-mode --channel=ubuntu-touch/devel-proposed --bootstrap --wipe
> 2014/10/09 15:29:40 Expecting the device to be in the bootloader... waiting
> 2014/10/09 15:29:40 Device is |mako|
> 2014/10/09 15:29:42 Flashing version 275 from ubuntu-touch/devel-proposed
> channel and server https://system-image.ubuntu.com to device mako
> 2014/10/09 15:29:42 ubuntu-touch/utopic-proposed is a channel alias to
> ubuntu-touch/devel-proposed
> 955.23 KB / 955.23 KB [=============================
> ============================================================
> =====================================================================]
> 100.00 % 453.31 KB/s
> 44.56 MB / 44.56 MB [=============================
> ============================================================
> =========================================================================]
> 100.00 % 2.38 MB/s
> 319.58 MB / 319.58 MB [=============================
> ============================================================
> =======================================================================]
> 100.00 % 5.14 MB/s
> /tmp/ubuntuimages/gpg/image-signing.tar.xz
> /tmp/ubuntuimages/ubuntu-touch/devel-proposed/mako/version-275.tar.xz
> /tmp/ubuntuimages/gpg/image-master.tar.xz
> /tmp/ubuntuimages/pool/custom-ba77049bb9a0184744e4c3cf38a2fb
> 37407fca18e814a21da5bb972db8f188ad.tar.xz
> /tmp/ubuntuimages/pool/device-491606a4e1da693361cc4bc94e0f86
> eef43df481e70dea1d7f049b46ea97a5ce.tar.xz
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/gpg/image-signing.tar.xz
> to device
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/ubuntu-
> touch/devel-proposed/mako/version-275.tar.xz to device
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/gpg/image-master.tar.xz
> to device
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/pool/custom-
> ba77049bb9a0184744e4c3cf38a2fb37407fca18e814a21da5bb972db8f188ad.tar.xz
> to device
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/pool/device-
> 491606a4e1da693361cc4bc94e0f86eef43df481e70dea1d7f049b46ea97a5ce.tar.xz
> to device
> 2014/10/09 15:31:01 Start pushing /tmp/ubuntuimages/pool/ubuntu-
> 5c26bf7d28633ba6753c25feaf0f7c7a36a3cf7a7aabf546d4a914ca94acf59d.tar.xz
> to device
> 2014/10/09 15:31:01 Done pushing /tmp/ubuntuimages/gpg/image-signing.tar.xz
> to device
> 2014/10/09 15:31:01 Done pushing /tmp/ubuntuimages/gpg/image-master.tar.xz
> to device
> 2014/10/09 15:31:01 Done pushing /tmp/ubuntuimages/ubuntu-
> touch/devel-proposed/mako/version-275.tar.xz to device
> 2014/10/09 15:31:02 Done pushing /tmp/ubuntuimages/pool/custom-
> ba77049bb9a0184744e4c3cf38a2fb37407fca18e814a21da5bb972db8f188ad.tar.xz
> to device
> 2014/10/09 15:31:14 Done pushing /tmp/ubuntuimages/pool/device-
> 491606a4e1da693361cc4bc94e0f86eef43df481e70dea1d7f049b46ea97a5ce.tar.xz
> to device
> 2014/10/09 15:31:45 Cannot push /tmp/ubuntuimages/pool/ubuntu-
> 5c26bf7d28633ba6753c25feaf0f7c7a36a3cf7a7aabf546d4a914ca94acf59d.tar.xz.asc
> to device: free space on /cache/recovery is unknown
>
> I am able to "adb shell" into the device:
>
> $ adb shell
> initctl: unable to determine sessions
> initctl: unable to determine sessions
> phablet@ubuntu-phablet:~$ ls
> Documents Downloads Music Pictures src tmp Videos
>
> "adb reboot bootloader" does reboot the device, but the bootloader is
> never reached. The screen stays stuck on the black-and-white Google boot
> screen the entire time. ubuntu-device-flash just waits for bootloader mode.
>
> Any suggestions?
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References