Closed Bug 908512 Opened 12 years ago Closed 12 years ago

OS OTA Update doesn't apply on ZTE Open

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: q, Unassigned)

References

Details

Attachments

(1 file)

Video at http://www.youtube.com/watch?v=RZEu9Bw-scI
99 bytes, text/html
Details
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release) Build ID: 20130814063812 Steps to reproduce: Attempted to update ZTE Open with OTA updater -- 1. Received notification of update 2. Accepted update, proceeded to download update 3. Was prompted to reboot to apply update, did so Actual results: 1. After reboot, update screen showed progress, apparently finished updating 2. Phone finished reboot, back to home screen 3. Proceed to use phone, several minutes later get notification of same required update I verified that the system OS was the same (1.0.1.0) and when it asked me to download the update again, that download package size was the same size (13.34mb) Expected results: Update should have been applied properly
Also should probably note that I'm *not* using a SIM card in this phone yet -- just received it today and have wanted to play with it a bit on wifi before committing to service on the phone.
We've seen reports of this in the #b2g channel as well, so marking confirmed.
Status: UNCONFIRMED → NEW
Component: General → Gaia::System
Ever confirmed: true
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
Kevin, can you help route this bug to the right place? I'm not sure where something for a vendor update should get filed.
Flags: needinfo?(khu)
If you have encountered this problem and are comfortable using the adb tool, can you grab any files at these locations and attach to the bug? /data/local/updates/0/update.log /cache/recovery/last_log You will need to enable Remote Debugging in the developer tab in the settings app first. Then use adb pull: adb pull /cache/recovery/last_log
Here is a video provided by user thesov on irc.
Attachment #794819 - Attachment mime type: text/plain → text/html
log from the last_log file hell@android:/cache/recovery # cat last_log Starting recovery on Fri Aug 23 19:33:56 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 53178368 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] shell@android:/cache/recovery #
Flags: needinfo?(khu)
Flags: needinfo?(khu)
I'm getting the same problem on Keon with 1.2 (nightly builds). See bug 908757
(In reply to Hubert Figuiere [:hub] from comment #7) > I'm getting the same problem on Keon with 1.2 (nightly builds). See bug > 908757 Could you try again to see if this issue persists. ZTE told me they've cleaned up the fake packages on their FOTA this morning. There should be no prompt for the OTA update now. The root cause is ZTE put a fake FOTA package (.mar and .xml) for test but forgot to remove .xml afterward. That's why the phone keeps prompting the update for user and there may be also 404 error when trying to get .mar file.
Flags: needinfo?(khu)
(In reply to Ivan Tsay (:ITsay) from comment #8) > That's why the phone keeps prompting the > update for user and there may be also 404 error when trying to get .mar file. I switched my phone back to checking for Daily updates (I had set to monthly due to his bug) and hit 'check now' and so far have not been prompted. Does this mean ZTE will not yet provide an OTA update for v1.1.?
This seems to be fixed now. I did have to restart the phone to clear the notifications.
The issue is resolved for me as well.
resolved per above comments
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I tried as well but after clicking the "Check now" I still get the "There is an error while downloading the updates" error message. It's a ZTE Open: OS-Version 1.0.1.0 Firmware revision V1.01.00.01.019.144 Build id 20130723181018 And I was not able to download the last_log file, the adb command gives: > adb pull /cache/recovery/last_log remote object '/cache/recovery/last_log' does not exist Is there another way to get more information on what maybe failed?
See comment 10. I had the same problem but power cycling the phone cleared the issue.
The power cycling doesn't resolv the issue for me. I always have "There is an error while downloading the updates" error message. Regards
Well, same Problem here. logcat gives: --8<-- I/Gecko ( 114): *** AUS:SVC Checker:getUpdateURL - update URL: http://firefox.ztems.com/prerelease/roamer2/18.0/20130723181018/update.xml?force=1 I/Gecko ( 114): *** AUS:SVC Checker:checkForUpdates - sending request to: http://firefox.ztems.com/prerelease/roamer2/18.0/20130723181018/update.xml?force=1 I/GeckoDump( 114): XXX FIXME : Got a mozContentEvent: force-update-check D/memalloc( 114): /dev/pmem: Allocated buffer base:0x4c001000 size:57344 offset:3579904 fd:166 D/memalloc( 500): /dev/pmem: Mapped buffer base:0x46329000 size:3637248 offset:3579904 fd:55 I/Adreno200-EGLSUB( 114): <CreateImage:991>: Android Image I/Adreno200-EGLSUB( 114): <GetImageAttributes:1200>: RGBA_8888 D/memalloc( 114): /dev/pmem: Freeing buffer base:0x4c35d000 size:57344 offset:3522560 fd:133 D/memalloc( 500): /dev/pmem: Unmapping buffer base:0x45f3a000 size:3579904 offset:3522560 I/Gecko ( 114): *** AUS:SVC Checker:onProgress - 1049/1049 I/Gecko ( 114): *** AUS:SVC Checker:onLoad - request completed downloading document I/Gecko ( 114): *** AUS:SVC Checker:updates get - unexpected node name! I/Gecko ( 114): *** AUS:SVC Checker:onLoad - there was a problem checking for updates. Exception: Error: Unexpected node name, expected: updates, got: parsererror I/Gecko ( 114): *** AUS:SVC Checker:onLoad - request.status: 404 I/Gecko ( 114): *** AUS:SVC getStatusTextFromCode - transfer error: Update XML file not found (404), code: 404 I/Gecko ( 114): UpdatePrompt: Setting gecko.updateStatus: check-error-http-404 I/Gecko ( 114): *** AUS:SVC UpdateService:onError - error during background update. error code: 1404, status text: Update XML file not found (404) I/Gecko ( 114): UpdatePrompt: Update error, state: , errorCode: 110 I/Gecko ( 114): UpdatePrompt: Warning: no patches available in update I/Gecko ( 114): UpdatePrompt: Setting gecko.updateStatus: Update XML file not found (404) --8<-- The ZTE url is not working. Perhaps it's the bug is not yet resolved? It seems to me it's also a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=907827
(In reply to Daniel [:krrrcks] from comment #17) > Well, same Problem here. > > logcat gives: > > I/Gecko ( 114): UpdatePrompt: Setting gecko.updateStatus: Update XML file > not found (404) > --8<-- > > The ZTE url is not working. Perhaps it's the bug is not yet resolved? > > It seems to me it's also a duplicate of > https://bugzilla.mozilla.org/show_bug.cgi?id=907827 Yes that issue seems to be bug 907827. The bug here was different. It was unrelated to manual checking for update. This bug was about the automatic check always deciding there was an update and displaying a notification that an update was available. If you tried to apply the update, it would immediately result in a new notification about an update being available.
Blocks: 907827
SO, I went to the ZTE website and downloaded what they claimed is the orgianal software for the device, loaded that onto my sdcard and did an update form the sdcard and it still says it is US_DEV_FFOS_V1.0.0B02 I am not at all sure this issue is still understood.
The fix for this bug was to ask our partner to remove the fake FOTA package from their production server. As mentioned in comment 8, our partner accidentally uploaded a fake FOTA package when they tried to test the FOTA update for the carrier version. Regarding the latter comments in this bug about the bad URL (also seen in bug 907827), it was also fixed at that time when the partner uploaded back the released xml file.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: