ubuntu-phone team mailing list archive

[Ken Harris <kjh@xxxxxxxxxxx>]

Dunno.  fastboot seems to be complaining about "InvalidSize", but I
don't know why.

As you say, if your most recent "phablet-flash" ran OK , then this
should as well.  Basically the script finds the most recent device
file in the phablet-flash pool and then reinstalls it while adding
"datapart=/dev/mmcblk0p10" to the cmdline.


On Thu, Dec 19, 2013 at 10:23 AM, Florian Felgenhauer
<florian.felgenhauer@xxxxxxxx> wrote:
> I installed abootimg. Now I get this:
>
> partitions/boot.img
> writing boot image config in bootimg.cfg
> extracting kernel in zImage
> extracting ramdisk in initrd.img
> < waiting for device >
> creating boot image...
> creating boot image - 8833024 bytes
> sending 'boot' (8626 KB)...
> OKAY [  1.039s]
> writing 'boot'...
> FAILED (remote: (InvalidSize))
> finished. total time: 1.395s
> rebooting...
>
> The device does not reboot correctly!
>
>
> 2013/12/19 Ken Harris <kjh@xxxxxxxxxxx>
>>
>> The error indicates that it can find "abootimg", which is a tool to
>> read/write/update android boot images.
>>
>> On Fedora, do "yum install abootimg".  I don't know about Ubuntu, but
>> maybe something similiar.
>>
>> On Thu, Dec 19, 2013 at 6:55 AM, Florian Felgenhauer
>> <florian.felgenhauer@xxxxxxxx> wrote:
>> > Hey Ken,
>> >
>> > I got errors running your script:
>> >
>> > partitions/boot.img
>> >
>> > ./touch-tilipia-datapart-workaround.sh: 19:
>> > ./touch-tilipia-datapart-workaround.sh: abootimg: not found
>> > < waiting for device >
>> > cannot load 'zImage': No such file or directory
>> > error: cannot load bootable image
>> > rebooting...
>> >
>> > finished. total time: 0.020s
>> >
>> > Can you explain to me in more detail what your script is doing, or do
>> > you
>> > have any idea why it failed?
>> >
>> > Cheers
>> >
>> > Florian
>> >
>> >
>> > 2013/10/1 Ken Harris <kjh@xxxxxxxxxxx>
>> >>
>> >> FYI, I've attached a simple script to add "datapart=/dev/mmcblk0p10" to
>> >> the "cmdline" for tilipia.
>> >>
>> >>
>> >> On Tue, Oct 1, 2013 at 12:34 PM, Darren Paxton
>> >> <darren@xxxxxxxxxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> Brilliant News, Ken.
>> >>>
>> >>> charging my Tilapia as we speak to get it up and running.
>> >>>
>> >>> Darren Paxton
>> >>> Staticwave
>>
>> >>> On Tue, Oct 1, 2013 at 8:31 PM, Ken Harris <kjh@xxxxxxxxxxx> wrote:
>> >>>>
>> >>>>
>> >>>>
>> >>>> I got tilipia to boot!  Ubuntu Touch looks great!
>> >>>>
>> >>>> I added "datapart=/dev/mmcblk0p10" to the "cmdline".  This is a
>> >>>> workaround, but indicates that the problem is in the /dev partition.
>> >>>>
>> >>>> In "initrd" , /scripts/touch , in "mountroot", it searches /dev for
>> >>>> ""userdata UDA DATAFS USERDATA" , when it doesn't find it, it panics.
>> >>>> I
>> >>>> don't know exactly how to do fix this.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Wed, Sep 25, 2013 at 8:30 AM, Ken Harris <kjh@xxxxxxxxxxx> wrote:
>> >>>>>
>> >>>>> The 2 devices are nearly identical.
>> >>>>>
>> >>>>> The only difference I see is that the /data partition is mmcblk0p10
>> >>>>> on
>> >>>>> tilipia (Nexus 7 3G) and mmcblk0p9 on grouper (Nexus 7 wifi).  This
>> >>>>> can be
>> >>>>> hidden by using /dev/block/platform/sdhci-tegra.3/by-name/UDA to
>> >>>>> refer to
>> >>>>> the /data partition.
>> >>>>>
>> >>>>>
>> >>>>> On Wed, Sep 25, 2013 at 5:51 AM, Chris Johnston
>> >>>>> <chrisjohnston@xxxxxxxxxx> wrote:
>> >>>>>>
>> >>>>>> I don't believe that tilapia was ever a supported device. AFAIK you
>> >>>>>> would need to port to tilapia just like any other unsupported
>> >>>>>> device.
>> >>>>>>
>> >>>>>> cJ
>> >>>>>>
>> >>>>>>
>> >>>>>> On Wed, Sep 25, 2013 at 4:39 AM, Darren Paxton
>> >>>>>> <darren@xxxxxxxxxxxxxxxx> wrote:
>> >>>>>>>
>> >>>>>>> Ken,
>> >>>>>>>
>> >>>>>>> I and a few others have had the same problem, we've posted here
>> >>>>>>> but
>> >>>>>>> unfortunately we've had no further assistance. It would appear
>> >>>>>>> that tilapia
>> >>>>>>> is no longer a reference device despite documentation to the
>> >>>>>>> contrary. I'm a
>> >>>>>>> little disappointed in this as I bought the tilapia with the
>> >>>>>>> intention of
>> >>>>>>> getting ubuntu running on it and like you, I can only get earlier
>> >>>>>>> builds on
>> >>>>>>> it and these dont really do much.
>> >>>>>>>
>> >>>>>>> Anybody else on the list care to pick up the task of either
>> >>>>>>> helping
>> >>>>>>> tilapia owners debug this problem or taking the stance that its no
>> >>>>>>> longer a
>> >>>>>>> supported device otherwise other people are just going to have the
>> >>>>>>> same
>> >>>>>>> problem and its pretty frustrating to be posting content with
>> >>>>>>> nobody willing
>> >>>>>>> to help from the development team.
>> >>>>>>>
>> >>>>>>> Darren Paxton
>> >>>>>>> Staticwave
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On Wed, Sep 25, 2013 at 8:02 AM, Ken Harris <kjh@xxxxxxxxxxx>
>> >>>>>>> wrote:
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> Greetings,
>> >>>>>>>>
>> >>>>>>>> I'm trying to install Ubuntu touch on "Nexus 7 3G (tilipia)".
>> >>>>>>>> "phablet-flash" runs to completion, but then it doesn't boot : I
>> >>>>>>>> just get
>> >>>>>>>> the "Google" splash screen (with the "unlocked" icon).  "adb" is
>> >>>>>>>> active at
>> >>>>>>>> this point.  I did "adb shell" and looked a bit, but I don't know
>> >>>>>>>> how to
>> >>>>>>>> debug it.  One odd thing I notice is that "df" only reports
>> >>>>>>>> "/dev" and
>> >>>>>>>> "/run" being mounted.  Is there a log file?  Any tips on how to
>> >>>>>>>> debug would
>> >>>>>>>> be appreciated.
>> >>>>>>>>
>> >>>>>>>> This is "tilipia" (1st gen Nexus 7 w/ 3G).  It should work.  I
>> >>>>>>>> got
>> >>>>>>>> an old Ubuntu Touch to work (from July or so).  Also "Plasma
>> >>>>>>>> Active" runs
>> >>>>>>>> OK.  Android 4.3 runs great, so the hardware is fine.
>> >>>>>>>>
>> >>>>>>>> I ran "phablet-flash ubuntu-system -d grouper -b".  I've attached
>> >>>>>>>> the log file.  I've also attached a log file with debug :
>> >>>>>>>> "phablet-flash
>> >>>>>>>> ubuntu-system --no-backup -d grouper --debug".
>> >>>>>>>>
>> >>>>>>>> FYI, I'm running Fedora.  I install phablet-flash w/ "bzr branch
>> >>>>>>>> lp:phablet-tools".
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> 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
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> 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
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Chris Johnston <chrisjohnston@xxxxxxxxxx>
>> >>>>>> Software Engineer - Canonical Ltd.
>> >>>>>> www.ubuntu.com
>> >>>>>>
>> >>>>>> --
>> >>>>>> 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
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> 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
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> 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
>> >>>
>> >>
>> >>
>> >> --
>> >> 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
>> >>
>> >
>
>