Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

SOLVED: see below for the answer

I've had Ubuntu Touch on my 8gb Nexus 7 for a while now (from the day it was released). Today I wanted to go back to Android. However flashing the Nakasi-jdq39 image fails while erasing/flash the userdata section with error: file_write: write: No space left on device - also when I execute sudo fastboot format userdata.

This leads me to a set of questions/ideas of why this could be:

  • Does the Ubuntu Touch installer (esp. the very first version) change the partition table of device somehow? If so, how do I revert those changes?
  • Was Ubuntu Touch ever intended to be installed on an 8gb Nexus 7?
  • Has anyone else had similar/the same problems and how did they solve it?

Any help or idea is appreciated.

In an attempt to verify the "Ubuntu Touch changes the partition table" assumption I've listed said table, and it seems like there is no change.

$ sudo fastboot getvar all
(bootloader) version-bootloader: 4.18
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: 015d24a42a0ff610
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000180b00000
(bootloader) partition-type:userdata: ext4
finished. total time: 0.160s
$ echo $[$(printf "%d" 0x0000000180b00000)/1024/1024]

Although I still don't know what caused this error, at least I have my device back. Manually flashing system and userdata did the trick:

$ sudo fastboot flash system system.img 
erasing 'system'...
OKAY [  1.447s]
sending 'system' (471804 KB)...
OKAY [ 55.746s]
writing 'system'...
OKAY [ 34.717s]
finished. total time: 91.910s
$ sudo fastboot flash userdata userdata.img 
erasing 'userdata'...
OKAY [  7.360s]
sending 'userdata' (104289 KB)...
OKAY [ 12.352s]
writing 'userdata'...
OKAY [ 14.267s]
finished. total time: 33.980s
$ sudo fastboot reboot
finished. total time: 0.020s
share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.