is there any way to update zte open to v1.1?

Hi Jose,

Thanks for using ZTE Open! Currently there is no update to v1.1
available for ZTE Open. Let us know what you are missing on v1.0, there
might be some other options we can show you and we like to hear your
feedback.

Best regards,
Michelle Luna
Mozilla support

On 7/27/13 8:54 AM, jose llopis wrote:
> is there any way to update zte open to v1.1?

> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g

Hi Michelle,

any plans for Alcatel One Toch Fire for 1.1?

BR

Rafał

Hi Rafal,

As far as 'plans', those are with ZTE and Alcatel for their devices.
Neither has 1.1 available at this time as far as I understand (1.1
version is only in developer preview/pre-release testing now).

-Michelle

Ok thnx for the info. Happy to help in dev/testing if needed.

BR

Rafal

Always possible to build your own (at least thats what I do for my one touch fire) https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build

Hello,

I've try to build b2g for my zte open (inari device) but at the end I don't have boot.img.

Anyway I have flashed (with flash_image) system.img and userdata.img but my phone won't boot anymore and stay fixed on splatch screen.

Le 29/07/2013 08:07, Jan Jongboom a écrit :
> Always possible to build your own (at least thats what I do for my one
> touch fire)
> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build

AFAIK you can't flash the system on production devices (unless the
device is rooted somehow of course).

Hmm, aren't all phones rooted?


2013/8/23 Julien Wajsberg <jwaj...@mozilla.com>

Le 23/08/2013 09:42, Jan Jongboom a écrit :
> Hmm, aren't all phones rooted?

Only geeksphones one are rooted, AFAIK.

On 08/23/2013 03:26 AM, Julien Wajsberg wrote:
> Le 29/07/2013 08:07, Jan Jongboom a écrit :
>> Always possible to build your own (at least thats what I do for my one
>> touch fire)
>> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build
>
> AFAIK you can't flash the system on production devices (unless the
> device is rooted somehow of course).

My experience with a non-rooted image was that I could flash using the
full ./flash.sh script because it uses fastboot.  I wasn't able to do
make install-gaia or ./flash.sh gecko, though, because those use adb to
push to the file system which of course requires root.

Hope that helps.

Ben

I haven't been able to use fastboot with some production device, but
maybe I did something wrong :)

Hello,

You can root the device with this howto :
http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/

Fastboot fails to flash system.img but fash_image in adb shell works.

I was working on my dev buri that was flashed with non-root production software from the vendor.  Maybe this is not equivalent to the issue here.  Sorry for the confusion!

Ben

Doesn't seem to work for me. Here's what I did:

In `adb shell`:

    su
    mount -o rw,remount /
    mkdir _tmp
    chmod 0777 _tmp

Then, in a normal shell:

    adb push out/target/product/inari/system.img _tmp/system.img

Then back in `adb shell`:

    flash_image system _tmp/system.img

And the output was:

    ...
    mtd: successfully wrote block at 5b20000
    mtd: successfully wrote block at 0
    Segmentation fault

Fortunately, I had a backup image on the SD card.

What am I doing wrong?

Flashing system on running system (FirefoxOS) produce Segmentation fault. I use CWM recovery cli commands. After installed CWM, start on recovery mode, enter using adb shell and apply flash_image. This method not generate Segmentation fault, however FxOS do not works!

I have to try several times with fastboot to work, change usb ports, reboot in fastboot mode a couple of times, etc. but eventually it works.

On Saturday, July 27, 2013 8:54:11 AM UTC-7, jose llopis wrote:
> is there any way to update zte open to v1.1?

Here are the steps I took to create a new boot image for the ZTE Open which allows installing dev builds of FxOS:

https://gist.github.com/joshuapurcell/6513333

Someone named edu at the following link was the first one I found to figure out the steps, and I made minor changes for the steps to work in my environment (Ubuntu 13.04 64-bit):

http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions

On Tuesday, 10 September 2013 21:25:05 UTC+3, Joshua Purcell  wrote:
> Here are the steps I took to create a new boot image for the ZTE Open which allows installing dev builds of FxOS:
>
> https://gist.github.com/joshuapurcell/6513333

Thanks for sharing! Doesn't seem to work for me, though. Some details:

I bricked my device in an earlier attempt. Ever since I flashed the system partition (using flash_image), when I reboot, it gets stuck at the splash screen (the fox is static, not animated).

Also, Clockwork Mod refuses to install from the official ZTE zip:

    assert_failed: getprop_new("ro.build.display.id") == "OPEN_EU_DEV_FFOS_"

After following the steps in your gist, the device is still bricked.

I was only able to run `./flash.sh gaia` and `.flash.sh gecko` in recovery mode, since the device was not recognized by adb when booting normally. Maybe that's relevant somehow.

On Saturday, July 27, 2013 8:54:11 AM UTC-7, jose llopis wrote:

> is there any way to update zte open to v1.1?

Are you defier from this thread? http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions

Hopefully you can figure out steps needed to get your phone working. Here are some steps on MDN for unbricking a phone running fxos:

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/Updating_and_Tweaking_Geeksphone#.22Ok.2C_I_bricked_my_phone.22

Hi
I've succesfully updated a ZTE Open to Firefox Os 1.1
Some issues I've found:
After the update if I make a Reset Phone the system apps like contacts or calendar updates are gone and they come to the previous version, so the old apps are still there?


The update number in the info keeps on 1.1 after a system reset, so the phone keeps updated on 1.1 but the apps doesn't

I've got less space in my device to install apps even if I delete all the testing apps

Probably you updated your phone on developer mode then you have old apps installed in /system/b2g/webapps and new b2g apps on /data/local/webapps

In order to keep coherency, you must update to production devices using

VARIANT=user ./flash.sh gaia

or reset all using:

cd B2G
make reset-gaia PRODUCTION=1

Le 16/09/2013 04:08, Eduardo González a écrit :
> Probably you updated your phone on developer mode then you have old apps installed in /system/b2g/webapps and new b2g apps on /data/local/webapps
>
> In order to keep coherency, you must update to production devices using
>
> VARIANT=user ./flash.sh gaia
>
> or reset all using:
>
> cd B2G

I guess you meant "cd gaia".
> make reset-gaia PRODUCTION=1

"make production" is a shortcut :)

>
> On Sunday, September 15, 2013 1:38:00 PM UTC-4:30, Xes Garcia wrote:
>> Hi
>>
>> I've succesfully updated a ZTE Open to Firefox Os 1.1
>>
>> Some issues I've found:
>>
>> After the update if I make a Reset Phone the system apps like contacts or calendar updates are gone and they come to the previous version, so the old apps are still there?
>>
>>
>>
>>
>>
>> The update number in the info keeps on 1.1 after a system reset, so the phone keeps updated on 1.1 but the apps doesn't
>>
>>
>>
>> I've got less space in my device to install apps even if I delete all the testing apps

Yes Julien, i was wrong,

cd gaia
make production

is more elegant!
Thanks Julien

On Sunday, September 15, 2013 7:08:17 PM UTC-7, Eduardo González wrote:
> Probably you updated your phone on developer mode then you have old apps installed in /system/b2g/webapps and new b2g apps on /data/local/webapps
>

From what it looks like on my phone, new apps (after switching to production mode) are actually in /system/b2g/webapps. The other location (/data/local/webapps) contains only two files: marketplace.firefox.com and webapps.json.

