Closed Bug 838924 Opened 12 years ago Closed 12 years ago

FOTA updates still don't work


(Firefox OS Graveyard :: General, defect)

Gonk (Firefox OS)
Not set


(blocking-b2g:tef+, firefox19 wontfix, firefox20 wontfix, firefox21 fixed, b2g18 fixed, b2g18-v1.0.0 fixed, b2g18-v1.0.1 fixed)

B2G C4 (2jan on)
blocking-b2g tef+
Tracking Status
firefox19 --- wontfix
firefox20 --- wontfix
firefox21 --- fixed
b2g18 --- fixed
b2g18-v1.0.0 --- fixed
b2g18-v1.0.1 --- fixed


(Reporter: dhylands, Assigned: dhylands)



(Whiteboard: QARegressExclude, [qa-])


(1 file, 1 obsolete file)

OK - I screwed up in bug 835210 (/me hangs head in shame)

I didn't know how to test the success path, and my innocuous little change broke the success path.

Marking as tef? since bug 835210 was tef+
Finally figured out how to create and test a FOTA update and tested that update was actually applied with this patch.

I tested both storing the update to /data/local/updates/fota and /mnt/sdcard/updates/fota
Attachment #711131 - Flags: review?(marshall)
Comment on attachment 711131 [details] [diff] [review]
Fix try/catch introduced in bug 835210 which caused FOTA updates to still be broken

Moving let outside the try (as per comment by marshall via email) will upload new patch when ready.
Attachment #711131 - Flags: review?(marshall)
Moved let outside the try/catch as per email.
Attachment #711135 - Flags: review?(marshall)
Attachment #711131 - Attachment is obsolete: true
Attachment #711135 - Flags: review?(marshall) → review+
Issue repros on the OTA for 2/7/13.  When attempting to do an OTA from build 20130205070201 (OTA for 2-5-13) to build 20130207070202 (Current OTA for 2/7/13) it failed on three out or four devices to do on carrier network.  Wifi would work just not AT&T network.  There were four bars showing on carrier network and Data was turned on.  Tested while off as well.  Issue repro. device to update_2-5 OTA and then OTA worked.

Build/Kernel Info that OTA is not working on 
Build ID: 20130130070201
Kernel: Dec 5
Gaia   f7f5a0cd17e3d04308cc5850b254947e127122b9
Closed: 12 years ago
Resolution: --- → FIXED
blocking-b2g: tef? → tef+
Does not make sense to create a regression issue.
Flags: in-moztrap-
Can you please provide steps to verify this fix - as we will blackbox test from the UI?
You need to create a VARIANT=user or VARIANT=userdebug build.

I just tested with a VARIANT=userdebug.

1 - build it (./
2 - flash it (./

3 - Build the fs_config tool
cd into your B2G directory
. ./
cd build/tools/fs_config

4 - Build a FOTA update. IMPORTANT: The partition names below are phone specific. If you use the wrong ones, you will almost certainly brick your phone.

mkdir fota
tools/update-tools/ \
    --system-dir out/target/product/${DEVICE}/system \
    --system-fs-type ext4 \
    --system-location /dev/block/mmcblk0p19 \
    --data-fs-type ext4 \
    --data-location /dev/block/mmcblk0p22 \
    --output fota/

tools/update-tools/ \
    --output fota/update.mar fota/

5 - Deploy the fota update to your phone (requires an adb connection - so make sure that this is enabled first). Also make sure that Wifi is enabled and connected.

tools/update-tools/ --fota-update fota/update.mar

6 - Once B2G finishes restarting, Go into Settings -> Device Information and do "Check Now"

7 - After about 30 seconds, you should get a notification that a new system update is available. I normally uncheck any apps which need to be updated and just apply the system update. Choose Download.

8 - Once the update has been downloaded and uncompressed, you should get presented with the apply update dialog, choose "Install Now"

The phone should reboot into Android recovery and apply the update. This didn't happen for me when I just tried it. So I can't list the step-by-step required.

So it appears to be broken again.

I did see: 

UpdatePrompt: Rebooting into recovery to apply FOTA update: /mnt/sdcard/updates/fota/

as the last line of my adb logcat, so it thought it was trying to do that, but it just rebooted back into b2g.
It appears that we don't have the tools to do this on our end in the QA lab here unfortunately.
Whiteboard: QARegressExclude
Depends on: 858188
I suspect this affects OTAs but we'll continue on QA side by continuing to test OTA updates.   QA- ing.   Can Dave please ensure that this is resolved and move status from Resolved=>Verified if it's working?  Thanks!
Flags: needinfo?(dhylands)
Whiteboard: QARegressExclude → QARegressExclude, [qa-]
I tried to verify but it didn't work, so I opened bug 858188
Flags: needinfo?(dhylands)
You need to log in before you can comment on or make changes to this bug.