It's not getting up that far. It has three available states:

1. Hold volume DOWN and power = FTM
2. Hold volume UP and power = recovery mode where SD updates always fail
3. Normal power up - goes to the Firefox wavy tail splash screen and stays there.

In none of these states does 'adb devices' or 'fastboot devices' see the device, but the USB drivers *do* see it. On Windows, the USB drivers also see a disk partition even with no SD card in it, so I'm assuming that's the on-device flash. But you can't examine it in Windows, and I haven't found anything like that in Linux.

By the way, I have filed a bug here: https://bugzilla.mozilla.org/show_bug.cgi?id=956584

I tried that too - still fails on a signature verification.

If you hold the down button only ( not volume down) while reboot the device you should get to fastboot mode.

If you can get there then you can try : fastboot erase cache [provided that you have android sdk installed or fastboot somewhere]

That will erase the cache partition. Then try : fastboot reboot and see if the device starts up.

Otherwise you can get back into that mode, make a build and flash the .img files on it to get it to a working state again.

To note, each mode is different fastboot only works on fastboot mode adb only works if the system is up and running and has remote debugging turned on. FTM is a different mode than adb/fastboot. It's expected not to work there. System Recovery is a different mode than adb/fastboot. It's expected not to work there.

If you hold the down button only ( not volume down) while reboot the device you should get to fastboot mode.

If you can get there then you can try : fastboot erase cache [provided that you have android sdk installed or fastboot somewhere]

That will erase the cache partition. Then try : fastboot reboot and see if the device starts up.

Otherwise you can get back into that mode, make a build and flash the .img files on it to get it to a working state again.

It never gets to 'fastboot mode'. I start fastboot on the Linux host terminal and it prints <waiting for device> and just stops there while the phone reboots. I've checked the udev settings on Linux and they're correct. The USB drivers do see the device:

   # more /etc/udev/rules.d/50-android.rules 
   SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev" # ZTE Open
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev" # Google device 

   # lsusb
   Bus 003 Device 015: ID 19d2:1353 ZTE WCDMA Technologies MSM

Hrm. What do you see on the device?

I usually hold the down button for a good 20 secs after a reboot (remove the usb cable, unplug the battery, plug the battery in, hit the power and hold volume down) and then check the fastboot devices. Sometimes if that doesn't work I hold the volume down while plugging the battery in. It might be that the device is oem locked, now that I think about it.  :/

Try going to system recovery mode and delete the cache. ie Hold volume UP and power, and use the volume buttons to move to the delete cache and use the power button to accept.

If you can't get to the fastboot mode nor adb and system recovery doesn't work... there's not much you can do other than send it to someone that can fix it. You would need proprietary software in order to try to get it fixed.

Where is the 'down' button? I have a power switch on the top and a volume control on the left.

Sorry, I should have specified the hardware Volume down button.

Ah - that puts the phone into a white screen with black text 'FTM'. And it's still inaccessible to adb and fastboot. :-(

It shouldn't. if you are holding the power button and the volume down button that will put you to the FTM. You need only to hold the volume down button.

Just try using the system recovery as per the other method to erase the cache.

I 've been away of my ffosZTEOpen for some time...

For some reason I ignore, my code copy-pasting does not seperate lines always and cannot be edited later, be patient...

@znmeb: When you start ZTEOpen by just pressing the power-button, does the device STAY at the "Firefox wavy tail splash screen" or does a "boot loop"?

My ZTEOpen restarts about every 15". Just after the red LED turns on the "EarthFox" Firefox OS logo appears. At about 6,5" the fox first shows-up with the LED on. At about 11" the LED turns off. Somewhere about 13,5" I could locate my device!

The next are in Root Terminal:

root@vostroA90:/home/ovasilis74# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 8087:07d9 Intel Corp. Bus 001 Device 003: ID 413c:8147 Dell Computer Corp. F3507g Mobile Broadband Module Bus 001 Device 012: ID 19d2:1350 ZTE WCDMA Technologies MSM root@vostroA90:/home/ovasilis74#

The vendor(ZTE) ID is the 19d2 and the product ID is the 1350, IN NORMAL Power-up state (and in this boot-loop state).

So, I powered-up (just power-button) and executed in the Root Terminal after 11" but before 13 (not sure if this is important):

root@vostroA90:/home/ovasilis74# adb wait-for-device reboot-bootloader error: protocol fault (no status) root@vostroA90:/home/ovasilis74#

...if I am a little late at 13"... After some "adb wait-for-device reboot-bootloader" attempts, occures a reboot where the "EarthFox" Firefox OS logo STAYS. I belive I 'm in fastboot mode.

root@vostroA90:/home/ovasilis74# adb wait-for-device reboot-bootloader root@vostroA90:/home/ovasilis74# adb wait-for-device reboot-bootloader root@vostroA90:/home/ovasilis74# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 8087:07d9 Intel Corp. Bus 001 Device 003: ID 413c:8147 Dell Computer Corp. F3507g Mobile Broadband Module Bus 001 Device 017: ID 18d1:d00d Google Inc. root@vostroA90:/home/ovasilis74#