>
>
> In order to keep coherency, you must update to production devices using
>
>
>
> VARIANT=user ./flash.sh gaia
>
>
>
> or reset all using:
>
>
>
> cd B2G
>
> make reset-gaia PRODUCTION=1
>
>
>
> On Sunday, September 15, 2013 1:38:00 PM UTC-4:30, Xes Garcia wrote:
>
> > Hi
>
> >
>
> > I've succesfully updated a ZTE Open to Firefox Os 1.1
>
> >
>
> > Some issues I've found:
>
> >
>
> > After the update if I make a Reset Phone the system apps like contacts or calendar updates are gone and they come to the previous version, so the old apps are still there?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > The update number in the info keeps on 1.1 after a system reset, so the phone keeps updated on 1.1 but the apps doesn't
>
> >
>
> >
>
> >
>
> > I've got less space in my device to install apps even if I delete all the testing apps

On Saturday, July 27, 2013 10:09:24 PM UTC+5:30, Michelle Luna wrote:
> Hi Jose,
>
>
>
> Thanks for using ZTE Open! Currently there is no update to v1.1
>
> available for ZTE Open. Let us know what you are missing on v1.0, there
>
> might be some other options we can show you and we like to hear your
>
> feedback.
>
>
>
> Best regards,
>
> Michelle Luna
>
> Mozilla support
>
>
>
>
>
> On 7/27/13 8:54 AM, jose llopis wrote:
>
> > is there any way to update zte open to v1.1?
>
> > _______________________________________________
>
> > dev-b2g mailing list
>
> > dev...@lists.mozilla.org
>
> > https://lists.mozilla.org/listinfo/dev-b2g

Hi Michel,
Any update on v1.1 availability for ZTE Open as of 11 Oct 2013?
Regards
Sudhakar

Hi there,

I published some instructions on the ZTE, including making it flashable, and updating it:

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN

I'm assuming from the date of your last mail that you got one of the older ones? follow the instructions from

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN#Device_revisions

onwards, and you should be able to update it.

Let me know how you get on.

Chris Mills
   Senior tech writer || Mozilla
developer.mozilla.org || MDN
   cmi...@mozilla.com || @chrisdavidmills

Hi Chris,
your MDN ZTE page is great info source, thx for it, however I miss there information for those having bought phone from cariers like Movistar, if they could follow given instructions as well or not, because having non rooted phone and waiting for update is a little bit frustrating...
Thx,
Marek

You are absolutely right. I will take it as a work item going forward to try to cover all phones and carriers going forward.

Chris Mills
   Senior tech writer || Mozilla
developer.mozilla.org || MDN
   cmi...@mozilla.com || @chrisdavidmills

So, are you saying that an update to FxOS v1.1 is not distributed OTA by
Mozilla/ZTE?

All ZTE devices are manufactured by ZTE and ZTE distributes the original FxOS software for it, as well as any updates. We are working with all our vendors to make sure that they update the devices, but in the end only ZTE can make reliable statements when and whether and which updates will be available. Any information on our Wiki is merely us trying to facilitate the flow of information.

Andreas

No - I'm merely saying that I'm going to try to provide information on as many of the different Firefox OS devices as I can on MDN, as there are so many unanswered questions on there.

Best,

Chris

Thanks for clarifying.

Chris, I'm on a Canadian carrier. Are interested in some information on
that for your wiki?

Stephan

So, is there no information on when the 1.1 update will be available OTA for the ZTE Open? Will it *ever* be available?

Sam

Again, only ZTE can make statements about that. The ZTE Open is a ZTE device. Only ZTE can make software for it, based on the source code they get from us. We cannot make updates and we cannot promise that ZTE will. ZTE and Mozilla are completely separate entities. We don't/can't speak for ZTE.

That having said, as I said before, we are working closely with all vendors to help them make updates available for 1.2 and future versions. For any more details than that, please wait for ZTE to communicate details about updates.

Thanks,

Andreas

On 11/10/13 11:44 AM, Stephan Bardubitzki wrote:
> Chris, I'm on a Canadian carrier. Are interested in some information on
> that for your wiki?

I don't understand the question exactly, but the US version of the ZTE
Open supports UMTS 850/1900 which mean it will work on the two big
networks in Canada: Bell/Telus and Rogers. And the regional one like
Sasktel or MTS that use the same bands. It will not work on WIND,
Mobilicity, Videotron or Eastlink that all operate in the AWS frequency.

