** Changed in: ubuntu-nexus7
Assignee: Oliver Grawert (ogra) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091220
Title:
Document resizing and/or rebuilding 8GB image for 16GB/
This is probably a stupid question but where did you get simg2img and
make_ext4fs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091220
Title:
Document resizing and/or rebuilding 8GB image for 16GB
I'm not sure what the -J flag does on make_ext4fs but I've found it
created a smaller rootfs.img which allowed me to flash. I have 100%
failure rate using sparse, so I needed a file less than 700MB. Here was
my process for my 32GB Nexus 7.
simg2img raring-preinstalled-desktop-armhf+nexus7.raw tmp.
not defective but built in a special way using the android-fsutils which
create a sparse filesystem that gets turned into a "kind of normal" ext4
filesystem during flashing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Why does the resize2fs operation fail? It the root filesystem defective
in some way?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091220
Title:
Document resizing and/or rebuilding 8GB image for 16
for the manual repackaging, you use simg2img to convert the file into a
proper img, then mount the img file, copy the tarball from the mount
into a temporary dir and use make_ext4fs from the package to create one
using this temporary dir as input for an image of the appropriate size.
--
You recei
as dimitrijs listed above, the plan as discussed at UDS was to have usb-creator
do the repackaging, i would have started to work on this already but had to
burn my annual vacation days ;)
work on this will start soon.
--
You received this bug notification because you are a member of Ubuntu
Bug
How eaxactly would one go about using android-tools-fsutils to resize
the image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091220
Title:
Document resizing and/or rebuilding 8GB image for 16GB/3
If we published images in all three sizes, would the larger sizes just
be zero-filled to make up the space? that would be quite compressible,
wouldn't it? Seems you could just have 16gb.iso.gz that would be not
much larger than 8gb.iso.
--
You received this bug notification because you are a memb
There are multiple nexus7 sizes, but the generate image contains pre-
formatted fixed size filesystem (as required to flash it using android
tools).
The problem is that we don't want to generate 3 images (expensive buildtime,
download size, qa efforts).
On the other hand we do want to maximize an
** Changed in: ubuntu-nexus7
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091220
Title:
Document resizing and/or rebuilding 8GB image for 16GB/32GB variants
To man
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-nexus7-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091
It would be also great if the ubuntu-nexus7-installer rebuilds the image
for the actual storage capacity of the target Nexus 7.
** Also affects: ubuntu-nexus7-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-nexus7-installer (Ubuntu)
Importance: Undecided =>
13 matches
Mail list logo