Now my ZTEOpen's ID (18d1:Google, d00d:Generic etc.) is listed as a "Generic and unspecified debug interface" Google device, fastboot sees the device

root@vostroA90:/home/ovasilis74# fastboot devices -l ROAMER2 fastboot usb:1-8 root@vostroA90:/home/ovasilis74#

and fastboot commands are enabled!

root@vostroA90:/home/ovasilis74# fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.001s] finished. total time: 0.002s root@vostroA90:/home/ovasilis74# fastboot devices -l ROAMER2 fastboot usb:1-8 root@vostroA90:/home/ovasilis74#

...But the phone does not coperate well: I have copied in "ovasilis74@vostroA90:~/android_sdk/android-sdk-linux/platform-tools$ " -even if it 's not needed- the 1.0 and 1.1 updates for the ZTEOpen from the "main" ZTE update site: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html?type=software , a copy of recovery-clockwork-6.0.3.3-roamer2.img and a copy of a stock-recovery.img from my SDcard and the files from a CWM backup from 1.0:

ovasilis74@vostroA90:~/zteopen/backup101/clockworkmod/backup/2013-11-10.22.54.23$ ls boot.img data.yaffs2.img recovery.img system.yaffs2.img cache.yaffs2.img nandroid.md5 recovery.log ovasilis74@vostroA90:~/zteopen/backup101/clockworkmod/backup/2013-11-10.22.54.23$

