Closed Bug 1112663 Opened 11 years ago Closed 8 years ago

Latest images of FxOS brick Flame phone just before startup

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: michael.moroni, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 Build ID: 20141216030203 Steps to reproduce: 1. Download v188.zip 2. Extract it 3. (If you use Linux) rename flash.bat into flash.sh 4. Open a terminal 5. sh flash.sh All goes well. 6. Download (one of the) latest Firefox OS 2.2 image(s) 7. sh shallow_flash.sh gecko=/path/to/b2g-37*.tar.gz gaia=/path/to/gaia.zip Actual results: The Flame is bricked when the Firefox logo and "Firefox OS" appear, just after "ThunderSoft" (and the animated fox, but it doesn't appear. Is it another bug?) If you rotate the screen, the logos will rotate too. Expected results: Firefox OS should be loaded.
Severity: normal → blocker
blocking-b2g: --- → 2.2?
"adb logcat" is stuck at "- waiting for device -", so I can't even get a log of what happens behind the scene
I am not able to reproduce thus behaviour. I upgraded my Flame today from prerelease 1.3 to the same zip 188 as you did. It was stuck on <waiting for device> on Linux (F20), but this was due to running the flash script as a normal user. I retried it as root and it succeed.
Which of the 2.2 images did you use?
Sorry for my late answer, I just came home from holidays. Did you flashed Gecko and Gaia too, as described in steps 6 and 7? I can flash Gonk without any problem. I have a Flame device so I use this image of Gecko and Gaia [1]: - b2g-37.0a1.en-US.android-arm.tar.gz - gaia.zip I tested also with Firefox OS v2.1 and I get the same problem of v2.2 [2] but everything goes well if I use v 2.0 [3]. [1] https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk/ [2] https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g34_v2_1-flame-kk/ [3] https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk/
I updated with the production nightly as you mentioned in [1]; named b2g-37.0a1.en-US.android-arm.tar.gz and it works without a hitch. I haven't tried 2.1. What about reflashing from Step 1 again?
I tried to reflash again from step 1 but nothing changes. I noticed that when the screen is stuck at the "Firefox OS" logo I can make screenshots by holding Power button and Down button (I can hear the sound of screenshot) but nothing is saved. I just suppose that a system file is stored and it causes some problems. How can I completely format my Flame? Emergency mode doesn't format my Flame...
Thank you very much but I need the serial number. How can I obtain that?
You should not need, but this is the string that identifies your device (mostly useful when more than one device is connected). But if you really need, you can get it using 'adb devices'.
I tried to use that script but the problem still occurs. I don't know what to do. By now I keep Firefox OS v 2.0 installed on my Flame.
I forgot to say that I get an error when flashing: https://bugzilla.mozilla.org/show_bug.cgi?id=1115022 I think that it is a useful clue to find how to solve my problem.
Probably I need to flash a custom build of Gonk to my Flame to fix this problem. How can I build it? I cannot find any answer on MDN
(In reply to michael.moroni from comment #12) > Probably I need to flash a custom build of Gonk to my Flame to fix this > problem. > How can I build it? I cannot find any answer on MDN Not sure what kind of error you met, but i think i help you to recover your device and update it to latest gecko/gaia if you would like to build it in your side. Firstly, you can use base image to recover your device: http://cds.w5v8t3u9.hwcdn.net/v188.zip Then you can build you own images for flame: 1) Setting some build environment here: https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites 2) get source code, build and flash your device: 2.1 $ git clone git://github.com/mozilla-b2g/B2G.git . 2.2 $ ./config.sh flame-kk 2.3 $ ./build.sh (please connect your flame with adb) 2.4 $ ./flash.sh (of course you can flash gecko/gaia only in this step) (ref: https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS)
Thank you viral but I don't need to know how to build Gecko and Gaia, because I already followed the guide, but: 1. I don't need to recover my phone because it works with v188 and Firefox OS v 2.0 and when I try to flash latest 2.2 and it bricks my Flame I can recover it by flashing v188 and 2.0 again 2. I need to build Gonk or what we called v188 from source in order to flash 2.2 and to use latest version of Firefox OS and be happy again with latest features. How can I build Gonk/v188?
(In reply to michael.moroni from comment #14) > Thank you viral but I don't need to know how to build Gecko and Gaia, > because I already followed the guide, but: > 1. I don't need to recover my phone because it works with v188 and Firefox > OS v 2.0 and when I try to flash latest 2.2 and it bricks my Flame I can > recover it by flashing v188 and 2.0 again good :) > 2. I need to build Gonk or what we called v188 from source in order to flash > 2.2 and to use latest version of Firefox OS and be happy again with latest > features. > How can I build Gonk/v188? We have to build full images if you would like to update gonk part :) The steps here are similar to comment 13, the only difference is we set v2.2 branch here. (https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites also required) $ git clone git://github.com/mozilla-b2g/B2G.git . $ BRANCH=v2.2 ./config.sh flame-kk $ ./build.sh (please connect your flame with adb) $ ./flash.sh I'm in homescreen now with the version below: Gaia-Rev 8b868120ac55de6e0e199acb7b62e89cf4c2cf04 Gecko-Rev b583e22005c6336ad675749467e74eadcef1aa90 Build-ID 20150115110816 Version 37.0a2 Device-Name flame
Right now I'm in the building process. Just some questions in case it will fix the problem: 1. Will "./config.sh flame-kk" configure the v3 branch or the v2 one? 2. How to create a production build? It seems that this process creates only engineering builds
(In reply to michael.moroni from comment #16) > Right now I'm in the building process. > Just some questions in case it will fix the problem: > 1. Will "./config.sh flame-kk" configure the v3 branch or the v2 one? that's v3 branch, if you would like to build v2, you should add branch like "BRANCH=v2.2 ./config.sh flame-kk" > 2. How to create a production build? It seems that this process creates only > engineering builds Yes, it's eng build as default, you can new a file .userconfig in your root of b2g folder and add "PRODUCTION=1" in .userconfig. Please refer this link for detail https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file#Creating_production_and_engineering_builds
FYI after 7 hours of building I found a syntax error: https://bugzilla.mozilla.org/show_bug.cgi?id=1123590
(In reply to michael.moroni from comment #11) > I forgot to say that I get an error when flashing Any feedback or resolution to this? I do not think building the image would actually be your solution, since I think you would still encounter the same issue when flashing it to the device.
Everytime I flash v188, which contains Firefox OS v2.0, and a non-v2.0 image of Firefox OS on my Flame it doesn't work. This is why I think that building it all could be a solution.
Reviewed in triage today. QA suggests we wait for 18D nightly, which will be in ~2 weeks, post Chinese New Year. Don't anticipate a resolution arriving before that. Not blocking because this is not a build issue for vendors.
blocking-b2g: 2.2? → ---
Is this still occurring? Also could you try the latest contributor build? We just recently posted a new version.
With new kernel images this bug is fixed. Can be closed. Thank you
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.