Hello,

After reading the information provided about your issue I suggest a soft reset of the phone.

1. Take the back cover of the phone off.
2. Take the battery out.
3. Take the SIM card and microSD card out (if applicable).
4. Wait 10 seconds.
5. Put the SIM card and microSD card back in (if applicable).
6. Put the battery back in.
7. Put the back cover back on.
8. Turn the device on.
9. Check if the issue you were having is still present.

Please report back to us if this solved your problem!

Thank you

No, it does not solve the problem for me.

If I check for updates, I still see "1 update available", "System update REQUIRED, 13.34 MB". I click Download, it downloads. it uncompresses, I get a message "System Update Ready" and "Install update now?". I press the big red button that says "Install Now", i get the two blue screens with the firefox on it (booting?), I get an orange screen with a rotating gear and a progress bar, then it reboots again and seems to functional again, but if I check for updates again, I see the same "required" system update, as if it was not applied.

Device Information shows, Software: OPEN_US_DEV_FFOS_V1.0.0B02, as before, though Last Updated shows the time of the most recent update attempt.

Even without "checking", I'm seeing another of the same 13.34MB "updates available". So, even if the update is applying, it's not noticing that the upstream update isn't needed anymore. Or, alternatively, the update is not applying and the system is trying again, but unsuccessfully some how. I get no feedback that tells me for sure which to believe.

Hi Russell,

Thanks for using Firefox OS and for reporting this issue. I'm not aware of an update that has been made available for the device yet, so while this is annoying for you I'm sure, I believe it is safe to ignore at this time, providing that the device is working correctly otherwise.

Thanks also for the recovery file, I'll provide this to the development team to see if it helps to debug this issue, but I suspect it is unrelated.

Regards, Michelle Luna

Just jumping in here, I received mine on the 23rd and I am also seeing the same problem, but the logs are a bit different. Although, I am running OPEN_US_DEV_FFOS_V1.0.0B02. While the recovery log states B01.

I'll toss my log up as well so trends can be examined. Starting recovery on Sun Aug 25 07:04:10 2013 framebuffer: fd 4 (320 x 480) recovery filesystem table

=============

 0 /tmp ramdisk (null) (null) 0
 1 /boot mtd boot (null) 0
 2 /amss mtd amss (null) 0
 3 /appsbl mtd appsbl (null) 0
 4 /mibib mtd mibib (null) 0
 5 /qcsbl mtd qcsbl (null) 0
 6 /oemsbl1 mtd oemsbl1 (null) 0
 7 /oemsbl2 mtd oemsbl2 (null) 0
 8 /splash mtd splash (null) 0
 9 /cache yaffs2 cache (null) 0
 10 /data yaffs2 userdata (null) 0
 11 /misc mtd misc (null) 0
 12 /recovery mtd recovery (null) 0
 13 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
 14 /system yaffs2 system (null) 0

I:Got arguments from /cache/recovery/command mtd: successfully wrote block at 0 I:Set boot command "boot-recovery" Command: "/sbin/recovery" "--update_package=/sdcard/updates/fota/update.zip"

