SIM connection often lost ZTE Open C

I'm running latest-mozilla-b2g32_v2_0-flame on the ZTE Open C and after having no issues for about a week now the SIM card connection gets lost. I restarted once (removed battery) and this worked. But now not even that works.
Also, is there a way I can install pure android on the phone. This problem is rather painful and considering I purchased what was supposedly a well supported firefoxOS phone I'm getting to the point of utter annoyance with this problem. If it can't be solved I could at least reserve some patience for the project if I can still use this device and it wasn't a total waste of a purchase.

Hi vongesell,
I'm sorry to hear you are having issues with your ZTE Open C device. I understand that you are losing connection to your SIM card frequently.
Please follow these steps to reset your device back to factory settings:
'''Warning:''' '''''Resetting your phone will delete all data stored on the device, including apps, calendar data, email accounts, and settings.'''''
# Open the [[Image:Settings App (small)]] '''Settings''' application.
# Tap on the '''Device Information''' button.
# Tap on the '''More Information''' button.
# Tap on the '''Reset phone''' button.
# Tap '''OK''' to reset your device.
Please let us know if your problem persists after following these steps.
- Ralph

Similar Messages

My sim card is no longer recognized by the ZTE Open sold on EBay

After 6 month of happy usage of my ZTE Open, manually upgraded to Firefos OS 1.3.
My phone suddenly does not recognize my sim card any more.
I performed some tests with other phones, other operators, and other sim cards that lead me to tell that the problem comes from the phone.
There was no special event that can explain this problem (no fall, no update, no water...).
I tried to retart the phone, to reset it. No way the sim card is recognized.
I seem to be able to call and receive phone calls, but no sms and no data.
Can you please help ?

Same thing with me, but SMS and data seem to work fine. Only seems to affect Usage app on my phone (ZTE Open C).

How to connect ZTE Open C with Firefox OS 1.3 to a calDAV server of Synology DSM 5.1?

