1227450 - [Flame] Shallow_flashing a 2.2 image over a v18D nightly base image (v3 or v4) results in a black screen on reboot

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Mossroy]

Steps to reproduce (following the instructions in https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame ) :
- install the V18D nighlty v4 base image
- shallow_flash a recent v2.2 image (I tested with 2015-11-23-03-25-00-mozilla-b2g37_v2_2-flame-kk and 2015-10-24-03-25-05-mozilla-b2g37_v2_2-flame-kk, both with latest shallow_flash.sh from https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/shallow_flash.sh )

Observed behavior : the shallow_flash.sh script restarts the device, but it stays on a black screen after the "ThunderSoft" screen
It's possible to connect with adb. An adb logcat shows lines like :
I/I/O     (  208): connect failed with error 2 (No such file or directory)

Expected behavior : Firefox OS 2.2 should start correctly

I found that restoring a profile with https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/backup_restore_profile.py solved the issue.

Another workaround that worked for me is to connect with adb before shallow_flashing, and run :
rm -rf /data/local/*

So I suspect that some files in /data/local (probably from the Firefox OS nightly contained in the nightly base image) are causing issues with Firefox OS 2.2.
Maybe shallow_flash.sh should delete more content in /data/local?

NB : if using the nightly v3 base image, the issue is the same. If using the v18D base image (not nightly), there's not problem (but I suppose some bug fixes would be missing : https://bugzilla.mozilla.org/show_bug.cgi?id=1154072 )

Comment 1

[BMO Automation]

Firefox OS is not being worked on