ro.secure=1 ro.allow.mock.location=0 ro.debuggable=0 ro.build.id=IMM76D ro.build.display.id=OPEN_US_DEV_FFOS_V1.0.0B01 ro.build.version.incremental=eng..20130724.030603 ro.build.version.sdk=15 ro.build.version.codename=REL ro.build.version.release=4.0.4 ro.build.sw_internal_version=US_DEV_FFOS_V1.0.0B01 ro.build.baseband_version=P752D04B02 ro.build.firmware_revision=V1.01.00.01.019.144 ro.build.date=2013年 07月 24日 星期三 03:06:47 CST ro.build.date.utc=1374606407 ro.build.type=user ro.build.user= ro.build.host=ThinkCentre2-XXXX ro.build.tags=test-keys ro.product.model=roamer2 ro.product.external_model=ZTE OPEN ro.product.brand=ZTE ro.product.name=roamer2 ro.product.device=roamer2 ro.product.board=roamer2 ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=ZTE ro.product.locale.language=en ro.product.locale.region=US ro.wifi.channels= ro.board.platform=msm7627a ro.build.product=roamer2 ro.build.description=roamer2-user 4.0.4 IMM76D eng..20130724.030603 test-keys ro.build.fingerprint=ZTE/roamer2/roamer2:4.0.4/IMM76D/eng..20130724.030603:user/test-keys ro.build.characteristics=default rild.libpath=/system/lib/libril-qc-1.so rild.libargs=-d /dev/smd0 persist.rild.nitz_plmn= persist.rild.nitz_long_ons_0= persist.rild.nitz_long_ons_1= persist.rild.nitz_long_ons_2= persist.rild.nitz_long_ons_3= persist.rild.nitz_short_ons_0= persist.rild.nitz_short_ons_1= persist.rild.nitz_short_ons_2= persist.rild.nitz_short_ons_3= ril.subscription.types=NV,RUIM DEVICE_PROVISIONED=1 debug.sf.hw=1 debug.composition.7x27A.type=mdp debug.composition.7x25A.type=mdp dalvik.vm.heapsize=128m persist.cne.UseCne=none persist.cne.bat.range.low.med=30 persist.cne.bat.range.med.high=60 persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml persist.cne.loc.policy.user=/system/etc/UserPolicy.xml persist.cne.bwbased.rat.sel=false persist.cne.snsr.based.rat.mgt=false persist.cne.bat.based.rat.mgt=false persist.cne.rat.acq.time.out=30000 persist.cne.rat.acq.retry.tout=0 persist.cne.fmc.mode=false persist.cne.fmc.init.time.out=30 persist.cne.fmc.comm.time.out=130 persist.cne.fmc.retry=false media.stagefright.enable-player=true media.stagefright.enable-meta=false media.stagefright.enable-scan=true media.stagefright.enable-http=true media.stagefright.enable-fma2dp=true media.stagefright.enable-aac=true media.stagefright.enable-qcp=true ro.opengles.version=131072 ro.use_data_netmgrd=true persist.data.ds_fmc_app.mode=0 persist.ims.regmanager.mode=0 ro.bluetooth.request.master=true ro.qualcomm.bluetooth.sap=false ro.bluetooth.remote.autoconnect=true persist.sys.strictmode.visual=false persist.omh.enabled=1 ro.config.ehrpd=true ro.qualcomm.cabl=1 ro.fm.analogpath.supported=true ro.fm.transmitter=false ro.fm.mulinst.recording.support=false ro.hw_plat=7x27a ro.emmc.sdcard.partition=18 ro.screen.layout=normal debug.enabletr=false debug.camcorder.disablemeta=0 persist.fuse_sdcard=false debug.camera.landscape=true ro.max.fling_velocity=4000 hwui.render_dirty_regions=false httplive.enable.discontinuity=true power.webview.DM=false dalvik.vm.heapstartsize=5m dalvik.vm.heapgrowthlimit=36m org.bluez.device.conn.type=boolean keyguard.no_require_sim=true ro.com.android.dataroaming=false ro.com.android.dateformat=MM-dd-yyyy ro.config.ringtone=Ring_Synth_04.ogg ro.config.notification_sound=pixiedust.ogg ro.config.alarm_alert=Alarm_Classic.ogg ro.vendor.extension_library=/system/lib/libqc-opt.so ro.display.colorfill=1 ro.moz.ril.emergency_by_default=true ro.moz.omx.hw.max_width=640 ro.moz.omx.hw.max_height=480 ro.moz.cam.0.sensor_offset=270 ro.moz.ril.simstate_extra_field=true persist.sys.ztelog.enable=1 persist.radio.add_power_save=1 ro.sensor.arch.type=new net.bt.name=Android net.change=net.bt.name dalvik.vm.stack-trace-file=/data/anr/traces.txt ro.factorytest=0 ro.serialno=ROAMER2 ro.bootmode=unknown ro.baseband=msm ro.carrier=unknown ro.bootloader=unknown ro.hardware=roamer2 ro.revision=0 ro.emmc=0 init.svc.recovery=running

Finding update package... I:Update location: /sdcard/updates/fota/update.zip Opening update package... I:1 key(s) loaded from /res/keys Verifying update package... I:comment is 1746 bytes; signature 1728 bytes from end I:whole-file signature verified against key 0 I:verify_file returned 0 Installing update... try_update_binary(path(/sdcard/updates/fota/update.zip)) radio.diff not found Verifying current system...Failed to mount /dev/block/mtdblock4 on /cache: Device or resource busy mtd mount of cache failed: Device or resource busy 51191808 bytes free on /cache (5714 needed)

applying patch to /system/build.prop "/system/build.prop" is already target; no patch needed Removing unneeded files... Patching system files... Symlinks and permissions... script result was /system

I had the same update. It crashed the first time. The next time, it seemed to work out ok. But then the same update showed up again. This repeated itself 5 times, then it apparently worked. I haven't had another notification since then.

The device is on 1.0.1 right now, I do believe the latest version is 1.1.

So yes, an update should be pushed down, I think most people bought ZTE open and expect to receive update from mozilla whenever there is one. Is there any reason to believe that ZTE needs to vet/re-package the update package and we will not receive upgrade directly from Mozilla?

That would create a problem much like samsung and google, which leads to multiple months delay of update of samsung andriod phones.

Can admin confirm or clarify this? Thanks

@m_niemann is your os now ver 1.1?

No it isn't. Here's the listing from Device Information: Software: OPEN_US_DEV_FFOS_V1.0.0B02

So it hasn't even updated to ver 1.0.1

Oh, and the same update is showing up again twice already. And there is an update folder on my SD card. One of the files includes a zipped file.

One more thing. Everytime I restart the phone, there's a message about 255 new voicemails. But that goes away when I clear notifications.

Same issue for me.

I'd also like clarifications on if we can get new firmware directly from mozilla, or if we have to wait for ZTE to release it. I contacted ZTE about another issue (https://support.mozilla.org/en-US/questions/969144), and they persisted in saying I need to contact my "authorized service provider" for an update (even though I bought the phone unlocked from ZTE, and did not buy it from my cell carrier).

We are working with ZTE to getting a proper update out for you guys. Please be patient and stay tuned.

Well Feer56, it;s been three months since you suggested folk should be patient, perhaps Mozilla could release compiled binaries? They were hosed by ZTE, why not bypass them and help out the loyal early adopters?

Doramia: Your issue is being addressed in the thread you started: https://support.mozilla.org/questions/979055