874123 - [B2G] [Inari] [System] Flashing to commercial v1.1 build fails

Status: VERIFIED WORKSFORME

(Firefox OS Graveyard :: Gaia, defect)

Description

[Nick Davidson]

Attachment: log of loading comm v1.1 OS on Inari and trying to restart device afterwards.

Description:
Attempting to update to the May 20 commercial build v1.1 will result in a blank black screen right after blue Firefox logo screen, with no way to get the device to start.

Repro Steps:
1) Flash to Inari Build ID: 20130520070207
2) Once the flash completes, observe the state of the device.
3) Hold down the power button until the device responds, then observe what is shown.

Actual:
After flashing, the user will see devise starting to boot up and then afterblue screen with Firefox logo device go to a blank black screen.  Attempting to restart will show the device splash screen but then returns to the blank black screen.

Expected:
After flashing, the device shows the device and OS splash screens before beginning the First Time User setup.

Environmental Variables:
Build ID: 20130520070207
Kernel Date: Feb 21
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/321d5b4db55a
Gaia: b161f42c5647b37e35ba5a20f394ba40bf674d9c

Notes:
Repro frequency: 100% 2 devices
Q Analysts Test Team Priority: Pri 1
See attached logcat logs for more info.
link to the build: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2g_ril/inari-mozilla-b2g18-20130520070207-ril01.01.00.019.099.zip

Comment 1

[Allen Maxwell]

This affects the smoketest for the Inari v1.1 from passing.

Request escalation Pri 1

Comment 2

[Michael Vines [:m1] [:evilmachines]]

AU 099 is known to be incompatible with the tip of v1.1 gecko.   Please retry with AU 101 or greater, which should be released by 5/21 AM PST

Comment 3

[Nick Davidson]

(In reply to Michael Vines [:m1] [:evilmachines] from comment #2)
> AU 099 is known to be incompatible with the tip of v1.1 gecko.   Please
> retry with AU 101 or greater, which should be released by 5/21 AM PST

I flashed to -  inari-mozilla-b2g18-20130521070208-ril01.01.00.019.102. and still experience same issue. 

Build ID: 20130521070208
Kernel Date: Apr 25
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/762354023009
Gaia: c51082d92f18c4c7cdbc4f96c977be735500562a

Comment 4

[Michael Vines [:m1] [:evilmachines]]

Ah, can you please share the output of |adb logcat -b radio| from boot with this 102 build?

Comment 5

[Nick Davidson]

Attachment: adb logcat -b radio for Inari v1.1 Com RIL from MAY20 build

log was captured by running "adb logcat -b radio" in cygwin - please let me know if this is what you are looking for.

Comment 6

[J Zimbrick]

Issue does not seem to be occurring in the latest Inari build on the commercial 1.1 branch: 

Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/4785b1353fd7
Gaia: 4de4354e3a99f151a834743c7b03a041ac8db12f
Build: 20130603070207

Device appears to flash correctly and appears to be fully functional.

Resolving as works for me.

Comment 7

[Chris Kreinbring [:CKreinbring]]

Verified as Worksforme on Inari 1.1 commercial RIL.  Flashing to today's commercial build was successful.

Build ID: 20130625070217
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/29933d1937db
Gaia: 1436e2778b90bd74635b0b94d1cf8ccb0d71b60c
Platform Version: 18.1