Hi,
I am running Firefox OS 1.3 on a ZTE Open C. I am trying to connect the calendar of the phone to a calDAV server of a NAS of Synology running DSM 5.1 (newest release).
I go into the calendar app of the phone and configure the calDAV account:
username: testuser
password: *******
URL: https://192.168.1.251:5006/testcalendar
The calendar does not connect and the error message the phone shows is:
wrong login and/or password
Some background information:
1. I am successfully connecting to this calendar from a Windows 8.1 PC (Firefox Lightning), an Apple iPAD (Apple Calendar), and a Linux notebook (Firefox Lightning). So the URL, the login and the calendar work ok.
2. I am successfully connecting with the firefox browser of the phone using https to the mangagement interface (port 7001) of the NAS (the certificate is flagged as "untrusted" and a permanent exception has been made). So login with https works ok in principle.
3. I get the same error message "wrong login and/or password" under DSM 5.0. So it is not a problem of the version of the Synology DSM calDAV server
4. I get the same error "wrong login and/or password) with an unsecure connection using http and the respective URL: http://192.168.1.251:5005/testcalendar (beware of the changed port number using http). So it is not a problem of the ssl-connection.
I have connected the phone to the linux machine and generated the log by running:
sudo adb logcat -v time > calendar.log
Here is are the results of the log (I have made 1 unsuccessful attempt to connect to the calDAV server on 11-16 14:26 and 2 unsuccessful attempts on 11-16 14:27. I am not sure for which message to look for so I just have the sections that contain most probably the bug (If required I can of course provide the full log or even re-test and re-log). my guess for the bug is:
11-16 14:26:34.448 D/wpa_supplicant( 2965): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
or
11-16 14:26:34.448 D/wpa_supplicant( 2965): nl80211: survey data missing!
Some help is very appreciated!!
(and thanks for you guys at mozilla for https://support.mozilla.org/en-US/questions/1027436#question-reply which gave me an idea how to debug)
If you need further infos, logs, etc. please let me know.
11-16 14:26:33.758 D/AudioHardwareALSA( 276): setVoiceVolume(1.000000)
11-16 14:26:33.858 D/TrackUtils( 280): livesLocally = 0
11-16 14:26:33.858 W/TrackUtils( 280): AudioTrack created for streamType =1, flags =0
11-16 14:26:33.858 W/TrackUtils( 280): We donot need to inform HAL
11-16 14:26:34.448 D/WifiHW ( 280): wifi_send_command 'SIGNAL_POLL'
11-16 14:26:34.448 D/wpa_supplicant( 2965): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
11-16 14:26:34.448 D/wpa_supplicant( 2965): wlan0: Control interface command 'SIGNAL_POLL'
11-16 14:26:34.448 D/wpa_supplicant( 2965): nl80211: survey data missing!
11-16 14:26:35.028 D/TrackUtils( 280): setFastFlag - flags b4 = 4 , streamType = 1
11-16 14:26:35.028 D/TrackUtils( 280): ULL for ringtones/Alarm/Notification/system sound/enforced audible
11-16 14:26:59.448 D/WifiHW ( 280): wifi_send_command 'SIGNAL_POLL'
11-16 14:26:59.448 D/wpa_supplicant( 2965): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
11-16 14:26:59.448 D/wpa_supplicant( 2965): wlan0: Control interface command 'SIGNAL_POLL'
11-16 14:26:59.458 D/wpa_supplicant( 2965): nl80211: survey data missing!
11-16 14:27:03.338 E/Profiler( 1987): BPUnw: [1 total] thread_unregister_for_profiling(me=0x1b74520) (NOT REGISTERED)
11-16 14:27:04.458 D/WifiHW ( 280): wifi_send_command 'SIGNAL_POLL'
11-16 14:27:04.458 D/wpa_supplicant( 2965): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
11-16 14:27:04.458 D/wpa_supplicant( 2965): wlan0: Control interface command 'SIGNAL_POLL'
11-16 14:27:04.458 D/wpa_supplicant( 2965): nl80211: survey data missing!
11-16 14:27:06.318 D/SST_QC_B2G( 280): Signal Strength changed; sending info to content process
11-16 14:27:06.318 D/SIGNAL_STRENGTH_QC_B2G( 280): GetDbm = -105
11-16 14:27:06.318 D/SIGNAL_STRENGTH_QC_B2G( 280): GetRelSignalStrength = 12
11-16 14:27:06.328 D/SIGNAL_STRENGTH_QC_B2G( 280): GetDbm = -105
11-16 14:27:06.328 D/SIGNAL_STRENGTH_QC_B2G( 280): GetRelSignalStrength = 12
11-16 14:27:06.328 I/Gecko ( 280): -*- [SUB0] QCContentHelper_QC_B2G: sendMessage to content process: RIL:VoiceInfoChanged{ connected : true, emergencyCallsOnly : false, roaming : false, type : 'umts', signalStrength : -105, relSignalStrength : 12, network : { mcc : '228', mnc : '03', longName : 'Orange', shortName : 'Orange', }, cell : { gsmLocationAreaCode : 9001, gsmCellId : 304145, cdmaBaseStationId : -1, cdmaBaseStationLatitude : -2147483648, cdmaBaseStationLongitude : -2147483648, cdmaSystemId : -1, cdmaNetworkId : -1, }, state : 'registered', }
11-16 14:27:06.328 I/Gecko ( 280): -*- QCMessageManager_QC_B2G: Received sendTargetMessage with topic='mobileconnection', message='RIL:VoiceInfoChanged'
11-16 14:27:06.338 I/Gecko ( 280): -*- [SUB0] QCContentHelper_QC_B2G: sendMessage to content process: RIL:DataInfoChanged{ connected : false, emergencyCallsOnly : false, roaming : false, type : 'umts', signalStrength : -105, relSignalStrength : 12, network : { mcc : '228', mnc : '03', longName : 'Orange', shortName : 'Orange', }, cell : { gsmLocationAreaCode : 9001, gsmCellId : 304145, cdmaBaseStationId : -1, cdmaBaseStationLatitude : -2147483648, cdmaBaseStationLongitude : -2147483648, cdmaSystemId : -1, cdmaNetworkId : -1, }, state : 'registered', }
...

Hi Ralph,
thanks a lot for the quick response. This is very appreciated! I will try to equally give you all the information required as quickly as possible.
1. CalDAV Log on Synology:
I have tested the connection between the calDAV client on ZTE Open C (Firefox OS 1.3) and the calDAV server on Synology (DSM 5.1) again and I get the same bug "wrong login and/or password". The logs on the Synology NAS show the following (Synology NAS: Control Panel-> File Services -> webDAV -> Advanced Settings -> View Logs -> Select: Connection)
User [testuser] from [192.168.1.6] failed to login in via [WebDAV] due to authorization failure
2. Seperate Folder/Files for calendar on Synolgoy
I have setup the CalDAV files on Synology NASin a dedicated folder. The calendar ist in https://192.168.1.251:5006/dir_PersonalCalendars/testcalendar . Unfortunately the error on the ZTE Open C is the same as before: "wrong login and/or password" .
Interesting is, that if I mis-type the folder or the calendar name, then I get on the ZTE Open C the error: "Something is wrong. Try again later".
This suggests that the folder and files are well recognized when loggin in.
Hope that helps you to continue. If you need something more, than please let me know.
Thanks,
Schaefi

My iPhone 4 has lost SIM connection several times over the past week when the phone is left on continually. I have had the SIM checked and it was not the source of the problem. I have found that I can reactivate the SIM by switching the phone off and on.

My iPhone 4 has lost SIM connection several times over the past week when the phone is left on continually. I have had the SIM checked and it was not the source of the problem. I have found that I can reactivate the SIM by switching the phone off and on again. Has anyone else experienced this problem and if so, is there an easy fix. I have been advised by Apple that the latest IOS update may overcome this situation but I'm only on slow download speeds and 690 Mb would take forever. I would appreciate any advice.
Best regards,
Rob.

PinguXeF wrote:
, while I have taken a backup of the iTunes Library,
this means nothing if it was not done correctly...
To have EVERYTHING on a New Computer...
From your OLD computer...
Copy your ENTIRE iTunes FOLDER to an External Drive... and then from the External Drive to your New Computer..
Full Details Here > http://support.apple.com/kb/HT1751

I have the ipad2 with the latest Os upgrade. On certain websites, I get the following error message: cannot open page. Safari cannot open the page because the network connection was lost. I have rebooted, turned off wifi and reset the password.

This is happening to only certain websites. Unfortunately, the work ones that I need to access. I appreciate any help.
Error message:
Cannot open page
Safari cannot open the page because the network connection was lost
I reset the wifi and the password, I also rebooted several times.

Do you have any other browsers on your iPad? If you don't have one, why don't you try downloading one of these free browsers - they will all be "lite" versions (not full featured) - but if you can access these websites with one of those - then I assume that we can point to Safari as being the culprit. That will not solve the Safari problem, but it will give us another point from which to work.
http://www.google.com/search?client=safari&rls=en&q=free+ipad+web+browsers&ie=UT F-8&oe=UTF-8
I have Mercury, iCab Mobile, Opera, Dolphin and Atomic. iCab Mobile - the paid version is great.
BTW ... have you tried to access these sites from another WiFi connection - like a library, a friend's house - any other WiFi network?

"Hotspot login could not open the page because the network connection was lost"

So, I've been trying to connect to the login for our school's wifi for a while now, but instead of like going into the sign in spot where you accept the terms of use agreement for our wifi, the pop up screen says "Hotspot loging could not open the page because the network connection was lost". This is on my iPod touch 2nd Generation, and I've never had this problem before, but it popped up like 4-5 weeks ago, and I haven't been able to log in since. Anybody else solve this problem/ have it and could give me advice on how to solve it? That would be great, thanks and see you fellow Applers later!!

1. Double-click the Home button to reveal Task Bar at bottom
2. Hold the Safari app down for a second or two until you see the minus sign
3. Tap the minus sign to close app
4. Re-launch the app and test
Note: If necessary close all apps in the Task Bar

Hotspot login cannot open the page because the network connection was lost. Why?

Everyttime I try to connect to the wifi, all I get is about a second of the phone saying it is connected, before I get a login page, with the web adress of "captive.apple.com".
The login page is black, and after about a second I get the message,
"Error Opening Page: Hotspot login cannot open the page because the network connection was lost"
I've tried restarting the phone, resetting the network data, everytihng I can think of but no luck.
How can I fix this?

Good day everybody. I had the same issue and I got crazy but keep up work on it about 1 week to have the resolution.
Here is the simple steps to overcome this problem:
1. Choose your Wifi and get connected
2. On Wifi page at the bottom Turn On 'Ask to Join Networks'
3. Connect to your Wifi,
4. After connecting, you will see a blue next to your selected Wifi
5. Press the blue and get into the connection detail of your wifi
6. Turn on Auto-Join
7. Turn Off Auto-Login
8. Close settings
9. Go to Safari log with Hotel, Business wifi page
Trick is the Auto-Login must be turned off

Getting "safari cannot open the page because the network connection was lost" on a popular UK electrical retailer when trying to click and collect, yet I have excellent 3G and WIFI connections

When I try and use a click and collect service via a popular electrical retailers website in the UK I get " safari cannot open the page because the network connection was lost"
I have a superb WIFI connection and have tried it via 3G.
I am not getting this on other websites, however have recently updated Safari.
Any ideas?

Install Chrome and see if the problem lies with Safari...that's where it was with my mini.

TS3048 My wireless mouse often loses connection. I replace batteries and it works for a few days before becoming problematic again. Battery currently shows 100% and connection is lost intermittently. Bluetooth is on and wireless keyboard works. Any sugges

My wireless mouse often loses connection. I replace batteries and it works for a few days before becoming problematic again. Battery currently shows 100% and connection is lost intermittently. Bluetooth is on and wireless keyboard works. Any suggestions?

Is it possible that you have a bad bunch of batteries?
My Magic Mouse on one computer and the Mighty Mouse on another use batteries I bought through the Apple store (with a charger). They last a long time.
http://store.apple.com/us/product/MC500LL/A/apple-battery-charger
Another possiblity is that the mouse is defective. Since the keyboard connects, it has to be the mouse or the batteries.

Visual Admin often lost connection

Hi experts,
I login to Visual Admin , the connection was lost about 5 seconds.
If I login again, the connection will lost again.
It pop-up a message "Ping time out. Conection server is lost!" .
But the J2EE is running well, all stutas in MMC is green.
The userful information in log files as follow :
Caused by: java.io.EOFException: End of stream is reached unexpectedly during
input from Socket[addr=/192.168.0.27,port=50704,localport=3748]
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
com/sap/sldserv/vaclient/ClientManagementGui$WaitForServiceIf
Caused by: com.sap.engine.services.rmi_p4.NoSuchObjectException: ID:011781:
Object:<security>
     at
com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getInitialObject
(P4ObjectBrokerServerImpl.java:959)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:396)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:129)
exceptions.BaseLoginException: Cannot create new RemoteLoginContext.
Please give me some advice !
Thanks.
BR,
Jianguo Chen

