ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #13345
Re: Debian Chroot, was: Re: Bootloop after installing OTA4
hi,
Am Dienstag, den 16.06.2015, 22:00 +0200 schrieb Torsten Sachse:
> 2) Using phone only (not recommended since it breaks over the air updates)
> It is possible to install debootstrap on the phone by remounting the
> system as read-write and executing the following commands. At least it
> worked on my BQ on r22. Imagine you want to install your chroot into the
> directory "jessie" which should reside in the current working directory:
>
> sudo mount / -o remount,rw
> sudo apt-get update
> sudo apt-get install debootstrap
> sudo debootstrap --arch=armhf jessie ./jessie http://http.debian.net/debian
hmm, doesnt debian have minimal rootfs tarballs somewhere like
http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/wily-preinstalled-core-armhf.tar.gz
that way you could avoid the writable part completely (since you dont
need to install debootstrap)
>
> This only works on the internal storage without what's explained in
> section 4).
>
> 3) Using computer and phone
> The problem with this debootstrap-command failing your average computer
> is that your computer cannot execute binaries compiled for the ARM
> architechture. This is why you have to add the option --foreign to
> debootstrap which tells it to only download all packages and leave
> anything that needs executing of any of the installed binaries to
> another system. So do (sudo might not be needed):
>
> sudo debootstrap --arch=armhf --foreign jessie ./jessie http://http.debian.net/debian
sudo apt-get install qemu-user-static ...
then use qemu-debootstrap (takes identical args to debootstrap) so you
dont need to do all the --foreign dance, way easier (oh, and you can
chroot into the created dir too if you want to try out armhf stuff on
your pc or make changes, install extra packages etc)
> 4) Using an image file
...
this part is *absolutely lovely* ...
you should put it on the wiki somewhere :)
(or perhaps someone could script it in a way that you can just call it
with an adb enabled device attached) :)
ciao
oli
Attachment:
signature.asc
Description: This is a digitally signed message part
References
-
Bootloop after installing OTA4
From: Torsten Sachse, 2015-06-16
-
Re: Bootloop after installing OTA4
From: Nathan Haines, 2015-06-16
-
Re: Bootloop after installing OTA4
From: Torsten Sachse, 2015-06-16
-
Re: Bootloop after installing OTA4
From: John McAleely, 2015-06-16
-
Re: Bootloop after installing OTA4
From: Torsten Sachse, 2015-06-16
-
Re: Bootloop after installing OTA4
From: Simos Xenitellis, 2015-06-16
-
Re: Bootloop after installing OTA4
From: John McAleely, 2015-06-16
-
Re: Bootloop after installing OTA4
From: Torsten Sachse, 2015-06-16
-
Debian Chroot, was: Re: Bootloop after installing OTA4
From: Chris Croome, 2015-06-16
-
Re: Debian Chroot, was: Re: Bootloop after installing OTA4
From: Rodney Dawes, 2015-06-16
-
Re: Debian Chroot, was: Re: Bootloop after installing OTA4
From: Oliver Grawert, 2015-06-16
-
Re: Debian Chroot, was: Re: Bootloop after installing OTA4
From: Torsten Sachse, 2015-06-16