The handset is independent of the carrier.

Hub

> The handset is independent of the carrier.

This is not the point, maybe have a lock at the link below and the
information provided for US carriers

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN

And non of my colleques was aware that you can't buy a ZTE Open in
Canada... oh ebay.com... how much is the shipping cost? ... MicroSD
card... what plan did you choose?

Hmm... all the cost involved does it still make sense to give it a shot...

On Oct 11, 2013, at 2:19 PM, Stephan Bardubitzki <ste...@mobitec.ca> wrote:

>> The handset is independent of the carrier.
> This is not the point, maybe have a lock at the link below and the information provided for US carriers
>
> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN
>
> And non of my colleques was aware that you can't buy a ZTE Open in Canada... oh ebay.com... how much is the shipping cost? ... MicroSD card... what plan did you choose?
>

> Hmm... all the cost involved does it still make sense to give it a shot…

I purchased one in Canada. The shipping was $11 or so and it arrived within a week.

 S.

I'm in Canada and bought mine from ebay in the states. $15 shipping. Arrived in a week.

Sam

Hi,

I have no luck flashing my ZTE Open:

# ./flash.sh
< waiting for device >
erasing 'cache'...
OKAY [  0.528s]
finished. total time: 0.528s
erasing 'userdata'...
OKAY [  1.397s]
finished. total time: 1.397s
sending 'userdata' (66670 KB)...
OKAY [  5.608s]
writing 'userdata'...
FAILED (status read failed (No such device))
finished. total time: 10.991s

# adb devices
List of devices attached
roamer2 device

Can anyone help?

Thanks for reading. Sven

On Wed, 2013-10-16 at 11:37 -0700, Sven Ehret wrote:
> Hi,
>
> I have no luck flashing my ZTE Open:
>
> # ./flash.sh
> < waiting for device >
> erasing 'cache'...
> OKAY [  0.528s]
> finished. total time: 0.528s
> erasing 'userdata'...
> OKAY [  1.397s]
> finished. total time: 1.397s
> sending 'userdata' (66670 KB)...
> OKAY [  5.608s]
> writing 'userdata'...
> FAILED (status read failed (No such device))
> finished. total time: 10.991s
>
> # adb devices
> List of devices attached
> roamer2 device
>
> Can anyone help?

I ran into a similar problem. I realized that the fastboot device is
different from the adb device. If you check your dmesg you'll see two
different vendor strings. Make sure you have both vendors in your
android udev rules:

SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev" # ZTE Open
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev" # Google device

And then restart udev (or reload it's configs).

Note: I still don't have a bootable image on the ZTE Open yet. In fact,
I can't get it back to boot via ZTE's latest firmware update either.
It's like the system.img was missing from their update. This post[1]
seems to indicate we'll have to build a new boot.img to be compatible
with a custom B2G, though I'd much rather build it myself than grab some
random binary off the web ;)

-Aaron

[1] http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html

Hi! I'm author of adapted boot image, and is correct is not recommended use files from third party as file hosted by me, but the issue about create own boot.img is not so easy.
Before talk about boot.img, is necessary remember that flashing the zte open using ./flash.sh require fastboot full supported. If you get problems using flash.sh (as exact messages posted by Sven) then you have a device without fastboot full supported.
In order to enable fastboot you must update using DEV images from ztedevices.com, for example the images of UK American Standard or European Standard. Check https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN

Next step is use boot image adapted by me as explained on
http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html
By default, b2g tree do not create boot.img. You must define on device tree (<b2g_dir>/device) the elements required so kernels is compiled and generate boot.img. Additionally stock boot.img contain a kernel using particular modules (zte blobs) not included into b2g kernel source

Hi,

Thanks to Eduardo for is good job. I made a simple check on his boot.img
file.
Only 2 files have changed ( init.rc and init.b2g.rc). I don't see backdoor
on his code.