Hi
Check the following link
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/4a/f434417f222004e10000000a155106/content.htm">Ping Timeout Connection to Server Is Lost</a>
Hope it helps you..
Regards
ambicasony
null

How can I unbrick ZTE Open thats lost fastboot?

This is what has happened. As a complete newbie, rooted the phone and flashed clockwork recovery for roamer2. Then used the update zip from ZTE support in the recovery mode, but since it failed verification, I manually removed from asserts in the update-script and repackaged/zipped it up. Now recovery failed with reason installation failed. But ended up with fastboot. Using this fastboot I could not flash the stock boot.img or any other image. During some of this tries something i did caused to loose fastboot as well and now the phone is bricked. It is recognised in USB with vendor id: device id as 19d2:0112.
I would appreciate, if you can guide me to tools that can flash back fastboot on the phone which just provides the above mentioned usb device.

Keep in mind that I am a bigger noob than you, since I have not yet used fastboot.
Have you checked Mozilla's [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN ZTE OPEN page]?
It has all the answers.
To summarize:
# You do not need to root the phone to use fastboot.
# The checksum for ZTE's image does not work. I have already mentioned this in [/questions/971252] and got no response. They did secure the download with SSL, whatever that is worth.

Update problems, no space left on device (ZTE Open)

I just received a ZTE Open device in the mail today, and after playing around with it a bit, I noticed that every time I tried to check for system updates, it would show me one 13.xx MB update, which I downloaded, apparently applied, and the phone seemed to restart itself, but then I would be shown the same (??) update available. The phone is without a SIM card, just playing with it connected via Wifi, with the 4GB microSD card installed. Then, this evening, I got an error message, which apparently was recorded on the SD card, a file called recovery.log (contents follow):
<pre><nowiki>Starting recovery on Fri Aug 23 07:29:21 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"
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
E:Error in /cache/recovery/log
(No space left on device)
E:Error in /cache/recovery/last_log
(No space left on device)
mtd: successfully wrote block at 0
I:Set boot command ""
E:Error in /cache/recovery/log
(No space left on device)
E:Error in /cache/recovery/last_log
(No space left on device)</nowiki></pre>
The SD card also contains a zip file in updates/fota/update.zip, which in turn contains patch/system/P752D04_DEV_US_20130726.zip, which contains: amss.mbn (about 20 meg) and boot.img (about 4 meg).

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.0'''B02'''. 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]