(I don 't remember if it is with stock-recovery or recovery-clockwork-6.0.3.3-roamer2.img after rooting and recovery-flashing the ZTEOpen, I think it is the second, cwm) . None of the commands responds in a way that I could use the results

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot update EU_DEV_FFOS_V1.0.0B02_USER_SD.zip archive does not contain 'android-info.txt' archive does not contain 'android-product.txt' error: update package has no android-info.txt or android-product.txt root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot update EU_DEV_FFOS_V1.1.0B04_UNFUS_SD.zip archive does not contain 'android-info.txt' archive does not contain 'android-product.txt' error: update package has no android-info.txt or android-product.txt root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

Flashing recovery.img and recovery-clockwork-6.0.3.3-roamer2.img leads the ZTEOpen to reboot and I have to bring it back to fastboot mode:

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot flash recovery recovery.img sending 'recovery' (5712 KB)... OKAY [ 0.485s] writing 'recovery'... FAILED (status read failed (No such device)) finished. total time: 5.808s root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# adb wait-for-device reboot-bootloader root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot flash recovery recovery-clockwork-6.0.3.3-roamer2.img sending 'recovery' (5712 KB)... OKAY [ 0.487s] writing 'recovery'... FAILED (status read failed (No such device)) finished. total time: 5.882s root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

"flasall" gives this without rebooting the phone:

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot flashall error: neither -p product specified nor ANDROID_PRODUCT_OUT set root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot -p roamer2 flashall error: could not load android-info.txt: No such file or directory root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

I also did:

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot reboot rebooting...

finished. total time: 0.002s root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# adb wait-for-device shell flash_image recovery /sdcard/recovery.img error opening /sdcard/recovery.img: Permission denied root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

I did other thigs too, cannot remember all, no result. I forgot to tell that in FTM mode (voldown + power-button/"fastboot reboot") the phone looks like:

root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# fastboot reboot #voldown is pressed rebooting...

finished. total time: 0.001s root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools# lsusbBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 8087:07d9 Intel Corp. Bus 001 Device 003: ID 413c:8147 Dell Computer Corp. F3507g Mobile Broadband Module Bus 001 Device 125: ID 19d2:0112 ZTE WCDMA Technologies MSM root@vostroA90:/home/ovasilis74/android_sdk/android-sdk-linux/platform-tools#

So my /etc/udev/rules.d/60-ffos.rules is:

SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="1350", MODE="0666", GROUP="plugdev" SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="0112", MODE="0666", GROUP="plugdev" SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666", GROUP="plugdev"

In FTM "adb devices" and "fastboot devices" bring nothing and shuting-down the phone is possible only by disconecting USB cable and removing battery.

For now, I don 't know what 'android-info.txt' and 'android-product.txt' are, but I don 't think they could help me; or could they? I assume I sould look for TPT solutions and learn how it works, I unknow even what it means, have not found realy helpful TPT info yet .

In any case, I can't see they have any excuse ZTE but espesialy Mozilla to answer in marketing-style to questions about all this unacceptable situation too many of us have been into with this "closed"-open phone. I 'm not complaining about the partialy-incomplete FFOS but for the "closed doors" and caotic and incomplete documentation for those trying to solve bricks-and-other-problems, even if I enjoy finding solutions. Clarity is wisdom...

...I also suspect that there are more 256MB of RAM "locked" in this fox-device...

@znmebDo you realy see a 1353 ID?

1. lsusb

  Bus 003 Device 015: ID 19d2:1353 ZTE WCDMA Technologies MSM

I boughted mine from ZTE_UK and its ID is 1350 in "normal" mode.

"@znmeb: When you start ZTEOpen by just pressing the power-button, does the device STAY at the "Firefox wavy tail splash screen" or does a "boot loop"? "

wavy tail splash screen

"@znmebDo you realy see a 1353 ID?

   lsusb 

 Bus 003 Device 015: ID 19d2:1353 ZTE WCDMA Technologies MSM

I boughted mine from ZTE_UK and its ID is 1350 in "normal" mode. "

Mine is a US eBay unit from mid-September 2013.

"In any case, I can't see they have any excuse ZTE but espesialy Mozilla to answer in marketing-style to questions about all this unacceptable situation too many of us have been into with this "closed"-open phone. I 'm not complaining about the partialy-incomplete FFOS but for the "closed doors" and caotic and incomplete documentation for those trying to solve bricks-and-other-problems, even if I enjoy finding solutions. Clarity is wisdom..."

What's worse IMHO is that Mozilla and ZTE have announced *more* partnership devices at CES 2014. I'll cut everyone a little slack because we're dealing with three languages - English, Chinese and Spanish - and a few carriers, but it does look like the "openness" of the device isn't there.

Notes on formatting in this forum:

It is using some sort of Textile-like coding. Use the buttons for bold, italic, links, ordered and unordered lists. For code or other text that you don't want interpreted, precede each line with four spaces, like this:

   # My pasted root prompt shows up here - if it was at the left of the line it would be formatted as a numbered list item.

Thank you for the information.

Mozilla does have a lot of documentation at

• Moz Dev : ie https://developer.mozilla.org/en-US/Firefox_OS
• Wikis : ie https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks, https://wiki.mozilla.org/B2G
• Github : ie https://github.com/mozilla-b2g/gaia, https://github.com/mozilla-b2g/B2G

What you have run across may be bugs, which unfortunately occurs, esp on projects that are new. If you recall Android had started off in the same foot. To make these things better for the rest of the community, filing bugs and helping Mozilla find solutions are a great way to contribute. This thread is a great way to help bring knowledge to the rest of the community. I appreciate your help in regards to understanding what's causing these issues so that we can try to fix them and/or find work around for the rest of the community.  :)

Also to note, it appears that ZTE has an upgrade version dependant on where you got the device from. If the upgrade version doesn't match, more than likely you will get the error message saying that the verification failed:

See: http://www.ztedevices.com/search.html?keyword=FFOS

"It shouldn't. if you are holding the power button and the volume down button that will put you to the FTM. You need only to hold the volume down button."

It doesn't seem to be doing anything. Should I do it with battery in / no USB connection, battery out / USB connection or battery in / USB connection?

"Just try using the system recovery as per the other method to erase the cache."

I've done that - it says it has erased the cache. The device is still unresponsive after that.

I'm now moving on to bug 935059 - trying to build an installable zip archive and install it from an SD card. There's a github server out of commission so I'm still acquiring source but eventually I should have a zip file.

I am not sure if this is helpful, but did anyone try this yet: https://hacks.mozilla.org/2013/12/upgrading-your-zte-open-to-firefox-o... ?

"I am not sure if this is helpful, but did anyone try this yet: https://hacks.mozilla.org/2013/12/upgrading-your-zte-open-to-firefox-o... ?"

Yeah - that was a step on my path to brickage. ;-) I have moved on to bug 935059 - build a zip archive and install via SD card. So far I'm still acquiring source; there's a Github server that isn't responding.

Git hub had an issue with the dns ... it should be working now: https://status.github.com/

)

@znmeb: Even with "wavy tail splash screen" at the end, you could(?) access fastboot-mode if at some stage of booting "adb wait-for-device reboot-bootloader" sees the device for 1", as in my occasion. After that I am stuck again, but this is me... Probably 1353 is the US version, not another boot-mode I haven 't found. I think mine has problems that only some low-stage flashing could deal.

@nhirata: For sure I 'm not the best person to speak about this or any project. I 'm not a developer at all, I cannot code in any language, also my job is irrelative, mainly I copy-paste and do basic tasks. But I have searched and read alot about the ZTEOpen and have not found many complete presentations of what to do for an X fact to be accived. I would expect to find two simple words about how to TPT an image to ZTEOpen, or ZTE or Mozilla telling me that I can 't. It 's better than a row of links... I mean that filing a bug seems unesesary to me if I want to flash with TPT a whole device. Thanks for the links, useful to have in one place.

@guigs2: The link you post is similar with most of the stuff in the known internet, at the end has this documentation for bricked devices, but all these:

fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot

take me to a reboot and same as I wrote above...

I have not yet tried to return the phone for another that I would shell as new and choose by support-level next time... Finaly, is http://firefox.ztems.com/ normal and valid or not? If yes I did something wrong, if not why is it there?