949727 - Flashing Hamachi with 1.3 after 1.2 bricks phone

Status: RESOLVED FIXED

(Testing :: General, defect)

Description

[cmtalbert]

Attachment: onescript.sh tool used by automation to flash device

If you flash a Hamachi with 1.3 after flashing it with 1.2 will brick the phone and the phone will no longer be accessible from adb.

This is a serious issue with our flashing system and prevents us from running automation.

Steps:
1. Download 1.2 from pvtbuilds: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2g_ril/hamachi-eng-mozilla-b2g26_v1_2-20131212004004-ril01.02.00.019.102.zip
2. Rename the zip to hamachi.zip
3. Plug in hamachi phone and run the onescript flashing tool used by the automation (attached as a patch).
4. Download 1.3 from pvtbuilds: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2g_ril/hamachi-eng-mozilla-aurora-20131212004003-ril01.02.00.019.102.zip
5. rename this to hamachi.zip
6. Run the onescript flashing tool (i.e. ./onescript.sh)

= Expected =
You flash to 1.3

= Actual =
Phone will fail to remove all items and after copying up b2g and attempting to reboot, the phone will hang at the blue "fox in the wind" loading screen and will no longer be addressable from adb (it will still appear in lsusb though).

The way to unbrick this phone is to plug it into a windows box and use the vendor supplied flashing tools, which is not possible in automation and is a royal PIA.

= An Idea =
If we fail to remove those items in the clean_directory function, perhaps we should stop flashing at that point so that we do not get into this state.

Suggestions on how to debug are very welcome. I will attach the logcat of a successful 1.2 startup and the 1.3 startup up to the point at which adb stops responding. I don't see any smoking guns in these logcats, but maybe another set of eyes will help.

Comment 1

[cmtalbert]

Attachment: The output of the onescript when flashing from 1.2 to 1.3, note the failure to remove certain directories

Comment 2

[cmtalbert]

Attachment: Logcat of starting 1.2

Comment 3

[cmtalbert]

Attachment: Logcat of starting up 1.3

Comment 4

[cmtalbert]

Dave, I think you told me in IRC that you fixed the script so we could no longer get into this state, is that right? If so we can mark this WFM...

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Attachment: Improved script

I created a new script, based off the existing one and the TW one [1] with some additional strengthening when stopping B2G and deleting files. It seems to have resolved a lot of these issues. I'll attach a copy of the latest script. As you were able to replicate this Clint, would you mind running this script to confirm it fixes the issue for you?

It assumes you have gaia.zip and b2g.en-US.android-arm.tar.gz (note the rename here without the version number) in the same location as the script.

[1] https://github.com/Mozilla-TWQA/B2G-flash-tool

Comment 6

[cmtalbert]

Yeah I'll give it a shot when I'm back in the SF office later this week.

Comment 7

[cmtalbert]

Sorry, went on paternity leave and now this is no longer an issue. Clearing the n/i flag.

Comment 8

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Yeah, I'd say the latest script fixes this as we haven't seen this for some time.