My new Zte Open c IMEI is disappeared after update.

Hello, I try to make a manual update on my Zte Open C following the instructions you provide here ( https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C ). Everything appear to be ok until the phone was rebooted(at 98% of the status bar). The phone boot perfectly but the upgrade tool alert me that the operation was unsuccessful. At that point I thought it was just a matter of recognizing the phone from the computer. However it was not, in fact, when I tried to insert the sim card I noticed that the phone could no longer connect to 3G networks. Looking into the details of the phone, I noticed that my IMEI was set to 0. Is there any way to restore my original IMEI?

Hi kRoLLh,
I have not experienced this problem on the ZTE Open C. It's possible that there is some issue with your specific device.
I would suggest contacting ZTE directly for additional support. I would also suggest contacting your carrier, and verifying that your network settings are all configured correctly in your Firefox OS.
Thanks,
- Ralph

Why does my ZTE open c Firefox OS smart phone forget the wlan settings and does not ring the alarm?

Sometimes it is even enough to go outside to the waste bin to let my smartphone forget the settings for the wireless lan. When I return I have to enter the - not so short - code from my wlan router again. After that the internet connection is running as it should.
Additionally the alarm clock does not work, I can set alarms as I like, setting the volume to the max and activate also the vibration alarm but nothing happens when the preset time is arrived, even when the alarm clock is shown on the screen the whole time. Is my phone broken? Or is it a bug in my Firefox OS installation?
Where does Firefox OS store these values for wlan connection and alarm times? Is there an internal database that is maybe corrupted?

