User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140716183446 Steps to reproduce: Following flash steps from https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame I've tried to flash to version 1.4 from 07-Aug-2014 and then, after failure, to 2.0 from the same date. Flash process went both times without significant errors (### Shallow Flash Successful!, on Win7, BTW, I'll submit my hacked pull-request to shallow_flash.sh script soon). Actual results: Device refuses to BOOT to GUI, ThunderSoft logo remains on the screen, however, it is accessible via adb. I'm attaching logcat results from both tries, they are almost the same, the problem IMHO is: D/ACDB-LOADER( 1121): send mbhc data D/ACDB-LOADER( 1121): ACDB -> ACDB_CMD_GET_ANC_SETTING D/ ( 1121): Invalid AV file. It doesnt contain LUT for tblid 0000000A D/ ( 1121): Failed to fetch the lookup information of the device 0000001A E/ACDB-LOADER( 1121): Error: ACDB ANC returned = -1 Expected results: Device should be running with new OS version. I wish to be able to flush any build and help with testing, but I'm stuck with this problem and hope for someone smarter than me to help me solve it why...

I'm using this shallow_flash.sh script (https://github.com/Mozilla-TWQA/B2G-flash-tool/pull/240), hacked for Cygwin support... perhaps there is some error?

Marek: Recommending reflashing the base image per the instructions here - https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software and then trying the shallow flash again.

This is what I did, several times, because after my failed flash device was not usable at all :-( Some other suggestion, please?

is there someone seeing in the logs the root cause of B2G not running?

I set bash debugging option ON on shallow_flash.sh and did failing flash on Cygwin. Then I've tried Ubuntu live distro and repeated the same procedure - this time with success! I've compared logs from both Linux and Cygwin runs and there are practically no differences, except of those Win specific + of course differing temporary directory names. I've also tried to run Cygwin terminal both as administrator and common user, but it behaves the same. So, for now, I'm giving up on Windows+Cygwin combination and I can only heartily recommend to all Windows users to do the same, as the only working way (for me): - create some live Linux distro on USB or CD/DVD disk - boot from it - install adb and clone repository with shallow script - flash.... and it is, you can then safely reboot to Windows you're used to Thx all who tried to help me... Marek

for Cygwin, that's it...

I believe the shell script not running with cygwin is because of two issues First the cat command is failing to find the user.js file that can be fixed with ## Adjusting user.js if [[ `uname` == "CYGWIN"* ]]; then cat c:$GAIA_DIR/gaia/profile/user.js | sed -e "s/user_pref/pref/" > c:$GAIA_DIR/user.js if [[ ! -d "/cygdrive/c/tmp" ]]; then mkdir "/cygdrive/c/tmp" fi cp -r $GAIA_DIR /cygdrive/c/tmp/ else cat $GAIA_DIR/gaia/profile/user.js | sed -e "s/user_pref/pref/" > $GAIA_DIR/user.js fi && This is using hard coded c drive though. The Second issue is that the permissions are not being preserved in the adb push command. As a hacky work around is to do this before the adb reboot ## Hack for windows with cywgwin for permission issue ## should use the correct permission instead of 777 if [[ `uname` == "CYWGIN"* ]]; then run_adb shell chmod 777 /system/b2g/b2g run_adb shell chmod 777 /system/b2g/updater run_adb shell chmod 777 /system/b2g/run-mozilla.sh run_adb shell chmod 777 /system/b2g/plugin-container fi &&

modified shell script

Hi, thx a lot for your fix. User.js was not an issue, and your fix made it broken for me, at least, but the second part about rights is the main culprit. I've tested it twice ind it works now, great!! Thx, I've already send pull request, check it here: https://github.com/Mozilla-TWQA/B2G-flash-tool/pull/273

Marek, On my windows machine the cat command that uses sed was failing to locate the User.js file in the pref directory. Are you using the 64bit version of cygwin? I think a bat file would be better solution BTW.

Yes, I'm. Maybe you've a bit outdated Cygwin binaries, try to run installer to update them. .bat file for Windows users would be better, yes, but maintain two scripts instead of one is major drawback, is it not?

I just downloaded the 64bit version. Yea different versions will be a pain but it is a relatively short script. The bigger problem is dealing with Sed, Cat and unzipping from windows.

Agree. A possible solution is to rewrite by python. We still put that in backlog since large effort.

I have this with the Nightly Aurora and Master. Either the script is broken or the docs are wrong: 1. Go to https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame 2. Download the 2.0 base and follow the instructions. https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software. I now have a working phone. 3. Now download either Aurora or Master as in https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame_to_a_nightly_build. The shallow flash appears to be successful, the phone reboots and gets stuck in the ThunderSoft screen. Host is 64-bit Fedora Linux. Please re-open this bug so I don't have to file a new one.

I have the same problem, it's only possible to flash the 2.0 base image. Newer images causes stuck on ThunderSoft screen.

(In reply to holztest08 from comment #20) > I have the same problem, it's only possible to flash the 2.0 base image. > Newer images causes stuck on ThunderSoft screen. I assume there's some combination of procedures that will work, like making a full directory by merging release pieces and doing a flash.sh instead of a shallow_flash.sh. This seems like something simple - a missing piece of software when you do a shallow_flash - but I don't have the time to troubleshoot the scripts on a bug tagged 'CLOSED WONTFIX' ;-)

(In reply to znmeb from comment #21) > (In reply to holztest08 from comment #20) > > I have the same problem, it's only possible to flash the 2.0 base image. > > Newer images causes stuck on ThunderSoft screen. > > I assume there's some combination of procedures that will work, like making > a full directory by merging release pieces and doing a flash.sh instead of a > shallow_flash.sh. This seems like something simple - a missing piece of > software when you do a shallow_flash - but I don't have the time to > troubleshoot the scripts on a bug tagged 'CLOSED WONTFIX' ;-) We update the script[1], please download new shallow_flash.sh script from github and try again. Askeing [1] https://github.com/Mozilla-TWQA/B2G-flash-tool/pull/296

(In reply to Askeing Yen[:askeing] from comment #22) > (In reply to znmeb from comment #21) > > (In reply to holztest08 from comment #20) > > > I have the same problem, it's only possible to flash the 2.0 base image. > > > Newer images causes stuck on ThunderSoft screen. > > > > I assume there's some combination of procedures that will work, like making > > a full directory by merging release pieces and doing a flash.sh instead of a > > shallow_flash.sh. This seems like something simple - a missing piece of > > software when you do a shallow_flash - but I don't have the time to > > troubleshoot the scripts on a bug tagged 'CLOSED WONTFIX' ;-) > > We update the script[1], please download new shallow_flash.sh script from > github and try again. > > Askeing > > [1] https://github.com/Mozilla-TWQA/B2G-flash-tool/pull/296 That worked! Thanks!!