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.

Similar Messages

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]

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

ZTE Open C doesn't have root access after running unlock tool

I've ordered a ZTE Open C from Ebay from UK, and I wanted to unlock the bootloader.
I followed the instructions from here (http://en.comebuy.com/developer-firefox-os-open-c.html), installed the EU version (I've ordered the phone from Hungary), but if I boot into recovery mode, I still see that the recovery version is 0B04, however it should be 0B06, and the phone isn't rooted due to this (adb shell getprop ro.secure) command (it's said 0, and as far as I know, it means it doesn't rooted).
I want to use android on the device, but now, I even can't install neither the kitkat nor the firefox rom (it said verifivation error) Could you help me how to install Kitkat on device with gapps?

Hi Lukibeni,
I understand that you tried to update your ZTE Open C from Ebay using the image provided on the Comebuy page, but that the update appears to have been unsuccessful.
I would suggest attempting to download your image again, and go through the update process one more time.
If the issue persists, you will need to contact ZTE for additional support. ZTE is the OEM (Original Equipment Manufacturer) who created the device-specific build and update tools.
Please let us know if the update process works the second time around.
Thanks,
- Ralph

How do I correctly update ZTE Open C

Hello.
I have a ZTE Open C with unlocked bootloader and a 1.4 build installed. I re-flashed to 1.4 instantly after the phone was delivered.
My question is, how do I correctly update it from source without loosing my data?
Currently, I'm pulling the latest source from git, doing this:
git pull
./repo sync -d
And then flash it to the phone using.
./build.sh gecko
./flash.sh gecko
Than a change directory to gaia and build/flash it using:
make clean && make install-gaia
All flashes okay, without any errors but I still got old build identified in More Information:
20140703092209
instead, the Git commit info is updated:
2014-07-07
f2c11876
Does this mean I'm correctly updating if the git commit info changes? Or something is wrong?
Thanks in advance.

Hi svnpenn,
The point of my comment was to express my excitement that ANTONBORODA was able to manually update his device, and to show my appreciation that he shared his findings in the forums.
These support forums are geared towards user-facing issues. This means that development, manual updates, and porting of devices is not usually supported.
This was the second reason for my comment: to set the correct expectations for users with developer-related questions who may come to this thread through Google searches. Users looking for this type of support are more likely to find help in developer-related pages like [https://developer.mozilla.org/en-US/Firefox_OS MDN] or [http://stackoverflow.com/questions/tagged/firefox-os StackOverflow].
However, the main reason for replying was to welcome ANTONBORODA to the community and recognize his contribution to the support forums (by sharing his findings). I hope this helps you understand my reasoning.
- 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

I installed Android on my ZTE Open C and went back to Firefox and my 3G won't work. (Optus)

Hello. I'm from Australia and I recently purchased a ZTE Open C. I wanted to try Android on it and I installed it to do exactly that. I went back to Firefox OS to discover my 3G won't work, even though it did with the stock version of Firefox. I'm on the Optus network. I have a feeling it has something to do with my APN settings but I can't fix it.

Hi AnthonyDickens,
I'm sorry to hear that you're having issues with your ZTE Open C after re-flashing it with a Firefox OS image.
Can you please list the exact steps or instructions you used to perform the porting of your device from Firefox OS to Android, and then back to Firefox OS? Please provide a link to the image files you used as well.
In the meantime, you may attempt the following APN settings listed on the Optus support site:
* [http://www.optus.com.au/business/support/answer?requestType=NormalRequest&id=1378&source=5&question=What%20are%20Optus%27%20Mobile%20Phone%20technical%20settings%20or%20APNs? Optus Mobile APNs and Technical Settings]
* [http://www.optus.com.au/business/support/answer?requestType=NormalRequest&id=1378&source=5&question=What%20are%20Optus%27%20Mobile%20Phone%20technical%20settings%20or%20APNs? Internet APN and Technical Settings]
Please let us know if this solves your issue, or if you have any other question about your Firefox OS device.
Thanks,
- Ralph

Return Stock transport Order referring to original Stock transport order

Hi,
We have a standard stock transport order process which involves PO creation and all relevant processes.
Now in case items received via STO are damaged or not good, then we create a return stock transfer order.
Is there anyway available in the system via which we can reference original STO to newly created return stock transport order. So anytime return STO is created for material, the requirement is opened again on original STO.
Looking forward for the response.
Cheers,
Ravi

Hi MBKM,
Thanks for the response.
But the requirement tracking number is information field only.
We want to automate re-opening of the requirement back onto original STO.
-Ravi

Loss of history, top site, etc in FFOS 2.2 on ZTE Open C

I updated my OPEN C to 2.2 using packages from here : http://builds.firefoxos.mozfr.org/doc/en/devices/zte-open-c-eu , most recent build is 20150227165045.
I have 3 batteries, original 1500mAh, two 1850mAh from ebay (they are designed for ZTE V768, but works good with OPEN C).
Yesterday, I switched out one 1850 mAh battery, and put in another. First system couldn't see the battery status of the 2nd battery (should be near 100%, but OS insists its <20%). So I did a battery pull for a few minutes and put 2nd battery in again. This time, the system see the proper battery percentage, but since that, there is no top site nor history in the browsers. Universal search also doesn't return any history records. I had to reset the phone.

Hi crislevin,
I am sorry to hear about the loss of history and top sites on your ZTE Open C device.
Unfortunately, it's possible that either the unofficial build or the unofficial battery may have caused problems with the phone and eventually the loss of data.
Please contact ZTE's support channels directly for further assistance. They are the manufacturer of your device and may be able to further assist you.
Thanks,
- Ralph

Notifications panel doesn't open on ZTE Open version B2G 1.3.0.0-prerelease

My Notification panel isn't opening. I'm running the latest version of FFOS, I updated today. A previous version of a few days ago had the same problem. The original version I got with the phone, I think it was v1.1 didn't have this problem. So is there any way I can fix the problem00?
Thanks!

@linuxholic: I flashed it by cloning and setting up the whole FFOS Repo. You have to then build the FFOS version you want. And then you have to flash it to your phone using ADB (Android Debug Bridge). I did all this on Ubuntu and advise you to do it on any Linux OS...
Read through this guide: https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN
And then follow the instructions on cloning, setting up building and flashing FFOS here: https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS
Note: There's a small issue with ZTE Open that it doesn't correctly configure the bootloader on default builds. So it's mentioned on the page (first link) how to avoid this. You need to add a boot.img image to your build before flashing it. This is the page they link to: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html

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.

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.

RETURN STOCK TO BE TAKEN INTO UNRESTRICTED USE

Dear All,
              I am SD Consultant my requirement is that I have done return return delivery with PGR ,now my problem is that I want that stock in my plant in perticular storage location but it not showing to take return stocks ingiven plant what are the process.
             As per my little knowledge I need to transfer stock by MB1B but the issue is what are the movement types are need to be used.
             Thanks in advance.
Regards
AJIT K SINGH

return return delivery with PGR
The control is with your schedule line category. I am sure, for returns, you should be having a separate schedule line category which would flow into your return order.
Go to VOV6 select your schedule line category and execute. There maintain movement type 653 and save. Now create a return order and do PGR. Check where the returned stock is posted.
thanks
G. Lakshmipathi

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

Return stock bootloader to ZTE Open C

Similar Messages

Maybe you are looking for