! FAILURE ! Please file a bug with console content !

NEW
Unassigned

Status

Firefox OS
B2gInstaller
2 years ago
a year ago

People

(Reporter: alex_mayorga, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(5 attachments)

(Reporter)

Description

2 years ago
Created attachment 8752537 [details]
console.log

¡Hola!

Keep getting an error when trying to flash a Flame.

So filing this bug as asked.

Please find attached the Browser Console contents.

Please see also https://pastebin.mozilla.org/8871416

¡Gracias!
Alex
What is the error you are getting? That log shows clearly successfull flashing.

> Devices enumerated, MUST be fastboot Object { id: "f031419e" }about.js:1121:5
> Using Object { sourceDir: "/tmp/b2g-installer/flame/content/SY…", imageFile: "/tmp/b2g-installer/flame/images/sys…", partition: "system" } from system.imgabout.js:1142:9
syntax errorversion:1:1
> Flash for Object { sourceDir: "/tmp/b2g-installer/flame/content/SY…", imageFile: "/tmp/b2g-installer/flame/images/sys…", partition: "system" } returned Object { sending: true, sendingOk: true, writing: true, writingOk: true, finished: true }about.js:1151:11
> Using Object { sourceDir: "/tmp/b2g-installer/flame/content/BO…", imageFile: "/tmp/b2g-installer/flame/images/boo…", partition: "boot" } from boot.imgabout.js:1142:9
> Flash for Object { sourceDir: "/tmp/b2g-installer/flame/content/BO…", imageFile: "/tmp/b2g-installer/flame/images/boo…", partition: "boot" } returned Object { sending: true, sendingOk: true, writing: true, writingOk: true, finished: true }about.js:1151:11
> Using Object { sourceDir: "/tmp/b2g-installer/flame/content/RE…", imageFile: "/tmp/b2g-installer/flame/images/rec…", partition: "recovery" } from recovery.imgabout.js:1142:9
> Flash for Object { sourceDir: "/tmp/b2g-installer/flame/content/RE…", imageFile: "/tmp/b2g-installer/flame/images/rec…", partition: "recovery" } returned Object { sending: true, sendingOk: true, writing: true, writingOk: true, finished: true }about.js:1151:11
> All partitions should have been flashed nowabout.js:1159:9
Flags: needinfo?(alex_mayorga)
I have just been able to successfully flash my Flame with the latest B2GOS transition build provided by Jovan, using latest Firefox Nightly (64 bits) on Linux :)
(Reporter)

Comment 3

2 years ago
¡Hola Alexandre!

Tried again today it failed on "Downloading Build"

Below please find the contents of the "Browser console".

¡Gracias!
Alex

Read from pref extensions.b2g-installer@mozilla.org.telemetry trueabout.js:1322:5
Verifying Gecko! XPCWrappedNative_NoHelper { processType: Getter, PROCESS_TYPE_CONTENT: 2, version: Getter, is64Bit: Getter, OS: Getter, QueryInterface: QueryInterface(), inSafeMode: Getter, logConsoleErrors: Getter, XPCOMABI: Getter, widgetToolkit: Getter, 24 more… }about.js:1535:5
Gecko is goodabout.js:1573:17
Verifying ADB Helper!about.js:1508:5
ADBHelper: Object {  }about.js:1510:7
ADBHelper status: trueabout.js:1516:7
ADBHelper version: 0.8.7about.js:1522:7
ADB Helper is goodabout.js:1575:17
Device.connected(), will create devicePromiseabout.js:798:5
[ADB] Device is in ADB mode. 2about.js:700:3
Device.connected(), resolving devicePromiseabout.js:810:9
Returning match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Mozilla Flame (Kitkat)", builds: Array[3], adb: Object, fastboot: Object }about.js:765:9
Property match failure ro.product.device expected one of Array [ "hammerhead" ] but got flameabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Nexus 5 (Lollipop)", builds: Array[2], adb: Object, fastboot: Object }about.js:768:9
Property match failure ro.product.device expected one of Array [ "crackling" ] but got flameabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Wileyfox Swift", builds: Array[1], adb: Object, fastboot: Object }about.js:768:9
Property match failure ro.product.device expected one of Array [ "mako" ] but got flameabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Nexus 4 (Kitkat)", builds: Array[2], adb: Object, fastboot: Object }about.js:768:9
Property match failure ro.semc.product.model expected one of Array [ "D5803", "D5833" ] but got undefinedabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Sony Xperia Z3 Compact (Kitkat)", builds: Array[2], adb: Object, fastboot: Object }about.js:768:9
Property match failure ro.semc.product.model expected one of Array [ "D5803", "D5833" ] but got undefinedabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Sony Xperia Z3 Compact (Kitkat)", builds: Array[1], adb: Object, fastboot: Object }about.js:768:9
Property match failure ro.product.device expected one of Array [ "FP2" ] but got flameabout.js:758:11
No match of Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object } against Object { id: "Fairphone 2 (Lollipop)", builds: Array[1], adb: Object, fastboot: Object }about.js:768:9
Found builds: Array [ Object ] for device: Object { id: "f031419e", _modelPromise: Object, model: "flame", _readProps: Object }about.js:1433:5
Read from fs: /system/b2g/application.iniabout.js:562:7
Read from pref extensions.b2g-installer@mozilla.org.telemetry trueabout.js:1322:5
Has verified B2G: trueabout.js:1463:5
Keepdata set: trueabout.js:1465:5
offlineabout.js:1612:3
Installing failedabout.js:1380:9

XMLHttpRequest { onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, responseURL: "", status: 0, statusText: "", responseType: "arraybuffer", response: ArrayBuffer }about.js:1381:9

Read from pref extensions.b2g-installer@mozilla.org.telemetry trueabout.js:1322:5
1463518467605	Toolkit.Telemetry	ERROR	TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/f0eed8bb-353f-4659-8e70-3b5ba6a9fc94/b2g-installer-flash/Firefox/49.0a1/nightly/20160517030211?v=4: error
Log.jsm:753
Flags: needinfo?(alex_mayorga)

Comment 4

a year ago
Created attachment 8786291 [details]
2016-08-30+02 browser console log

Comment 5

a year ago
Created attachment 8786292 [details]
2016-08-30+02 Linux console log

Comment 6

a year ago
Same here. I waited patiently, and then flashing failed. Attached you find browser and Linux console output. What’s wrong?
(In reply to Felix E. Klee from comment #6)
> Same here. I waited patiently, and then flashing failed. Attached you find
> browser and Linux console output. What’s wrong?

It is not even attempting to reboot to fastboot. There are errors about pulling some files (BAD_REPONSE from ADB). I cannot tell more. Can you please with the VM ? https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS/Building_and_installing_B2G_OS/B2G_installer_add-on#Ready_to_use_VM
Flags: needinfo?(felix.klee)

Comment 8

a year ago
Created attachment 8786309 [details]
2016-08-30+02 browser console log

Comment 9

a year ago
See the latest console log: With the VM, my Flame went into Fastboot mode, but flashing still failed. What else can I try?
All I can see is: "Too many devices plugged in."

Comment 11

a year ago
Created attachment 8786346 [details]
2016-08-30+02 browser console log

Comment 12

a year ago
(In reply to Alexandre LISSY :gerard-majax from comment #10)
> All I can see is: "Too many devices plugged in."

…which was not the case. The only external USB device connected was the Flame.

Just tried it again, and again it failed. :(

See latest log, there now is an error message: “Device is not running in ADB mode, aborting ...about.js:1420:7”

Prior to flashing, I made sure that ADB does not magically see any other device:

b2ginstaller@b2g-installer:~$ adb devices
List of devices attached
f065416f        devices

After the failed attempt, the phone hangs displaying “FASTBOOT” written in purple text. It is visible to the computer:

b2ginstaller@b2g-installer:~$ fastboot devices
f065416f        devices

The OS currently on the device is 2.0.0.0-prerelease, to which I downgraded a while ago.

On the PC, I run VMware which at least in the past was preferable to VirtualBox when it comes to USB devices. In fact I recall switching from VirtualBox to VMware for flashing Firefox OS phones.

Any idea? Surely it is possible to manually flash the image created by the installer, no?
Flags: needinfo?(felix.klee)
(In reply to Felix E. Klee from comment #12)
> (In reply to Alexandre LISSY :gerard-majax from comment #10)
> > All I can see is: "Too many devices plugged in."
> 
> …which was not the case. The only external USB device connected was the
> Flame.

Well, this is what the addon says.

> 
> Just tried it again, and again it failed. :(
> 
> See latest log, there now is an error message: “Device is not running in ADB
> mode, aborting ...about.js:1420:7”

That is harmless. But there are still errors about multiple devices connected. We won't go further if we think there are multiple devices connected.
So it's not surprising that fastboot flash is not performed.

> 
> Prior to flashing, I made sure that ADB does not magically see any other
> device:
> 
> b2ginstaller@b2g-installer:~$ adb devices
> List of devices attached
> f065416f        devices
> 
> After the failed attempt, the phone hangs displaying “FASTBOOT” written in
> purple text. It is visible to the computer:
> 
> b2ginstaller@b2g-installer:~$ fastboot devices
> f065416f        devices
> 
> The OS currently on the device is 2.0.0.0-prerelease, to which I downgraded
> a while ago.

2.0 with bootloader L1TC000118D0 ? That looks strange.

> 
> On the PC, I run VMware which at least in the past was preferable to
> VirtualBox when it comes to USB devices. In fact I recall switching from
> VirtualBox to VMware for flashing Firefox OS phones.

I don't have VMWare, and I have not tested running the VM with.

> 
> Any idea? Surely it is possible to manually flash the image created by the
> installer, no?

They are in /tmp/b2g-installer/flame/images/, flashing by hand should work.

Comment 14

a year ago
(In reply to Alexandre LISSY :gerard-majax from comment #13)
> 2.0 with bootloader L1TC000118D0 ? That looks strange.

As said before, I downgraded to 2.0.

> They are in /tmp/b2g-installer/flame/images/, flashing by hand should
> work.

OK:

1. Copied to the Windows 7 host: /tmp/b2g-installer/flame/images/

2. Reinserted the battery of the phone, and booted it again into
   Fastboot mode, by pressing: Volume down + Power

3. On the host, flashed the images:

   >fastboot flash system system.img
   >fastboot flash boot boot.img
   >fastboot flash recovery recovery.img
   >fastboot flash data data.img
   >fastboot erase cache
   >fastboot reboot

   Each operation took a few seconds at most.

After displaying the ThunderSoft logo, the screen blanks and the phone
doesn’t boot. :(

What’s wrong now?
(In reply to Felix E. Klee from comment #14)
> (In reply to Alexandre LISSY :gerard-majax from comment #13)
> > 2.0 with bootloader L1TC000118D0 ? That looks strange.
> 
> As said before, I downgraded to 2.0.

Except I don't remember we should have that bootloader with 2.0.

> 
> > They are in /tmp/b2g-installer/flame/images/, flashing by hand should
> > work.
> 
> OK:
> 
> 1. Copied to the Windows 7 host: /tmp/b2g-installer/flame/images/
> 
> 2. Reinserted the battery of the phone, and booted it again into
>    Fastboot mode, by pressing: Volume down + Power
> 
> 3. On the host, flashed the images:
> 
>    >fastboot flash system system.img
>    >fastboot flash boot boot.img
>    >fastboot flash recovery recovery.img
>    >fastboot flash data data.img
>    >fastboot erase cache
>    >fastboot reboot
> 
>    Each operation took a few seconds at most.
> 
> After displaying the ThunderSoft logo, the screen blanks and the phone
> doesn’t boot. :(
> 
> What’s wrong now?

Who knows ? Mismatching versions could explain this.
Also, I don't know which version you selected. It is possible that what is available out of taskcluster is currently badly broken.

Comment 17

a year ago
“Your device has successfully installed Firefox OS” 

Comment 18

a year ago
What follows is the rest of my message. It got cut off when I used U+1F64C to indicate my joy. Seems like I ran into a Bugzilla bug.

First, on Windows 7, I installed the latest Firefox OS 2.6 base image:

http://cds.w5v8t3u9.hwcdn.net/v18D_nightly_v5/v18D_nightly_v5.zip

Then in my Arch virtual machine, I gave myself permissions to access the device via adb, and updated to the latest Firefox nightly.

I installed “B2G OS transition”, which is what I attempted to install before as well. My user data I selected *not* to keep. The home screen is full of test applications, and – unexpectedly – Facebook. There is no contacts list, but there are two apps to import contacts. Also messaging seems to be missing. May try the other versions now…
You need to log in before you can comment on or make changes to this bug.