Check this post to see my procedure (in french).
https://vincent.degat.ch/boot-img-de-firefox-os-1-2-pour-zte-open

> kernel source _______________________________________________ dev-b2g
> mailing list dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g

If the owners of ZTE Opens had a nice easy way to get the latest stable
and testing images for their devices (like the geeksphone users have at
http://downloads.geeksphone.com/) none of this would be an issue.

On Thu, 2013-10-17 at 08:37 -0700, jezra wrote:
> If the owners of ZTE Opens had a nice easy way to get the latest stable
> and testing images for their devices (like the geeksphone users have at
> http://downloads.geeksphone.com/) none of this would be an issue.

Agreed. It's a bummer that a device marketed as a "development" device
cannot be used for development out of box.

-Aaron

> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g

It seems as though they have taken a page from Tizen's book and
consider a "developer" to only mean someone that will be developing an
html5 app for the app store.

When I first used my ZTE Open, I found a bug and reported the bug. For
all I know, the bug I reported was fixed a few months ago in v1.1, but
since there is no easy way for beta testers to keep their ZTE devices up
to date, I may have just been wasting valuable developer time.

Hi just wanted to thank you all for this info.
I managed to update my zte to version 1.1

I wrote a blog post that I hope will organize the steps I learned here.

https://blog.non.co.il/index.php/zte-open-phone-upgrading-to-firefoxos-1-1-how-to/

Le 18/10/2013 19:30, jezra a écrit :
> When I first used my ZTE Open, I found a bug and reported the bug. For
> all I know, the bug I reported was fixed a few months ago in v1.1, but
> since there is no easy way for beta testers to keep their ZTE devices up
> to date, I may have just been wasting valuable developer time.
>

Don't worry, filing dupe bugs is never wasting time. It usually means
the initial bug was not easy to find, and your new duplicated bug will
make it easier to find for other users and contributors.

So don't feel bad about this, and thanks a lot. Please continue filing
other bugs if you find some without an existing bug  :-)

Although it's right we probably fixed most of 1.0 issues already, and
bugs for 1.2 would be more valuable, so I really thank all people
helping others to upgrade their phone. It really should be easier.

Thanks for your support,
--
Julien

It isn't just developer time that is getting wasted, the people
answering questions on the "support" site are also dealing with people
having problems with 1.0 on ZTE Open.

+1

I have a ZTE Open (U.S.) and it is frustrating to see only have version 1.0.1. But even more frustrating is when I press the Update button and nothing happens.

Please, it would be too much to ask that the developers put the images for the ZTE Open as well as have the Geekphones?

On Monday, November 11, 2013 7:49:29 PM UTC+1, Ernesto Acosta wrote:
> Please, it would be too much to ask that the developers put the images for the ZTE Open as well as have the Geekphones?

Yes, PLEASE! :)

I've been round the brick / reload to stock / re-root loop a few times now. Somewhere along the line, it has stopped being recognised as a roamer2 device in my VirtualBox ubuntu machine.

Using a virtual machine on my mac has been working fine, but now it just sees 'Handset [0231]' instead of roamer2, and no google device is seen for fastboot.

Not really worried about that, but is there a way of flashing the built img's from a windows or mac, without using flash.sh?

How about using clockworkmod rooted shell? Or will having CWM on the phone stop the B2G img's from working?

I think I'm close now, compiled with no errors using the image of the stock phone.

Any ideas gratefully received.

Well, it worked - I now have v1.2
CWM on, transfered the img files to the sdcard and used the root shell in cwm to flash them on.

The only difference is that I didn't allow CWM to re-add the root binary before rebooting.

So, thanks for the boot.img Eduardo!

One bug - can't swipe down to see notifications.

Check https://bugzilla.mozilla.org/show_bug.cgi?id=937101 for notifications issue

Hi,

If you don't known yet, v1.1 is available on ZTE site for UK model :

http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html?type=software

Eric