1065010 - [Flame][KK] Phone regularly fails to (re)boot: "Error::Cannot open the file /firmware/image/keymaste.mdt" | "Error::Loading image failed with ret = -1"

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Mike Habicher [:mikeh] (high bugzilla latency)]

Observed: Flame is stuck at the ThunderSoft(R) screen. logcat shows the following, over and over again:

05-06 23:22:01.040   323   323 E QCALOG  : [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent]
05-06 23:22:01.040   323   323 E QCALOG  : [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent]
05-06 23:22:03.499  1355  1355 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
05-06 23:22:03.499  1355  1355 D QSEECOMAPI: : App is not loaded in QSEE
05-06 23:22:03.499  1355  1355 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
05-06 23:22:03.499  1355  1355 E QSEECOMAPI: : Error::Loading image failed with ret = -1
05-06 23:22:03.509  1355  1355 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
05-06 23:22:03.509  1355  1355 D QSEECOMAPI: : App is not loaded in QSEE
05-06 23:22:03.509  1355  1355 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt
05-06 23:22:03.509  1355  1355 E QSEECOMAPI: : Error::Loading image failed with ret = -1
05-06 23:22:03.520  1355  1355 E QCOMKeyMaster: Loading keymaster app failied
05-06 23:22:03.520  1355  1355 E keystore: could not open keymaster device in keystore (Operation not permitted)
05-06 23:22:03.520  1355  1355 E keystore: keystore keymaster could not be initialized; exiting

Expected: phone should boot, natch.

A fresh flash of gaia usually clears the problem, but the problem recurs on reboot.

I'm running:

- gonk:  v166, w/ 319MB of RAM (though w/ 768MB, the problem still occurred)
- gecko: aurora:956b152e6d21 (buildID: 20140909000204)
- gaia:  v1.2:c7b55ed3be126b1f5f3d9cdd0277c365a6652d29

Also observed with:

- gecko: b2g-inbound:07f2836fb609
- gaia:  master:3a99e64704f1793f1bb547d19859d00721073a7c

Comment 1

[Jason Smith [:jsmith]]

QA Wanted - can anyone else reproduce?

Comment 2

[Eitan Isaacson [:eeejay]]

I can reproduce.

1. Flash v180 base firmware.
2. Flash gecko from master (e1a3c6b)
3. Flash gaia from master (ba6cf2c)
4. Reboot

Comment 3

[Eitan Isaacson [:eeejay]]

Actually, I see that error while flashing v180 alone with nothing additional. It does not impede bootup though.

Comment 4

[Reuben Morais [:reuben]]

When I flash the v180 base image I get the same error, but it boots. When I flash from master, that error message looping is the last thing on logcat, and it doesn't boot.

Comment 5

[michael.moroni]

I can reproduce the same bug with v188.
After flashing it shows up "There was an error in downloading the updates" even if the phone is not connected to Internet yet and it doesn't download any OTA update.
If I reboot my Flame, it freezes on the ThunderSoft's logo

Comment 6

[Duane Dixon [:ddixon]]

I also was able to reproduce a similar issue. 

STR: 
1. Flash to v188 base image on Flame device.
2. Attempt to perform OTA update to a 2.1 build. 
3. Restart device and observe error message/failure to install update. 

Actual Results: 
The device failed to perform an OTA update from v188 base image to a 2.1 branch build. 
	-"Error downloading update" message received after Restarting device. 
	-The device did NOT freeze on Thundersoft boot screen. 

Sorry, I don't have the resources to test any OTA features for a different base image for my Flame device (such as: v123, v188-1).

Comment 7

[BMO Automation]

Firefox OS is not being worked on