Hi Markus,
I understand that you're having issues with the Wi-Fi connection and the alarm clock in your ZTE Open C device.
The alarm clock issue appears to be similar to what has been reported by other users and is being tracked on [https://bugzilla.mozilla.org/show_bug.cgi?id=1052245 bug 1052245].
Do you have more information regarding the alarm clock issues that you encounter? This may be very helpful to our engineering teams investigating. Please be aware that ZTE is the manufacturer of your device, and only they are able to release an update.
The wifi issue may be related to [https://bugzilla.mozilla.org/show_bug.cgi?id=923324 bug 923324].
Please reply to this message with the following information:
* What is the OS version and Build ID found in the Device Information page? Please visit [https://support.mozilla.org/en-US/kb/how-do-i-find-what-version-firefox-os-i-have this link] if you need help finding the Build ID of your phone.
* Please provide the exact steps to reproduce the issue you are encountering.
* How often do you encounter this issue?
Please be sure to include as much detail as possible, including any websites that may exhibit this issue, and any error messages that you may be receiving, exactly as they appear. This will ensure that we have all the necessary information to investigate this behavior.
- Ralph

Wifi module not working in ZTE Open

Hi all.
Bought this device ZTE Open! When I updated the firmware to v1.1 wi-fi module stopped working!
Current firmware: OPEN_US_DEV_FFOS_V1.1.0B01
=More information=
OS version: 1.1.0.0
Firmware revision: 01.01.00.019.215
Hardware revision revision: P752D04B02
Platform version: 18.1
=Git commit info=
2013-12-04

'''UPD: '''
Wi-fi access point see, connected.
But no packets, internet does not work.

SIM connection often lost ZTE Open C

Similar Messages

Maybe you are looking for