It shows "cannot read 'sideload' " message during installing

Bug #1317371 reported by Ethan Chang
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
The Humpolec project
Fix Released
Medium
Ondrej Kubik

Bug Description

Milestone: M8
Device: Nexus4

Summary: Perform dualboot.sh to install dualboot on N4, and it shows "cannot read 'sideload'" during installing

1. Run ./dualboot.sh
2. It will reboot N4 and starting flash

Expected Result:
It will complete the installation and reboot to android

Actual Result:
It shows "cannot read 'sideload'" and stop to continue.
You will need to press "go back" and then it will retry to complete the sideload

Note:
Dev:04dbf50e910b4fe7: Waiting for adb recovery to be ready
Dev:04dbf50e910b4fe7: Creating update command
Dev:04dbf50e910b4fe7: Booting back to bootloader
Dev:04dbf50e910b4fe7: Waiting for fastboot to be ready
downloading 'boot.img'...
OKAY [ 0.267s]
booting...
OKAY [ 0.002s]
finished. total time: 0.269s
Dev:04dbf50e910b4fe7: Waiting for adb sideload to be ready
* cannot read 'sideload' *
Dev:04dbf50e910b4fe7: Waiting for adb recovery to be ready

Changed in humpolec:
status: New → Confirmed
importance: Undecided → Medium
Ondrej Kubik (ondrak)
Changed in humpolec:
assignee: nobody → Ondrej Kubik (w-ondra)
Revision history for this message
Ondrej Kubik (ondrak) wrote :

I tried this one and I can't reproduce it.
Can you reproduce this one every time?

Revision history for this message
Ethan Chang (ethan.chang) wrote :

@Ondrej
I can reproduce it on both N4 and N10 and I found that SuperSU doesn't installed, so when it try to install ubunt it will always fail

Note:
If use CM image then it won't happen this issue.

summary:
Revision history for this message
Ondrej Kubik (ondrak) wrote :

Can you put here more details please?
Is this N4 and N10 with factory image? ( mind you need to fastboot flash system system.img to make sure there is no remain of previous installation)
I have run $ ./dualboot.sh factory restored N4 and all went fine. Installed both SU and Ubuntu installer.

Revision history for this message
Stuart Langridge (sil) wrote :

I am upgrading -- I already have the previous Ubuntu dual boot system installed, and am experiencing this bug.

OK, I think the problem is that the app update is not actually being downloaded. Follow the bouncing ball:

If we specify "dualboot.sh update" (with explicit "update" parameter), we do this (lines 361-4):

    elif [[ "$ACTION" == update ]]; then
    echo "Dev:$DEVICE_ID: selected update install"
    download_app_update
    install_ubuntu_installer $UBUNTU_INSTALLER_PACKAGE

but if we do not specify a parameter, then we go into auto_mode (lines 372-3):

    echo "Dafaulting to auto action"
    auto_mode

and auto_mode then detects that an update is needed (lines 213-4):

        echo "selecting UPDATE mode"
        install_ubuntu_installer $UBUNTU_INSTALLER_PACKAGE

but note that it does not run download_app_update!

Explicitly running "dualboot.sh update" does download the app update, and makes the sideload error not occur, and the script completes without error.

Changed in humpolec:
milestone: none → m10-update
status: Confirmed → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.