My ZTE OPEN C reboot randomly

My phone is OPEN ZTE C (bougth in France)
My OS version is 1.3
Sometimes, firefox OS restart when hit was in stand by. I don't know why. No application are opened when the problem came..
I have the model since 1 month and it reboot 5 times.

Hi galathil,
I'm sorry to hear that you are having issues with your newly purchased ZTE Open C device from France, and that it reboots randomly.
In order to better understand and investigate on the issue that you are encountering, 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 [http://mzl.la/Gzz6Kp 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.
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 will have all the information needed to investigate into this.
In the meantime, I would also suggest that you contact ZTE's support directly, since this may be a hardware-related issue.
You should also update your phone to the latest version available. If you wish, you may install an update that allows access to "Root" in the phone via [http://en.comebuy.com/developer-firefox-os-open-c.html this link].
Thank you for your help and we look forward to hearing from you!
- Ralph

Similar Messages

ZTE Open C reboots during calls

The phone reboots during calls. OS version 1.3, latest according to ZTE.
Thing is, only when it is set to use 3G. But if I set to 2G the audio is absolutely terrible.
Both when using 2G and 3G sometimes the calls get cut-off on the receiver phone. I can hear the other person talking but the other person doesn't hear anything. This is another issue.
What can I do? The phone was bought from Ebay on September 2014.
Problem didn't start now, ZTE Ebay support said the issue was a SIM one. I recently changed to 3G because the noises in 2G are almost unbearable.

''Ralph Daub [[#answer-713346|said]]''
<blockquote>
Hi Falconet,
I understand you are experiencing rebooting and call quality issues on your ZTE Open C device.
Since ZTE is responsible for the Firefox OS build specific to your device, I would suggest following their advice.
You may be able to request a new SIM card for your device by contacting your carrier support.
I hope this resolves your issue. Please let us know if you have any other questions about your Firefox OS device.
Thanks,
- Ralph
</blockquote>
Hi,
What ZTE meant was changing carriers not just sim card. I can't do that for another 1.5 years. The reason they said is because the phone seemed fine for a while when using another carrier. Sadly, the SIM is fine since another SIM card from the same carrier does the same. Both are working fine on Android Phones.

I can't upgrade my ZTE Open to 1.2 or 1.1 using their instructions.

I recently bought a ZTE Open off of eBay in the US. I'm currently working on building an app for the phone.
I need to upgrade to 1.2 to use the Firefox emulator that comes with FF nightlies now and test out this app on a real device. It's currently running OPEN_US_DEV_FFOS_V1.0.0B01
I've tried the Fastboot method, but... *sigh* this is one of the broken versions so that's out. The recommendation from Mozilla is to upgrade via the SD method with the image provided by ZTE on their site.
I went out and bought an SD card to do this (!) and have tried all of the .zip files and followed the instructions from ZTE (and the Mozilla Hacks blog). I've tried a ton of different things and read all the comments... but...
Frustratingly, it keeps saying "E:Signature verification failed" and won't flash when using the SD card installation in the recovery menu thingy. The thing is... the files are fine! I can select it... I'm 99% sure I'm not being an idiot. I've tried the 1.2 images as well. Nothing will verify! Nothing! :(
The phone boots up fine afterwards and I come back and try and do more googling.
Help! All I want to do is support this new OS, but... man, I've put about 5 hours of time into this so far... just the phone!

Hi,
Sorry for the delayed reply. Thanks for using and supporting Firefox OS with your new app!
I found a similar thread on stackoverflow related to the fastboot not working that suggested to do '''adb devices''' and '''adb reboot bootloader''' before using any of the fastboot functions. Not sure if that will help you if you have one of the first ZTE Opens though.
I don't think you are alone in this signature verification failed issue at all, do not feel like an idiot, we have asked ZTE to loosen the keys on the files because of this problem for several months (I will ping my contact on our side about this again to see about it).
Here is the stackoverflow in case it is helpful:
http://stackoverflow.com/questions/tagged/firefox-os
Regards,
Michelle Luna
Firefox OS Support Manager, Mozilla

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

ZTE Open C crashes during calls.. Falsh

Hi
I bought a ZTE Open C, and unfortunately it frequently reboots when I answer or initiate a call. After the reboot it usually lets me retry the call succesfully, but it is very disruptive for answering calls
I have colleagues with the same issue who got the ZTE Open C at the same time as me. We work in a position where we take a lot of calls on our mobiles and we cannot see who calls (routed through a PBX) and so we cannot call back and it is very bad for customers :-/
I was wondering if there is an update to the dialer app, or if someone knows how I can maybe flash the phone to 1.4 FFOS or 2.0 or something ?

Hi Michelle
Under settings, it is set to Ask, but it does not ask me to send one ever when this happens, so no reports have been sent. I have for good measure now set it to Always Send.
We are 4 people with this issue. The number of restarts vary depending on the number of calls. I have had 1 restart in 1 hour today, but yesterday I had 3 in an hour and sometimes less, it does however happen consistently and both in in- and outgoing calls
We are all in Dublin, Ireland, but using a Danish cell carrier called TDC. Phones are connecting to the Vodafone Network in Ireland

Return stock bootloader to ZTE Open C

Recently, I followed a guide on how to install android 4.4 on a zte open c, mostly to see how it was:
https://www.youtube.com/watch?v=axOYIfo7y2s
After quickly getting bored and wanting to return to Firefox OS, I installed the 'droid to FFOS package, but it appears that I'm still stuck with the custom bootloader that android needed to install?
How might I get rid of this? I've tried running `sudo fastboot boot boot.img`, it worked for that boot but not for when I rebooted it; I'm presuming this is because it doesn't over-write the existing boot image?
Thanks in advance,
Johnny

I fixed this on my own.
And for you information that is the exact tool that I used.
And I'm not a novice; I know what a root shell is and I wouldn't have said that I have root if I didn't.
Maybe read the post before assuming you know more than the poster...
Anyway...
i just built cwm for the device and using the rooted shell dd'd the factory recovery image and dd'd the new one.
then i installed the ZTE Kis 3 firmware with the new recovery
then i rebooted to the bootloader and did "sudo fastboot oem unlock" and the bootloader was unlocked.
this did not working following the aforementioned guide using only the upgrade tool otherwise i wouldn't have posted.

ZTE Open C crashes during calls

Everything is in the title, my phone reboots sometimes automatically during some calls.

Hi HoplaMouais,
I'm sorry to hear you are having issues with your ZTE Open C device restarting.
This issue has also been reported by other users, and our technical account managers have been made aware of this problem, so that they can communicate it to ZTE:
* [https://support.mozilla.org/pt-BR/questions/1003430 Forum Thread - ZTE Crashes during calls]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1017604 bug 1017604]
You may also contact ZTE, the maker of your device, for more information.
- Ralph

ZTE Open 1.1 : STILL error downloading updates

So after 4 months (!), there is finally an update for the ZTE Open to 1.1
After bricking devices, withholding updates and a generally sucky experience, we now finally receive the update that will deliver us!
Right..?
...oh no, wait. Sorry, my bad.
"There was an error when checking for updates"
"Error while downloading the updates"
So after all this time, the best Mozilla and ZTE could manage was, apparently, to have the same @#$%ing problems in the new update that were there in the previous version.
Screw you guys, I'm going home (to Android*, which, y'know, actually works).
*: Because the moderators asked us to compare to Android, if I remember correctly.

I got the download for the official 1.1 update from ZTE. I have followed the instructions, but when the phone rebooted it goes to a blank screen after playing the firefox boot animation. I let it sit there for about 10 min and it wouldn't respond. Finally had to pull the battery.
I tried the md5 check, and I get the following error:
Finding file_list package...
Opening file_list package...
Verifying file_list package...
E:failed to open /system/etc/verify.zip (No such file or directory)
E:signature verification failed
I tried to reinstall the update and got this:
-- Install /sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Is there a way to restore my phone? I've been searching the internet and I keep getting linked back to the ZTE Open site, but the old images seem to have been removed.
Right now, when I boot the phone I get the FireFox OS logo, then the fox animation, then I get a quick bright flash of white before the screen goes out.
If anyone could help me, I would appreciate it. Thanks in advance.

IMac rebooting randomly...

Hi,
Just now, my iMac randomly restarted while Firefox was open. This has happened a couple of times before. I don't know if the problem is related to Firefox though.. just in case.
Does anyone know why my iMac would be rebooting randomly?
Thanks.

it just logged out again, so this is what the console log said:
Nov 16 18:24:19 -imac-g5 IíI[173]: sleep demand recorded: Sun Nov 16 18:24:19 2008\n\n
Nov 16 19:54:54 -imac-g5 configd[35]: SecKeychainFindGenericPassword err= -25308 ( =0xffff9d24, secErrStr=User interaction is not allowed. ) (current= Network)
Nov 16 19:55:01 -imac-g5 mDNSResponder: ERROR: Only name server claiming responsibility for " iMac G5." is "."!
Nov 16 19:55:01 -imac-g5 mDNSResponder: HostnameCallback: Error -65538 for registration of iMac G5. IP 121.209.19.156
Nov 16 19:55:04 -imac-g5 IíI[173]: sleeptime recorded: Sun Nov 16 18:24:19 2008\n\n
Nov 16 19:55:04 -imac-g5 IíI[173]: waketime is: Sun Nov 16 19:55:04 2008\n\n
Nov 16 21:00:17 -imac-g5 loginwindow[63]: sendQuitEventToApp (MicrosoftMouseHelper): AESendMessage returned error -609
The system log said:
Nov 16 21:00:17 -imac-g5 loginwindow[63]: sendQuitEventToApp (MicrosoftMouseHelper): AESendMessage returned error -609
Nov 16 21:00:28 -imac-g5 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Nov 16 21:00:29 -imac-g5 loginwindow[306]: Login Window Started Security Agent
Nov 16 22:03:34 -imac-g5 kernel[0]: Stealth Mode connection attempt to TCP 10.0.1.3:51888 from 203.36.59.41:80

Faulty capacitors syndrom - W1100Z reboots randomly under load

I've had this problem since I've acquired this Sun W1100Z workstation: it reboots randomly, particularly if there is a sudden peak in CPU load.
At first I thought it was due to a faulty 3D card, but I tried a few, it doesn't make a difference, and it even reboots when no 3D is used. Some games or 3D programs on Linux cause the reboot within seconds (2nd Life) while others seldom do (Google Earth, ET:QW). I haven't spent much times in Windows, but gave it a try (Win 2k iirc): rebooted randomly just the same.
After having tried all other possibilities (even switched out the power supply and RAM), and lost hundreds of work hours to this, I have come to the conclusion that the motherboard was toast from the beginning.
Does anyone have a similar experience? Does Sun have an extended warranty for this kind of severe malfunction, I know many vendors have extended warranties for busted caps mobos.
Any insight appreaciated. I'd rather do something useful with this expensive doorstop.

Since you're asking about `extended warranties`
we can presume the original one-year warranty
is long gone and you didn't purchase a service plan.
The only way to determine any additional coverage is to contact Sun.
(these forums are NOT Sun techsupport)
Begin the process of opening a support case.
Ask whether there are any FIN's or FCO's on the W1100z.
FIN = Field Informational Notice
FCO = Field Change Order
Keep in mind that such FIN/FCO's have expiration dates.
They do not exist for all eternity.
Lastly.
Go to the Sun System Handbook (SSH) resource page for your W1100z system.
Click on the SunAlert link. Let that page load completely.
(be patient, it's a loooong page)
There is one reference to a patch for the W1100z/W2100z systems for instability.
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102026-1

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 update apps in a ZTE Open (with FFOS 2.0 custom build)?

I have a ZTE Open I regularly update trough custom builds. In particular, I updated it to the 2.0 version by:
BRANCH=v2.0 VARIANT=user ./config.sh inari
BRANCH=v2.0 VARIANT=user ./build.sh
The operation has apparently been successful, and by the test apps being missing I guess that I really built and flashed the user variant.
Now, I do not expect system updates to work, as I heard that the inari update channel has been shut down.
Though, I would expect it to at least automatically update the third-part apps from the Market store. This does not seem to happen: I have outdated apps (Loqui IM v3.1, in particular) but the "Check now" button from the Settings has no effect (it says "Checking for updates", but nothing else happens).
Moreover, I do not remember of having ever received an update with previous build, so I guess it may be not a problem with this particular build.
Is there something I can do about it?

Are other ZTE Open users with a custom build experiencing the same problem? Do you receive any app update at all?
I can't tell whether there is a problem in my build, in some setting or in the device.

Apps wont open after reboot and reinstall

apps wont open after reboot and reinstall

yeah that was a bit open wasnt it.. sorry..
i have 10.8.2 mountain lion, just did a reboot and pulled my original user from my back up back into the new system, opened a new user profile that is the same name as the one i had backed up.
now i cant open up anything in Iworks 09... or anything inb microsoft office 2011, plus i can open garage band.... i used time machine retore to retrieve those apps... but they come up with errors
any ideas other than trying to reinstall thses.?

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

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 ZTE OPEN C reboot randomly

Similar Messages

Maybe you are looking for