← Back to team overview

ubuntu-phone team mailing list archive

bad news: I bricked my nexus 4 after making image writeable and updating saucy stable on it

 

adb shell
touch /userdata/.writable_image
reboot

apt-get update
apt-get install aptitude
aptitude
shift-U
g
g

It downloaded everything.  Installed everything, but I got this error
along the way.

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-touch
dpkg: warning: version 'touch' has bad syntax: version number does not
start with digit
grep: /boot/config-touch: No such file or directory
WARNING: missing /lib/modules/touch
Device driver support needs thus be built-in linux image!
FATAL: touch: not absolute path.
ERROR: could not open directory
/tmp/mkinitramfs_lWoWIN/lib/modules/3.4.0-3-mako: No such file or directory
FATAL: could not search modules: No such file or directory
reading ramdisk from /boot/initrd.img-touch
Writing Boot Image /dev/disk/by-name/boot
Press Return to continue.

I rebooted and now I'm stuck on the Google boot with the little unlock
icon at the bottom of the screen..

I bricked it.  It's official.

I managed to get it into fastboot mode so I need to reflash everything
from scratch again. android 4.2.2/supersu/multirommanager/ubuntu
touch(was stable now devel channel).

What should I not update in order to prevent this from happening again?
 I would have liked to update the system and install a few other things.
i.e. emacs-nox, poppler, document viewer...
How does everyone else update their phone stuff?

Cheers,
David Marceau



Follow ups

References