Flashing a flame image on a zte open c

Hi,
I would like to upgrade my open c, currently in v1.3 to v2.1
I've checked this page:
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C
It says:
Warning: Trying to flash a full Flame image onto the device would brick the phone, so is not recommended.
But right below, it gives instructions to flash a full flame image.
So I'm wondering if it's safe or not.
Thanks

Hi Milarespa,
The '''full''' flash means that both Gecko and Gaia are flashed onto your device. This is the method that is likely to brick your device.
The procedure outlined under that warning is for a flash of only the Gaia portion of your device, leaving the Gecko alone. This should work, but please be aware that there is always the risk of bricking or experiencing bugs when flashing a custom version.
You also need to ensure that you are flashing the correct build for your device.
Please let us know if this answers your question, or if you have any other issues.
Thanks,
- Ralph

Similar Messages

Bricked ZTE Open C with flame(-kk) image

Hi,
in a state of mental derangement I have flashed my ZTE Open C with FLAME base image v180.zip:
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame/Updating_your_Flame
Now, the device is not working anymore (black screen). Any ideas or suggestions how to get my device back to life? I have tried the windows based "Open C Upgrade Tool" from ZTE but Windows (7) do not recognize my phone as USB device (some driver issues, "qhsusb bulk" is missing).

''nicnoc [[#answer-685831|said]]''
<blockquote>
Hi Ralph,
I can not turn on/off my device anymore ("black screen"). I also can not access the device through ADB or fastboot.
The device is recognized from my linux system as a Qualcomm modem:
$ lsusb
Bus 002 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
or in more detail:
$ lsusb -v
Bus 002 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QHSUSB__BULK
If I connect the device to my windows system for trying to use the windows based ZTE tools from here:
http://en.comebuy.com/developer-firefox-os-open-c.html
windows is asking me for the QHSUSB__BULK driver ...
</blockquote>
I get the same under linux but I do get Windows coming up with:
Qualcomm HS-USB QDLoader 9008 (COM10)
Windows loads this device driver when I plug in the phone.
I don't know if that helps anyone to come up with a solution or not.
I was really enjoying this little phone and hope I haven't killed it.

Updating the ZTE Open C from Mozilla Nightly system images

I wanted to update my ZTE Open C from 1.4 to 2.1. When I update it from the official Mozilla Nightly system images from http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/ everything is good except the font is tiny. I tried to apply the font fix but it doesn't work. Any idea how to fix this ?

Hi RazorMKD,
Thank you for your response. I'm sorry to hear that you also have issues when flashing your ZTE Open C with with older versions of the Flame build.
Can you please explain the steps you are taking to flash your device? Flashing the ZTE Open C device with a Flame image requires a shallow flash, since the Gonk its may not work correctly on the ZTE Open C.
Where did you purchase the device? Can you also attempt to flash your device with ZTE's commercial rooted build to see if this issue persists? Please follow [http://en.comebuy.com/developer-firefox-os-open-c.html this link] for the files and further instructions.
Please let us know the results.
In the meantime, I contacted developers in the dev-b2g mailing list so that others can chime in with possible solutions.
- Ralph

Upgrading ZTE Open C to Firefox OS 2.2?

Hi,
On the official upgrade instructions on the dev wiki, it's fairly simple to upgrade to FXOS 2.1. However, because the build system is now based on Android KitKat, I can't install the latest images on my phone, as it just bricks it and I need to wipe it and start again. Is there any way to upgrade, or am I stuck?
Also, what's the difference between "flame" and "flame-eng"?
Thanks.

Hi megaminxwin,
Currently the ZTE Open C does not have that version available and may brick the device if you flash another build onto the Zte Open C device. However to recover the os it is possible to flash again. Please see the instructions on this page: [https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C]
If you have any other questions we are happy to help.

ZTE OPEN C boot from SD card

I have an ZTE OPEN C hardbricked into QHSUSB_BULK mode (trying to flash flame image)
Does it support boot from SD card or there is any other method for debricking?

My brick is totally bricked - there is no fastboot or adb modes. When I connect it dmesg shows
[Сб. нояб. 8 10:31:55 2014] usb 1-1: new high-speed USB device number 15 using ehci-pci
[Сб. нояб. 8 10:31:55 2014] usb 1-1: New USB device found, idVendor=05c6, idProduct=9008
[Сб. нояб. 8 10:31:55 2014] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Сб. нояб. 8 10:31:55 2014] usb 1-1: Product: QHSUSB__BULK
[Сб. нояб. 8 10:31:55 2014] usb 1-1: Manufacturer: Qualcomm CDMA Technologies MSM
[Сб. нояб. 8 10:31:55 2014] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[Сб. нояб. 8 10:31:55 2014] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB1

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

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

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.

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

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.

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.

Zte open c problem with sync calendar via https

I use ownCloud. On my device ZTE Open C use caldav.
When I use url of our CalDAV server http that synchronization is good
When I use https and click SAve -sync not work. I see "Something is wrong. Try again later".
What is the problem ?

Hello,
Thank you for contacting Mozilla Support! After reviewing the information that you provided, we think that the best way to fix this issue would be to reset your device.
'''Warning:''' '''''Resetting your phone will delete all data stored on the device, including apps, calendar data, email accounts, and settings.'''''
To reset the device, follow these instructions:
# 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.
We hope that this fixed the issue you were having. Please report back to us if this helped!
Thank you!

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

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

Flashing a flame image on a zte open c

Similar Messages

Maybe you are looking for