Re: [b2g] ZTE Open-- bricked when updating OS
On Sunday, October 13, 2013 11:55:32 PM UTC+3, Hubert Figuière wrote: On 13/10/13 09:36 AM, daniel.i...@googlemail.com wrote: I also have a bricked ZTE Open, yes one of the early ones without the later fastboot update. Mine is neither accessible via fastboot nor adb anymore, only through the diagnostics interface. I can't get into clockworkmod recovery (it hangs), so it requires some sort of low level flash. Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Please - if somebody knows how to do a low level flash of this phone (i have backups of all partitions), please provide some instructions. You can download the update.zip image from ZTE directly. You put it on the SD card and boot the phone. It will update. To download For the US phone http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html For the European phone: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html I don't have a device myself but I have been told this works from people that has similar issues. Hope this helps. Hub i am from fiji will this lock my network ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
hiii i am from fiji can i know where can i get stock rom for zte kis lite ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Monday, February 24, 2014 1:06:48 PM UTC-5, o...@old.com.ua wrote: So, if you can get the phone into a mode where fastboot will see the phone when booted on a good kernel, you are no longer 'bricked'. Not really. My bricked ZTE Open just reboots on any fastboot flash attempt despite the fact that fastboot 'sees' it. And, considering dead recovery and system partitions (and thus non-functional adb), I have my device totally bricked (since 4 months or so) with no real hope to recover. Simply because there is no any low-level flashing available from ZTE or Mozilla and there's noone to provide it. Here is a link to a signed zip file that worked for me. I've been battling this for a few days. Finally found something that works without a failed signature error. Please, everyone try this. It will save you some headaches. https://drive.google.com/uc?id=0BxLNwNKfKhUyeExFd2hid3lDTEUexport=download Just copy to your sd card, go into recovery mode, install from external storage, when it is done make sure to erase all data/factory reset and then reboot into stock factory v1.0 again. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I'm trying to fix my bricked ZTE Open and not having any luck. It powers on with the Firefox OS logo screen then hangs there. I cannot get into recovery mode. What do I do now? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Fri, Jan 17, 2014 at 9:45 AM, BenNG benjamin.kim.ngu...@gmail.comwrote: Hi there ! Good idea bit it doesn't work $ adb shell stop-b2g /system/bin/sh: stop-b2g: not found The command you are looking for is adb shell stop b2g (no hyphen). - Ryan ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Saturday, January 11, 2014 3:02:22 PM UTC+1, lgg2...@gmail.com wrote: Hello, Finally I have a working phone. All thanks to [paziusss] (http://forum.xda-developers.com/showpost.php?p=49329491postcount=40) or [pazos] (in spanish http://gnulinuxvagos.es/topic/2187-he-brickeado-mi-zte-open-%C2%BFy-ahora-qu%C3%A9/#entry14579). A short version is for all of us that had android 3e recovery: 1.- download the indicated file (see the links) and copy to the SD 2.- update the downloaded file with android 3e and goes OK 3.- reboot and IT WORKS. 4.- Try several times until get the root with the initial rooting method (aka. for version 1.0) 5.- Place the CWM recovery (see instrucctions) Then ALL is working OK. Greetings to [paziusss]/[pazos] for this work. Yeahhh for me too :) Thank you !! ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you for the answer :) I finally made it ! ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
J. Ryan Stinnett jryans@... writes: On Fri, Jan 17, 2014 at 9:45 AM, BenNG benjamin.kim.nguyen@...wrote: Hi there ! Good idea bit it doesn't work $ adb shell stop-b2g /system/bin/sh: stop-b2g: not found The command you are looking for is adb shell stop b2g (no hyphen). - Ryan Thx Ryan. I Finally find something that works for the rebooting-loop problem http://forum.xda-developers.com/showpost.php?p=49329491postcount=40 ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi, this is a great news, and thanks for sharing on the list! Regards, -- Julien Le 11/01/2014 15:02, lgg2l...@gmail.com a écrit : Hello, Finally I have a working phone. All thanks to [paziusss] (http://forum.xda-developers.com/showpost.php?p=49329491postcount=40) or [pazos] (in spanish http://gnulinuxvagos.es/topic/2187-he-brickeado-mi-zte-open-%C2%BFy-ahora-qu%C3%A9/#entry14579). A short version is for all of us that had android 3e recovery: 1.- download the indicated file (see the links) and copy to the SD 2.- update the downloaded file with android 3e and goes OK 3.- reboot and IT WORKS. 4.- Try several times until get the root with the initial rooting method (aka. for version 1.0) 5.- Place the CWM recovery (see instrucctions) Then ALL is working OK. Greetings to [paziusss]/[pazos] for this work. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Finally I have a working phone. All thanks to [paziusss] (http://forum.xda-developers.com/showpost.php?p=49329491postcount=40) or [pazos] (in spanish http://gnulinuxvagos.es/topic/2187-he-brickeado-mi-zte-open-%C2%BFy-ahora-qu%C3%A9/#entry14579). A short version is for all of us that had android 3e recovery: 1.- download the indicated file (see the links) and copy to the SD 2.- update the downloaded file with android 3e and goes OK 3.- reboot and IT WORKS. 4.- Try several times until get the root with the initial rooting method (aka. for version 1.0) 5.- Place the CWM recovery (see instrucctions) Then ALL is working OK. Greetings to [paziusss]/[pazos] for this work. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Saturday, January 4, 2014 12:29:54 AM UTC-8, richar...@gmail.com wrote: On Friday, January 3, 2014 7:57:43 PM UTC+1, Julien Wajsberg wrote: We're not focussing on 'top' terminals at all. As I said, ZTE Open is one of our tier 1 terminals, that is the terminals we're specifically testing our code on. I think the confusion is that there are apparently 2 versions of the ZTE Open - the one you can buy on Ebay and the one that Telefonica/Movistar sells in Spain. They are both called ZTE Open, but have different binary blobs on them so are not compatible. The ZTE Ebay Open is the tier 1 model you test on. This seems to be updatable from personal builds and is fully supported by Mozilla. The ZTE Movistar Open is in a state of limbo. Personal builds at least break wifi due to the MAC bug/problem described in one of the linked bugzillas above. That was the blocker for nightlies at least. The device might not even be flashable, presumably for security or some other restriction made by Telefonica (speculation). It's confusing. Also disappointing, as the ZTE Movistar Open is cheaper than the Ebay one (50€ locally, no need for shipping, with some amount of prepaid stuff included), but being so locked down means it is no good. As a user, it is a bad choice as it probably won't be updated past 1.1. I know, you try your best, but it is in the hands of ZTE, and handset manufacturers tend to have a policy of 1 update and that's your lot - that update was to 1.1. As a developer it is risky since the chance of flashing not working is high, or if it works then it might have bugs that will be WONTFIXED as it is not really an officially supported tier 1 device. Is this the state of things or have I got something horribly wrong? Regards, Richard I have the eBay US ZTE Open and mine is also currently bricked. No matter which ZTE update ZIP archive I try to apply on the SD card, I get a signature verification failure. What's worse is that it seems to have lost the ability to respond to adb or fastboot. So the procedure at https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN#I_bricked_my_phone does not work - it just sits there waiting for device. There are probably half a dozen threads on the forum about various ZTE Open brickage; I can go dig them up if you want. As it stands, the US eBay ZTE Open is not a user serviceable device - you can't easily apply ZTE updates or install a custom-built B2G on it without risking getting it into an unusable state. The ones that are being shipped by the carriers in Europe and Latin America may be working fine to surf the web and make phone calls but as a 'developer phone' it's pretty much useless. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi, Richard, The ZTE Open devices from eBay are used to be distributed to countries that ZTE Open devices are not available. Then, more users can get the devices and experience Firefox OS. ZTE Open was released earlier than ZTE Open from eBay. Therefore, ZTE Open from eBay has more Firefox OS fixes than what ZTE Open has. Mozilla doesn't manufacture devices and therefore, we don't have the technical ability to support devices that we don't manufacture, and also we have no legal right to distribute the vendor-specific codes that come on these devices. The respective OEMs support these devices. Mozilla keeps improving Firefox OS and partners can choose what Firefox OS builds they would like to integrate with vendor-specific codes and deliver them to end users. Thanks. Kevin Hu On Jan 4, 2014, at 4:29 PM, richard.qu...@gmail.com wrote: On Friday, January 3, 2014 7:57:43 PM UTC+1, Julien Wajsberg wrote: We're not focussing on 'top' terminals at all. As I said, ZTE Open is one of our tier 1 terminals, that is the terminals we're specifically testing our code on. I think the confusion is that there are apparently 2 versions of the ZTE Open - the one you can buy on Ebay and the one that Telefonica/Movistar sells in Spain. They are both called ZTE Open, but have different binary blobs on them so are not compatible. The ZTE Ebay Open is the tier 1 model you test on. This seems to be updatable from personal builds and is fully supported by Mozilla. The ZTE Movistar Open is in a state of limbo. Personal builds at least break wifi due to the MAC bug/problem described in one of the linked bugzillas above. That was the blocker for nightlies at least. The device might not even be flashable, presumably for security or some other restriction made by Telefonica (speculation). It's confusing. Also disappointing, as the ZTE Movistar Open is cheaper than the Ebay one (50€ locally, no need for shipping, with some amount of prepaid stuff included), but being so locked down means it is no good. As a user, it is a bad choice as it probably won't be updated past 1.1. I know, you try your best, but it is in the hands of ZTE, and handset manufacturers tend to have a policy of 1 update and that's your lot - that update was to 1.1. As a developer it is risky since the chance of flashing not working is high, or if it works then it might have bugs that will be WONTFIXED as it is not really an officially supported tier 1 device. Is this the state of things or have I got something horribly wrong? Regards, Richard ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Sorry, but many of us chose this terminal from the list as tier 1. Mozilla does not produce terminals, but is in contact with manufacturers. ZTE will have some kind of agreement production. According indicated in some emails, ZTE Mozilla makes available some engineers to adapt and polish versions defects in their terminals. Because in this case, ZTE does not help? (see: https://bugzilla.mozilla.org/show_bug.cgi?id=840845#c3 and https://bugzilla.mozilla.org/show_bug.cgi?id=840845#c9) I repeat: there are many ZTE Open bricked terminals and NOBODY gives a solution. This should resolve the Mozilla Foundation. Why? For your interest. For his reputation. For its future. The number of users with ZTE Open Movistar is important (users, application developers, potential contributors of code to the system, ...). ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On 06/01/2014 11:48, lgg2l...@gmail.com wrote: I repeat: there are many ZTE Open bricked terminals and NOBODY gives a solution. This should resolve the Mozilla Foundation. Why? For your interest. For his reputation. For its future. We're very much aware of that and I can assure we're doing our best unfortunately it's quite complicated. Having used a number of developer phones myself I can tell you that even Mozilla developers end up having trouble flashing their devices or with bricked devices. Ease of development on the phones is a general problem and we're trying to address it for everybody. Gabriele signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I don't think it is that complicated: since I'm using the modified boot.img by Eduardo and CWM I've had no problem building, flashing, backing up any b2g version. It's the fine print.. I found this article about a related OS and got a better understanding about the smartphone business which might help understand why things are the way they are with zte open and b2g: http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/ I was hoping for the better, time will tell. On Monday, January 6, 2014 1:07:34 PM UTC+2, Gabriele Svelto wrote: On 06/01/2014 11:48, lgg2l...@gmail.com wrote: I repeat: there are many ZTE Open bricked terminals and NOBODY gives a solution. This should resolve the Mozilla Foundation. Why? For your interest. For his reputation. For its future. We're very much aware of that and I can assure we're doing our best unfortunately it's quite complicated. Having used a number of developer phones myself I can tell you that even Mozilla developers end up having trouble flashing their devices or with bricked devices. Ease of development on the phones is a general problem and we're trying to address it for everybody. Gabriele ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi, Comments inline. Thanks. Kevin Hu On Jan 4, 2014, at 12:45 AM, an wrote: On Friday, January 3, 2014 1:06:56 PM UTC+2, lgg2...@gmail.com wrote: Hello, Today I have found that my terminal It is not inari as I thought. It is a ZTE Open from Movistar but This seems to be a bit different from inari. It is called internally as ikura. (see: https://groups.google.com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/mj25FivM3d8J ). I rolled my eyes when I saw that post too, apparently if it's something simple it is unacceptable nowadays. How about calling the device zte_open now that there's no more secret about it? For released devices, we have a list that maps the codename to partner names: https://developer.mozilla.org/en-US/Firefox_OS/Phones Also there are problems with ZTE about this terminal (see: https://bugzilla.mozilla.org/show_bug.cgi?id=840845 ). Therefore Mozilla has decided to desupport (??) this device in ALL versions (see ikura in: https://wiki.mozilla.org/User:Asasaki:B2GBuilds#Work_not_started_or_prioritized) Could this mean that Mozilla is passing the support of this device from now on to zte only? Mozilla doesn't manufacture devices and therefore, we don't have the technical ability to support devices that we don't manufacture, and also we have no legal right to distribute the vendor-specific codes that come on these devices. The respective OEMs support these devices. But, of course, this is one of the devices we test our codes on, and we keep fixing bugs and improving Firefox OS when testing on this devices and other devices. Partners can choose which Firefox OS builds they would like to integrate with vendor-specific codes and deliver them to end users. Then I think that Mozilla Foundation It is making it very bad about this terminal. It is been sold through Movistar to Spain and Latin America, that is a lot of users. And a lot of them are people that want to work with it. But this terminal It is REALLY locked by ZTE and Mozilla Foundation do nothing to change this. Any answer of this? P.D. (in spanish): Estamos jodidos con este terminal... Movistar se lava las manos, ZTE pasa del tema puesto que esta vendiendo un desarrollo que de haber sido solo para Mozilla Foundation hubiese sido tirar el dinero, con pequeñas modificaciones que eviten la huida de terminales. Mozilla Foundation lo utlizo para el arranque y ahora se da mas soporte y esfuerzos a la migracion a terminales caros desde Android que a los originales ZTE Open. Mozilla Foundation se puede topar con la misma piedra que Samsung con LiMo: no dar rienda suelta al terminal original provoco su desaparicion. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Today I have found that my terminal It is not inari as I thought. It is a ZTE Open from Movistar but This seems to be a bit different from inari. It is called internally as ikura. (see: https://groups.google.com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/mj25FivM3d8J ). Also there are problems with ZTE about this terminal (see: https://bugzilla.mozilla.org/show_bug.cgi?id=840845 ). Therefore Mozilla has decided to desupport (??) this device in ALL versions (see ikura in: https://wiki.mozilla.org/User:Asasaki:B2GBuilds#Work_not_started_or_prioritized) Then I think that Mozilla Foundation It is making it very bad about this terminal. It is been sold through Movistar to Spain and Latin America, that is a lot of users. And a lot of them are people that want to work with it. But this terminal It is REALLY locked by ZTE and Mozilla Foundation do nothing to change this. Any answer of this? P.D. (in spanish): Estamos jodidos con este terminal... Movistar se lava las manos, ZTE pasa del tema puesto que esta vendiendo un desarrollo que de haber sido solo para Mozilla Foundation hubiese sido tirar el dinero, con pequeñas modificaciones que eviten la huida de terminales. Mozilla Foundation lo utlizo para el arranque y ahora se da mas soporte y esfuerzos a la migracion a terminales caros desde Android que a los originales ZTE Open. Mozilla Foundation se puede topar con la misma piedra que Samsung con LiMo: no dar rienda suelta al terminal original provoco su desaparicion. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Friday, January 3, 2014 1:06:56 PM UTC+2, lgg2...@gmail.com wrote: Hello, Today I have found that my terminal It is not inari as I thought. It is a ZTE Open from Movistar but This seems to be a bit different from inari. It is called internally as ikura. (see: https://groups.google.com/d/msg/mozilla.dev.b2g/dENpc-7Fbi4/mj25FivM3d8J ). I rolled my eyes when I saw that post too, apparently if it's something simple it is unacceptable nowadays. How about calling the device zte_open now that there's no more secret about it? Also there are problems with ZTE about this terminal (see: https://bugzilla.mozilla.org/show_bug.cgi?id=840845 ). Therefore Mozilla has decided to desupport (??) this device in ALL versions (see ikura in: https://wiki.mozilla.org/User:Asasaki:B2GBuilds#Work_not_started_or_prioritized) Could this mean that Mozilla is passing the support of this device from now on to zte only? Then I think that Mozilla Foundation It is making it very bad about this terminal. It is been sold through Movistar to Spain and Latin America, that is a lot of users. And a lot of them are people that want to work with it. But this terminal It is REALLY locked by ZTE and Mozilla Foundation do nothing to change this. Any answer of this? P.D. (in spanish): Estamos jodidos con este terminal... Movistar se lava las manos, ZTE pasa del tema puesto que esta vendiendo un desarrollo que de haber sido solo para Mozilla Foundation hubiese sido tirar el dinero, con pequeñas modificaciones que eviten la huida de terminales. Mozilla Foundation lo utlizo para el arranque y ahora se da mas soporte y esfuerzos a la migracion a terminales caros desde Android que a los originales ZTE Open. Mozilla Foundation se puede topar con la misma piedra que Samsung con LiMo: no dar rienda suelta al terminal original provoco su desaparicion. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Le 03/01/2014 17:45, an a écrit : Also there are problems with ZTE about this terminal (see: https://bugzilla.mozilla.org/show_bug.cgi?id=840845 ). Therefore Mozilla has decided to desupport (??) this device in ALL versions (see ikura in: https://wiki.mozilla.org/User:Asasaki:B2GBuilds#Work_not_started_or_prioritized) Could this mean that Mozilla is passing the support of this device from now on to zte only? We just don't produce distributable builds for this device. We're still supporting it. I mean, this is one of the devices we test our code on, and we're fixing the bugs we find when testing with this device. We only rely on ZTE to test and build and distribute the build to final users. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, But there are several SERIOUS problems with ZTE Open (ikura) terminal and It doesn't seem that Mozilla Foundation It is doing anything to solve them. They are focusing in top terminals and loosing that the base terminal it is this, ZTE Open. The version 1.0 was updateable from ZTE to Mozilla. But the 1.1 update of ZTE/Movistar blocks this change of way (update). Enable fastboot but deny any change of the flash (reboot when trying) or broke it up If the update involves bootloader (reboot on the init [fox screen]). Why near all Android terminals haven't any problem to be flashed with fastboot and ZTE Open has them? Movistar (official forum moderator) doesn't giveme any local option to recover my terminal (althogh They say that was possible, but the indicated shop doesn't know anything about it and Movistar doesn't know why). ZTE the same and Mozilla desupport it from October'13. Why I must persevere with this terminal and with FirefoxOS? This OS needs a lot of base programming (i.e.: Contacts need a lot of functionalities to be usefull) and Mozilla Foundation It is giving all efforts to migrate to Samsung/Google top Android terminals instead poolish the base. [Julien], the terminal supported is INARI not IKURA and the BIGGEST number of the ZTE Open'like terminals are IKURA and this has been dessuported becasue ZTE it is not giving support to Mozilla about IKURA (read the post, begin in February without support and closed in October in the same state). [Julien], Why I want collaborate with the project If I cannot use the builds in my terminal? I have a bricked (nearly) terminal and no solution. That It is the problem. And more people has the same. And the solution must no be send it to the shop or to the dealer. This terminal was to be easy to recovery in order to solve any trouble during a flash. And It is not. Solutions? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Le 03/01/2014 19:25, lgg2l...@gmail.com a écrit : Hello, But there are several SERIOUS problems with ZTE Open (ikura) terminal and It doesn't seem that Mozilla Foundation It is doing anything to solve them. They are focusing in top terminals and loosing that the base terminal it is this, ZTE Open. We're not focussing on 'top' terminals at all. As I said, ZTE Open is one of our tier 1 terminals, that is the terminals we're specifically testing our code on. The version 1.0 was updateable from ZTE to Mozilla. But the 1.1 update of ZTE/Movistar blocks this change of way (update). Enable fastboot but deny any change of the flash (reboot when trying) or broke it up If the update involves bootloader (reboot on the init [fox screen]). Why near all Android terminals haven't any problem to be flashed with fastboot and ZTE Open has them? Most android terminals I know can't be flashed easily and needs to be rooted. When they're rooted they're still difficult to flash. The well-known exceptions are of course the Nexus devices, which we mostly support as Tier 2 or Tier 3 terminals. Movistar (official forum moderator) doesn't giveme any local option to recover my terminal (althogh They say that was possible, but the indicated shop doesn't know anything about it and Movistar doesn't know why). ZTE the same and Mozilla desupport it from October'13. I can't say anything on this, sorry, maybe someone else on this list will be able to help more. Why I must persevere with this terminal and with FirefoxOS? This OS needs a lot of base programming (i.e.: Contacts need a lot of functionalities to be usefull) and Mozilla Foundation It is giving all efforts to migrate to Samsung/Google top Android terminals instead poolish the base. Again, this is really untrue. [Julien], the terminal supported is INARI not IKURA and the BIGGEST number of the ZTE Open'like terminals are IKURA and this has been dessuported becasue ZTE it is not giving support to Mozilla about IKURA (read the post, begin in February without support and closed in October in the same state). This is untrue. Since the start, ZTE are the only ones to distribute builds to final user. This never changed, and this never was intended to change. [Julien], Why I want collaborate with the project If I cannot use the builds in my terminal? I have a bricked (nearly) terminal and no solution. That It is the problem. And more people has the same. And the solution must no be send it to the shop or to the dealer. This terminal was to be easy to recovery in order to solve any trouble during a flash. And It is not. I can only agree with what you're saying here, but that's unfortunately the current state. I'm sure this will get better in 2014 though :) -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hard to understand why zte can't get one thing right with this phone, anyway I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2478426 to root the device and install CWM which restored the functionality of my phone. Afterwards I flashed my own builds without problem. Don't forget to use Eduardo's boot.img (https://mega.co.nz/#!uJ52xZJa!M_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxnvdm4). On Sunday, December 22, 2013 11:56:48 PM UTC+2, lgg2...@gmail.com wrote: Hello, Another with the brick problem after update. No fastboot, ADB during less than 1 second, and reboot, without CWM, with signature error of any firmware that I want install. There are alot of post about people that brick and unbrick this phone and make guides about it, but none of them works. Mozilla Foundation MUST ask to ZTE publish a firmware for Open that works with ZTE handset update software and then It will posible to unbrick ALL Open phones through FTM mode. Mozilla Foundation, do You want to get users and developers? Solve this BIG TROUBLE. Speak with ZTE, make a VALID guide (without use adb/fastboot but FTM or download mode). This ZTE Open was like a first ship, but It is shinking. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, The problem becomes when the terminal fall into the reboot bucle. There is only 1 second (aprox.) of ADB service until reboot. In that lapse I can transfer a maximun of 2,5MB (tested) and not always. Also I have try to send the CWM splited and rejoined inside the /data/local/tmp/ but imposible flash It. I can list directories, dmesg, change attributes, users, etc. but all in less than 1 second. Also fastboot doesn't work. Huge problem. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Oh, in that second, issue 'adb shell stop-b2g' to prevent Gecko from starting. Then you will have adb forever. If you are able to run Firefox OS, go to Settings Device Information More Information Developer and enable Remote debugging. This switches on the ADB. On 23/12/13 13:01, lgg2l...@gmail.com wrote: Hello, The problem becomes when the terminal fall into the reboot bucle. There is only 1 second (aprox.) of ADB service until reboot. In that lapse I can transfer a maximun of 2,5MB (tested) and not always. Also I have try to send the CWM splited and rejoined inside the /data/local/tmp/ but imposible flash It. I can list directories, dmesg, change attributes, users, etc. but all in less than 1 second. Also fastboot doesn't work. Huge problem. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, PS output: USER PID PPID VSIZE RSS WCHANPC NAME root 1 0 480340 S /init root 2 0 0 0 S kthreadd root 3 2 0 0 S ksoftirqd/0 root 4 2 0 0 S kworker/0:0 root 5 2 0 0 D kworker/u:0 root 6 2 0 0 S khelper root 7 2 0 0 S suspend_sys_syn root 8 2 0 0 S suspend root 9 2 0 0 S sync_supers root 102 0 0 S bdi-default root 112 0 0 S kblockd root 122 0 0 S khubd root 132 0 0 S l2cap root 142 0 0 S a2mp root 152 0 0 S modem_notifier root 162 0 0 S smd_channel_clo root 172 0 0 S kworker/0:1 root 182 0 0 S kworker/u:1 root 192 0 0 S rpcrouter root 202 0 0 S rpcrotuer_smd_x root 212 0 0 S krpcserversd root 222 0 0 S kworker/u:2 root 232 0 0 D voicememo_rpc root 242 0 0 S kadspd root 252 0 0 S kswapd0 root 262 0 0 S fsnotify_mark root 272 0 0 S crypto root 402 0 0 S mdp_dma_wq root 412 0 0 S mdp_vsync_wq root 422 0 0 S mdp_hist_wq root 432 0 0 S mdp_pipe_ctrl_w root 452 0 0 S kgsl-3d0 root 462 0 0 S mtdblock0 root 472 0 0 S mtdblock1 root 482 0 0 S mtdblock2 root 492 0 0 S mtdblock3 root 502 0 0 S mtdblock4 root 512 0 0 S mtdblock5 root 522 0 0 S mtdblock6 root 532 0 0 S mtdblock7 root 542 0 0 S mtdblock8 root 552 0 0 S mtdblock9 root 562 0 0 S mtdblock10 root 572 0 0 S mtdblock11 root 582 0 0 S mtdblock12 root 592 0 0 S mtdblock13 root 602 0 0 S mtdblock14 root 612 0 0 S mtdblock15 root 622 0 0 S mtdblock16 root 632 0 0 S mtdblock17 root 642 0 0 S mtdblock18 root 652 0 0 S mtdblock19 root 722 0 0 S k_rmnet_mux_wor root 732 0 0 S f_mtp root 742 0 0 S file-storage root 752 0 0 S kworker/0:2 root 762 0 0 S diag_wq root 772 0 0 S diag_cntl_wq root 782 0 0 S kworker/0:3 root 792 0 0 S irq/146-cyttsp- root 802 0 0 D krtcclntd root 812 0 0 D krtcclntcbd root 822 0 0 S kfmradio root 832 0 0 D kbatteryclntd root 842 0 0 D kbatteryclntcbd root 852 0 0 S irq/82-0-000c root 862 0 0 S KXTIK Workqueue root 872 0 0 S irq/92-kxtik-ir root 882 0 0 S iewq root 892 0 0 D kinteractiveup root 902 0 0 S mmcsdcc_host1 root 912 0 0 S mmcsdcc_host2 root 922 0 0 S binder root 932 0 0 S krfcommd root 942
Re: [b2g] ZTE Open-- bricked when updating OS
Le 23/12/2013 13:28, lgg2l...@gmail.com a écrit : Hello, adb wait-for-device shell stop-b2g /ystem/bin/sh: stop-b2g: not found adb wait-for-device shell stop b2g (nothing and continues with rebooting bucle) Maybe: adb wait-for-device adb shell stop b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Nope, reboot... reboot... reboot... ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Monday, December 23, 2013 2:57:50 PM UTC+2, lgg2...@gmail.com wrote: Nope, reboot... reboot... reboot... Maybe I missed it in your posts but can you boot into recovery(volume up + power)? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Yes, I can get recovery menu (UP+ON), FTM menu (DOWN+ON) and download mode (UP+DOWN+ON). But in the recovery mode I only get signature errors with all roms/firmwares that I have try. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
https://drive.google.com/?tab=goauthuser=0#folders/0B5zNhwBGuTcCWUQ2S29lTXdOSlU On Monday, December 23, 2013 5:52:46 PM UTC+2, an wrote: On Monday, December 23, 2013 5:10:25 PM UTC+2, lgg2...@gmail.com wrote: Hello, Yes, I can get recovery menu (UP+ON), FTM menu (DOWN+ON) and download mode (UP+DOWN+ON). But in the recovery mode I only get signature errors with all roms/firmwares that I have try. That's Firefox OS recovery, right? I'm uploading a zip (will post the link soon) which you might want to try, see if you can flash/boot that one. If it works you will have CWM, Eduardo's boot.img and busybox. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Error: Unable to access folder with ID: 0ADABaPJPIs5fUk9PVA. Check access permissions on the folder. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Try again, I'm not that good with google drive :) On Monday, December 23, 2013 6:05:28 PM UTC+2, lgg2...@gmail.com wrote: Hello, Error: Unable to access folder with ID: 0ADABaPJPIs5fUk9PVA. Check access permissions on the folder. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Sorry but signature verification failed. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I got the same error as lgg2 :( El lunes, 23 de diciembre de 2013 11:56:18 UTC-4:30, an escribió: Try again, I'm not that good with google drive :) On Monday, December 23, 2013 6:05:28 PM UTC+2, lgg2...@gmail.com wrote: Hello, Error: Unable to access folder with ID: 0ADABaPJPIs5fUk9PVA. Check access permissions on the folder. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello, Another with the brick problem after update. No fastboot, ADB during less than 1 second, and reboot, without CWM, with signature error of any firmware that I want install. There are alot of post about people that brick and unbrick this phone and make guides about it, but none of them works. Mozilla Foundation MUST ask to ZTE publish a firmware for Open that works with ZTE handset update software and then It will posible to unbrick ALL Open phones through FTM mode. Mozilla Foundation, do You want to get users and developers? Solve this BIG TROUBLE. Speak with ZTE, make a VALID guide (without use adb/fastboot but FTM or download mode). This ZTE Open was like a first ship, but It is shinking. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
El viernes, 22 de noviembre de 2013 14:18:11 UTC-4:30, Gabriele Svelto escribió: On 22/11/2013 19:38, Ernesto Acosta wrote: I installed the. Zip from this web site without problems, but when the animated Fox show, the phone reboots again and again. Where did you buy it from? I got one from ZTE's UK shop and it had this problem, I solved it by flashing their updated 1.0.1 image available here: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html Look for a file called OPEN(European Standard) SD card upgrading instruction software package(ebay)-225500B0291OPEN_EU_DEV_FFOS_V1.0.0B02 I followed the instructions given in the archive but I had to do the update procedure (boot into fastboot, run the update, etc...) with the phone disconnected from the USB cable. Somehow it entered the non-stop reboot cycle when it was connected. After the update it worked fine and I haven't seen the reboot cycle anymore. Gabriele Can you upload this image to mega or other? version on zte website is v1.1 I have a boot loop :( ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Am Sonntag, 8. Dezember 2013 00:05:54 UTC+1 schrieb Philip Wright: On Saturday, 7 December 2013 22:46:13 UTC, tas_pats wrote: Something change? I need the image for UK ebay ZTE open phone. My phone on 'Android system recovery 3e' only now. So, wait for last resort. I have ZTE published image end with: E:signature verification failed Instalation aborted. On 2013.10.24. 23:04, Michelle Luna: Hi, Sorry for the delayed response, the Mozilla liaison has requested that ZTE post images that are more loose about the key/signature to resolve this. I would add this to the request and appreciate your time to report it to us. Just to clarify, is your case a UK device? Thanks for your patience. Regards, Michelle Luna Mobile Firefox OS Support Manager Mozilla On 10/24/13 6:43 AM, andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g -- Ar cieņu ... __ //IceDove un Debian // //Brīvība un drošība// remove the signature from the update.zip an how can i remove the signature? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Something change? I need the image for UK ebay ZTE open phone. My phone on 'Android system recovery 3e' only now. So, wait for last resort. I have ZTE published image end with: E:signature verification failed Instalation aborted. On 2013.10.24. 23:04, Michelle Luna: Hi, Sorry for the delayed response, the Mozilla liaison has requested that ZTE post images that are more loose about the key/signature to resolve this. I would add this to the request and appreciate your time to report it to us. Just to clarify, is your case a UK device? Thanks for your patience. Regards, Michelle Luna Mobile Firefox OS Support Manager Mozilla On 10/24/13 6:43 AM, andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g -- Ar cieņu ... __ //IceDove un Debian // //Brīvība un drošība// ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Saturday, 7 December 2013 22:46:13 UTC, tas_pats wrote: Something change? I need the image for UK ebay ZTE open phone. My phone on 'Android system recovery 3e' only now. So, wait for last resort. I have ZTE published image end with: E:signature verification failed Instalation aborted. On 2013.10.24. 23:04, Michelle Luna: Hi, Sorry for the delayed response, the Mozilla liaison has requested that ZTE post images that are more loose about the key/signature to resolve this. I would add this to the request and appreciate your time to report it to us. Just to clarify, is your case a UK device? Thanks for your patience. Regards, Michelle Luna Mobile Firefox OS Support Manager Mozilla On 10/24/13 6:43 AM, andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g -- Ar cieņu ... __ //IceDove un Debian // //Brīvība un drošība// remove the signature from the update.zip ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Le 14/10/2013 04:14, julian3...@gmail.com a écrit : Hi, i try to enter into recovery mode of my zte open, but for some reason i don´t get it, not working, i hold the start button and volume up button but the cel starts with the firefox os logo and then the sitting fox but nothing happens, the fox still forever. I'm quite sure you're in fastboot mode here :) To enter recovery, I think you need to use the volume down button instead of the volume up button. signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Le 07/11/2013 22:44, horus...@gmail.com a écrit : I bricked my ZTE Open using the following website http://firefox.ztems.com/ , apparently it's the official ZTE Firefox OS Update Website, but all I managed to do was install B2G from March 2013 using it. Yes, this website is painfully obsolete. From here the device booted, but the Firefox OS Recovery Utility was replaced with Android Recovery Utility, and all Verification failed. Had to then root the device and install CWM recovery using adb http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/ , and then I could flash the ZTE Devices update by removing 3 lines from the updater script regarding assert. the 3 lines are: assert(getprop(ro.product.device) == roamer2 || getprop(ro.build.product) == roamer2); assert(getprop_new(ro.build.display.id) == OPEN_EU_DEV_FFOS); I then self built v1.2 and was able to replace the cwm and the root with Firefox OS Recovery Utility, allowing me to get back to stock Firefox OS 1.0.0 I'm amazed by your obstinacy here, congrats ;) Happy to see you managed to get a working phone back. I hope this mail will help other people too. -- Julien signature.asc Description: OpenPGP digital signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On Wednesday, December 4, 2013 10:58:55 AM UTC+2, Julien Wajsberg wrote: Le 13/10/2013 21:08, an a écrit : Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Thanks for this, I was planing to get a zte open developer device shitty as it is. But don't blame zte, they never claimed to not being there just for your money, blame Firefox execs who rushed out there with a barely working OS on top of garbage hardware. It seems to me that ZTE is making good progress: providing update.zip to enable fastboot mode for older devices, fastboot mode by default for newer devices, things like that. Just got my zte today and it was an old device and thanks to Gabriele Svelto's post I applied the proper update. And guess what, as soon as I did that the OS reported that there is no sd card available. Mac OS X also didn't recognize the sd card and wanted to format it. After configuring udev on Linux the card became available. I agree that the first version of ZTE device was not open, but it's kind of harsh to blame them because you flashed a third party component (CWM recovery) using a hack and now you can't recover. The truth is: they actually care about you even when you do this (see other mails in this thread) and you should actually thank them for caring. No, they should thank me for buying the device, it is their job to provide what they say, a developer device and if there are problems it is their job to provide updates. Forget about cwm, that was the best available at the time. Yes, they probably can do more, but rants like this won't help. I will excuse you for calling my post a rant. Rants like this started as soon as zte open became available and they did help some of the customers, those who could still salvage their device. Otherwise, keep up the good work. -- Julien ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Wondering if anyone can help. After trying to get 1.02 B onto a ZTE open I am now stuck with the ANRDOID recovery 3g recovery tool. Where do I go from here? On Wednesday, August 28, 2013 7:31:21 PM UTC+1, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
All I have on the phone now is the Android Recovery Utility and any attempt to update fails with verification errors. Can I root the phone now? I don't believe so as there is no os ? On Wednesday, August 28, 2013 7:31:21 PM UTC+1, Ernie Powell wrote: I bricked my ZTE Open using the following website http://firefox.ztems.com/ , apparently it's the official ZTE Firefox OS Update Website, but all I managed to do was install B2G from March 2013 using it. From here the device booted, but the Firefox OS Recovery Utility was replaced with Android Recovery Utility, and all Verification failed. Had to then root the device and install CWM recovery using adb http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/ , and then I could flash the ZTE Devices update by removing 3 lines from the updater script regarding assert. the 3 lines are: assert(getprop(ro.product.device) == roamer2 || getprop(ro.build.product) == roamer2); assert(getprop_new(ro.build.display.id) == OPEN_EU_DEV_FFOS); I then self built v1.2 and was able to replace the cwm and the root with Firefox OS Recovery Utility, allowing me to get back to stock Firefox OS 1.0.0 ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
El jueves, 7 de noviembre de 2013 16:44:37 UTC-5, Philip Wright escribió: I bricked my ZTE Open using the following website http://firefox.ztems.com/ , apparently it's the official ZTE Firefox OS Update Website, but all I managed to do was install B2G from March 2013 using it. From here the device booted, but the Firefox OS Recovery Utility was replaced with Android Recovery Utility, and all Verification failed. Had to then root the device and install CWM recovery using adb http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/ , and then I could flash the ZTE Devices update by removing 3 lines from the updater script regarding assert. the 3 lines are: assert(getprop(ro.product.device) == roamer2 || getprop(ro.build.product) == roamer2); assert(getprop_new(ro.build.display.id) == OPEN_EU_DEV_FFOS); I then self built v1.2 and was able to replace the cwm and the root with Firefox OS Recovery Utility, allowing me to get back to stock Firefox OS 1.0.0 I installed the. Zip from this web site without problems, but when the animated Fox show, the phone reboots again and again. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
El viernes, 22 de noviembre de 2013 13:48:11 UTC-5, Gabriele Svelto escribió: On 22/11/2013 19:38, Ernesto Acosta wrote: I installed the. Zip from this web site without problems, but when the animated Fox show, the phone reboots again and again. Where did you buy it from? I got one from ZTE's UK shop and it had this problem, I solved it by flashing their updated 1.0.1 image available here: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html Look for a file called OPEN(European Standard) SD card upgrading instruction software package(ebay)-225500B0291OPEN_EU_DEV_FFOS_V1.0.0B02 I followed the instructions given in the archive but I had to do the update procedure (boot into fastboot, run the update, etc...) with the phone disconnected from the USB cable. Somehow it entered the non-stop reboot cycle when it was connected. After the update it worked fine and I haven't seen the reboot cycle anymore. Gabriele I have a ZTE Open (American Edition). In the MicroSD card I have this: OPEN (American Standard) SD card upgrading instruction software package (ebay)-223990B0249OPEN_US_DEV_FFOS_V1.0.0B02 But when I go to Recovery and try to upgrade from my MicroSD card, tell me: E: failed to Verify whole-file signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? Hi Danie, thank you, yes, what so ever is the button combination, screen remains black and USB being in diagnostic mode UART. QPST software floating around in internet somewhat sees it as in download mode. But I have no nor found any images or software that can be used with the condition of the phone I have. Would really appreciate someone in Mozilla or ZTE to provide a tool or procedure to restore to known state so people can truely use this phone for upgrades to newer FFOS releases, useful development and contributions. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I bricked my ZTE Open using the following website http://firefox.ztems.com/ , apparently it's the official ZTE Firefox OS Update Website, but all I managed to do was install B2G from March 2013 using it. From here the device booted, but the Firefox OS Recovery Utility was replaced with Android Recovery Utility, and all Verification failed. Had to then root the device and install CWM recovery using adb http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/ , and then I could flash the ZTE Devices update by removing 3 lines from the updater script regarding assert. the 3 lines are: assert(getprop(ro.product.device) == roamer2 || getprop(ro.build.product) == roamer2); assert(getprop_new(ro.build.display.id) == OPEN_EU_DEV_FFOS); I then self built v1.2 and was able to replace the cwm and the root with Firefox OS Recovery Utility, allowing me to get back to stock Firefox OS 1.0.0 ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Michelle, I guess you are the same mluna from Mozilla forum. Thank you for your response, my device is from Colombia, and is the same device reported as bricked by my lovely wife aledelreal. https://support.mozilla.org/es/questions/974554#answer-494262 So, we bought the phone in Movistar Colombia. And we took it to technical support. To be frank, we are afraid that Movistar consider the phone has no warranty, because we have upgraded the phone ourselves. El jueves, 24 de octubre de 2013 15:04:09 UTC-5, Michelle Luna escribió: Hi, Sorry for the delayed response, the Mozilla liaison has requested that ZTE post images that are more loose about the key/signature to resolve this. I would add this to the request and appreciate your time to report it to us. Just to clarify, is your case a UK device? Thanks for your patience. Regards, Michelle Luna Mobile Firefox OS Support Manager Mozilla On 10/24/13 6:43 AM, andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
While I have no solution to your problem, I understand how frustrating it is to ask for help and receive no response. Trust me, you are not alone in your displeasure with ZTE and Mozilla. Had I known the level of support that early adopters would receive, I probably never would have purchased the so called Open. On Thu, 24 Oct 2013 06:43:26 -0700 (PDT) andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi, Sorry for the delayed response, the Mozilla liaison has requested that ZTE post images that are more loose about the key/signature to resolve this. I would add this to the request and appreciate your time to report it to us. Just to clarify, is your case a UK device? Thanks for your patience. Regards, Michelle Luna Mobile Firefox OS Support Manager Mozilla On 10/24/13 6:43 AM, andres@gmail.com wrote: I have tried the same procedure that Sven, and get the same message: -- Install /sdcard ... Finding update package... Opening update package... Verifying update package... E:failed to verify whole-file signature E:signature verification failed Installation aborted. I was very happy to have a new smartphone, but now I'm very pissed off and dissapointed with ZTE and Mozilla. El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, but the update from http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html cannot be installed. It says verification failed. Maybe because I tried upgrading/flashing it before, copypasting things with boot.img. Can anyone help? Best, Sven. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Ivan, No problem. Thank you for your reply. Now my phone is in worst condition!, I think I used fastboot erase on a partition that now cause the phone to only have a blank screen. But not fully dead, I get this ZTE CDMA Technologies MSM USB device when connected to PC. Vol up + Power or any combination only leads to a blank screen. Is there anyway you could help me from this state of the phone? Regards, Vinayak ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Naoki, thanks for the hint but was your post adressed at me? If yes - as pointed out in my post from Oct 13th I am not able to access the phone via fastboot, thus I can't reflash it this way. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
This should basically do what you want if you create this as a script. If you want to keep your user data, you'll want to just skip/remove the userdata lines. #!/bin/bash echo + using adb to reboot to fastboot mode adb reboot bootloader echo + Checking to see if we see the device using fastboot fastboot devices echo + Flashing cache fastboot flash cache ramdisk.img echo + Flashing userdata fastboot flash userdata userdata.img echo + Flashing system fastboot flash system system.img echo + Flashing boot fastboot flash boot boot.img echo + Flashing rebooting the device fastboot reboot echo + Done! On 10/15/13 12:50 PM, jezra wrote: I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you. It appears that boot.img is not part of the build process; only ramdisk.img, userdata.img, and system.img get built. How/where do I find the boot.img? On Tue, 15 Oct 2013 13:36:10 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: This should basically do what you want if you create this as a script. If you want to keep your user data, you'll want to just skip/remove the userdata lines. #!/bin/bash echo + using adb to reboot to fastboot mode adb reboot bootloader echo + Checking to see if we see the device using fastboot fastboot devices echo + Flashing cache fastboot flash cache ramdisk.img echo + Flashing userdata fastboot flash userdata userdata.img echo + Flashing system fastboot flash system system.img echo + Flashing boot fastboot flash boot boot.img echo + Flashing rebooting the device fastboot reboot echo + Done! On 10/15/13 12:50 PM, jezra wrote: I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing
Re: [b2g] ZTE Open-- bricked when updating OS
It's the second link I emailed; here is the link again, courtesy of Eduardo : http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html On 10/15/13 1:54 PM, jezra wrote: Thank you. It appears that boot.img is not part of the build process; only ramdisk.img, userdata.img, and system.img get built. How/where do I find the boot.img? On Tue, 15 Oct 2013 13:36:10 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: This should basically do what you want if you create this as a script. If you want to keep your user data, you'll want to just skip/remove the userdata lines. #!/bin/bash echo + using adb to reboot to fastboot mode adb reboot bootloader echo + Checking to see if we see the device using fastboot fastboot devices echo + Flashing cache fastboot flash cache ramdisk.img echo + Flashing userdata fastboot flash userdata userdata.img echo + Flashing system fastboot flash system system.img echo + Flashing boot fastboot flash boot boot.img echo + Flashing rebooting the device fastboot reboot echo + Done! On 10/15/13 12:50 PM, jezra wrote: I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of what I was expecting from a device marketed as developer phone - not mentioning that it's completely crazy when looking at it from an ecologic perspective. Vinayak: Well, this is as similar to my situation, I assume you can also access see the device over USB being in diagnostic mode when you boot it by holding both voldown+volup + power although the screen remains black? ___ dev-b2g mailing list
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you. I suppose I was expecting something more official than a file hosted on a 3rd party file locker, but if it works I'll be content. On Tue, 15 Oct 2013 15:51:14 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: It's the second link I emailed; here is the link again, courtesy of Eduardo : http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html On 10/15/13 1:54 PM, jezra wrote: Thank you. It appears that boot.img is not part of the build process; only ramdisk.img, userdata.img, and system.img get built. How/where do I find the boot.img? On Tue, 15 Oct 2013 13:36:10 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: This should basically do what you want if you create this as a script. If you want to keep your user data, you'll want to just skip/remove the userdata lines. #!/bin/bash echo + using adb to reboot to fastboot mode adb reboot bootloader echo + Checking to see if we see the device using fastboot fastboot devices echo + Flashing cache fastboot flash cache ramdisk.img echo + Flashing userdata fastboot flash userdata userdata.img echo + Flashing system fastboot flash system system.img echo + Flashing boot fastboot flash boot boot.img echo + Flashing rebooting the device fastboot reboot echo + Done! On 10/15/13 12:50 PM, jezra wrote: I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: I apologize. I wasn't aware that you had not built your own images, that was my bad assumption. Have you installed the android sdk? You will need to do so in order to flash the device. Also which platform are you using ( Windows, Mac or linux )? Regards, Naoki On 10/15/13 12:25 PM, jezra wrote: Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: The script flash.sh in the main repository should flash all the parts including the boot.img. ie: project folder/flash.sh On 10/15/13 11:03 AM, jezra wrote: Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 平田修樹 (Naoki Hirata) nhir...@mozilla.com wrote: https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes FYI, Inari refers to the ZTE Open. Doing the vol down+up + power should put you in fastboot mode. This means that the fastboot should be able to see the device. ie: fastboot devices If that is the case, then you can flash partition images onto the phone using fastboot. This is what the flash.sh script does. It puts the device in fastboot mode and then flashes the images per fastboot. Chances if you are in fastboot mode then the boot.img that they pointed you to worked. The problem is described by Eduardo on a separate thread: http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once you place the boot.img in the proper location, give flash.sh another go. If that still doesn't work please let me know. The other thing we could potentially do is flash just gecko/gaia on the device provided that you can reboot the device and have adb access. This is done by : project folder/flash.sh gecko project folder/gaia/make reset-gaia Regards, Naoki On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: Michael: Thank you but, it took around 15 e-mails and over two weeks mailing around with the eBay seller until they actually understood my problem. They kept pointing me to the download already discussed in this thread over and over again, and I had the impression that I was talking to a wall. As explained, when they finally realized the actual problem they offered me a new phone for 80% of the initial price (which is a 20% discount). Again, I am not willing to throw an almost completely new phone (never carried around, no scratches, screen cover not removed yet etc.) in the trash can and buy a (discounted) new one just because the firmware is bricked and ZTE refuses to reflash it. This is the complete opposite of
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Sibekai, Excuse me for the late reply. It seems you have not erased your recovery image. Is your phone still booted into recovery mode (Power off the phone, then hold the power key and volume up key simultaneously)? If your phone can still boot into recovery mode, I wonder if this can be option for you to try again. Package for UK phone: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html Package for US phone: http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html Best Regards, Ivan Tsay sibekai vinayak.karia...@gmail.com 於 Oct 11, 2013 9:02 PM 寫道： Hi Ivan, My ZTE open stops at a blank screen with few white lines on top. Connecting USB to Windows 7 pc would enable the fastboot to list is as roamer2 device. This happened after I rooted the stock ZTE open from eBay (purchased US, shipped from UK) with the EU SD package content, but ASSERTs removed in the update-script and repackaging it so as to bypass the verification failure. The recovery mode (recovery-clockwork-6.0.3.3-roamer2.img), ended up with Installation Failed (instead of verification failed). After the above step, I ended up with just the firefox os splash screen going no where but able to see the device using fastboot. I tried something more, used fastboot erase on boot, splash, system etc. and ended up with what I have now :-(... complete stupid newbie mistakes may be? The fastboot only successfully does erase, flash function ends up with FAILED read status failed (too many links) . Do you think I have any shot at unbricking my device? Best regards. On Saturday, September 14, 2013 1:48:42 AM UTC+2, Ivan Tsay wrote: Is your ZTE Open phone bought on UK eBay? I wonder what Spanish site you are referring for the package update. Best Regards, Ivan Tsay 於 9/13/13 7:35 PM, xperime...@gmail.com 提到: Hi I have also briked my phone after updating to the last avaliable update in the spanish site. I have managed to install the uk update but carrier dont work and system is too unestable. From 5 boot times only one is ok. Can you help me? Thx ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Extremely poor judgment when vetting partners On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) an novac.a...@gmail.com wrote: Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Thanks for this, I was planing to get a zte open developer device shitty as it is. But don't blame zte, they never claimed to not being there just for your money, blame Firefox execs who rushed out there with a barely working OS on top of garbage hardware. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
My comment wasn't directed at your judgment. I was actually agreeing with you and I feel that Mozilla did an extremely poor job in vetting ZTE as a 'partner'. As an owner of a ZTE Open, my best advise would be to avoid the ZTE and get a phone from a company that seems to care. If the rollout of 1.1 is any indication, get a geeksphone; they've had 1.1 for a few months and, from what I can tell, they haven't had anti-consumer locks on the devices that they manufacture. jezra On Mon, 14 Oct 2013 21:18:09 +0300 andu novac novac.a...@gmail.com wrote: Can you elaborate, which part is extremely poor in my judgement? The fact that we have this exchange on this list should at least tell you that I am both interested in this OS and also aware of its current state/problems from people who actually work on it. I also installed it on my phone but since I didn't get any usable help on the power button issue I gave up on that. Also the fact that I was willing to spend 80E on a less then minimally attractive device just for its OS should also tell you something (yeah, maybe this is the poor judgement you were referring to). But what do you say about the partners who market a phone that bricks itself while upgrading and instead of providing service or replacement they want to sell you a new one? On Mon, Oct 14, 2013 at 7:12 PM, jezra je...@jezra.net wrote: Extremely poor judgment when vetting partners On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) an novac.a...@gmail.com wrote: Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Thanks for this, I was planing to get a zte open developer device shitty as it is. But don't blame zte, they never claimed to not being there just for your money, blame Firefox execs who rushed out there with a barely working OS on top of garbage hardware. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Can you elaborate, which part is extremely poor in my judgement? The fact that we have this exchange on this list should at least tell you that I am both interested in this OS and also aware of its current state/problems from people who actually work on it. I also installed it on my phone but since I didn't get any usable help on the power button issue I gave up on that. Also the fact that I was willing to spend 80E on a less then minimally attractive device just for its OS should also tell you something (yeah, maybe this is the poor judgement you were referring to). But what do you say about the partners who market a phone that bricks itself while upgrading and instead of providing service or replacement they want to sell you a new one? On Mon, Oct 14, 2013 at 7:12 PM, jezra je...@jezra.net wrote: Extremely poor judgment when vetting partners On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) an novac.a...@gmail.com wrote: Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Thanks for this, I was planing to get a zte open developer device shitty as it is. But don't blame zte, they never claimed to not being there just for your money, blame Firefox execs who rushed out there with a barely working OS on top of garbage hardware. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Ah, a misunderstanding, glad we agree. IMO Mozilla should have used at this stage just existing devices (and encourage porting!) rather then come up with these developer phones and the like. Just asking for extra trouble on a platform which is still green. On Mon, Oct 14, 2013 at 9:35 PM, jezra je...@jezra.net wrote: My comment wasn't directed at your judgment. I was actually agreeing with you and I feel that Mozilla did an extremely poor job in vetting ZTE as a 'partner'. As an owner of a ZTE Open, my best advise would be to avoid the ZTE and get a phone from a company that seems to care. If the rollout of 1.1 is any indication, get a geeksphone; they've had 1.1 for a few months and, from what I can tell, they haven't had anti-consumer locks on the devices that they manufacture. jezra On Mon, 14 Oct 2013 21:18:09 +0300 andu novac novac.a...@gmail.com wrote: Can you elaborate, which part is extremely poor in my judgement? The fact that we have this exchange on this list should at least tell you that I am both interested in this OS and also aware of its current state/problems from people who actually work on it. I also installed it on my phone but since I didn't get any usable help on the power button issue I gave up on that. Also the fact that I was willing to spend 80E on a less then minimally attractive device just for its OS should also tell you something (yeah, maybe this is the poor judgement you were referring to). But what do you say about the partners who market a phone that bricks itself while upgrading and instead of providing service or replacement they want to sell you a new one? On Mon, Oct 14, 2013 at 7:12 PM, jezra je...@jezra.net wrote: Extremely poor judgment when vetting partners On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) an novac.a...@gmail.com wrote: Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Thanks for this, I was planing to get a zte open developer device shitty as it is. But don't blame zte, they never claimed to not being there just for your money, blame Firefox execs who rushed out there with a barely working OS on top of garbage hardware. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Below is the return policy for e-Bay ZTE Open phones: * Note: Any problems, please contact our customer service first. No RMA, we won't sign for the item you return. * We want our customer to be happy with their new product. As you buying our products without have an opportunity to examine it, within 7 working days from the day after we first attempted to deliver your product we will either exchange it or cancel your agreement and provide a refund as detailed below:* 7 Days Return:* The returns period and the following instructions apply to sim free mobile phone. If upon receiving your handset you decide you no longer want the handset or the contract then you can complete a 7 working days return, for this to be completed you need to: 1.Contact our customer service team by 2.Ensure the Sim/Handset/Gift/Accessories has not been used 3.All products returned preferable in their original packaging 4.Retain a returns number( RMA), which you will be supplied and seal the product 5.a. Returns Number(RMA) b. All content which include: handset, accessories and free gift. 6.Must send the parcel back via special delivery, otherwise this policy will not apply to your case 7.The refund(postage will not include) will be issued via PayPal after confirmation of receiving your returned parcel in required condition 8.Advise our customer service team once you send your parcel( please include tracking number, your name, address, RMA and delivery date when you contact us) by email 9.Please allow up to 28 days from the date our warehouse received the phone, for send you feedback of case processing updatess* 60 Days Exchange:* If your original handset becomes faulty, we will be happy to offer a 60 day exchange. The average turn around time of an exchange is 72 hours depending if it falls on a weekend. To process an exchange you need to: 1.Contact our customer service team by 2.Retain an exchange code which you will be supplied 3.Please keep the free gift 4.All products returned preferably in their original packaging. 5.The returned parcel must include: a. Exchange code b. Handset, charger, battery, manual and any other included accessories c. Return form with information filled in, you will be issued one when you contact customer service team 6.Send the parcel back via Royal mail special delivery, liability for the handset remains with you until we receive it back. 7.Send the parcel back the warehouse within 48 hours of setting up the exchange 8.Please notify our customer service team once you send the parcel(please include racking number, your name, address, RMA and delivery date when you contact us) 9.Please note if the one of above requirement doesn't meet then 60 day exchange police will not apply to your case. The warehouse will send the handset back to you immediately.* Faulty Goods* If your handset becomes faulty outside of your 60 day exchange period then a repair can be arranged (please note this service only apply to the handset comes with valid manufacture warranty).To set up a repair you will need to: 1.Contact our customer service team by 2.The returned parcel for repair must include: a.RMA number ( you will issued one when you contact our customer service team) b.Faulty unit c.Return form with information filled in, you will be issued one when you contact customer service team 3.We suggest you send the repair unit by royal mail special delivery as it is an insured service, liability for the handset remains with you until we receive it back. 4.Please notify our customer service team once you send the parcel (please include racking number, your name, address, RMA and delivery date when you contact us). 5.We will notify you cost of repair, you can choose either you want this service or not. 6.If you choosing not to carry on repair service, there are two options for your to choose: a. we can deliver the faulty handset to you and you will be charged a delivery fee based on the type of handset; b. You can notify us to keep the faulty handset and our repair specialists will dispose your faulty unit safely. c.Please contact our customer service once you made your choice 7.Please allow up to 28 days of repair process to finish. Your hand set will send back to you by tracked service. We will notify you by email when the repairer process is finished. *Note: The Refunds, Exchange and Repair Policy do not affect your statutory rights.* *Additional guarantee from ZTE: * *If your phone was bricked during upgrade, because of ZTE provided wrong upgrade files. You may apply to exchange a new one at e-Bay store. Please contact ZTE e-Bay store via e-Bay message. * Thomas ? 13/10/13 ??12:37, daniel.i...@googlemail.com ??: Andreas was so kind to forward my issue to some other Mozilla people who now forwarded it to ZTE. I really hope that ZTE will find a better way to deal with this situation, especially if I'm not the only having this
Re: [b2g] ZTE Open-- bricked when updating OS
I also have a bricked ZTE Open, yes one of the early ones without the later fastboot update. Mine is neither accessible via fastboot nor adb anymore, only through the diagnostics interface. I can't get into clockworkmod recovery (it hangs), so it requires some sort of low level flash. Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Please - if somebody knows how to do a low level flash of this phone (i have backups of all partitions), please provide some instructions. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
I will send an email to ZTE about this. I will let you know what they say. Andreas Sent from Mobile. On Oct 13, 2013, at 6:40, daniel.i...@googlemail.com daniel.i...@googlemail.com wrote: I also have a bricked ZTE Open, yes one of the early ones without the later fastboot update. Mine is neither accessible via fastboot nor adb anymore, only through the diagnostics interface. I can't get into clockworkmod recovery (it hangs), so it requires some sort of low level flash. Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Please - if somebody knows how to do a low level flash of this phone (i have backups of all partitions), please provide some instructions. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Andreas was so kind to forward my issue to some other Mozilla people who now forwarded it to ZTE. I really hope that ZTE will find a better way to deal with this situation, especially if I'm not the only having this problem. I own a couple other devices, but normally for developer devices there is a way to recover from a brick without the manufacturer's help (i.e. sbf_flash for Motorola Devices or Odin/Heimdall for Samsung). For other ZTE devices like the ZTE Skate III there seem to be various other tricks like putting a specially named image with contents on the SDcard or some external tools. I am pretty sure there is also something similar for the ZTE Open (which seems to be pretty much the same as the ZTE KIS), so it would be extremely helpful if ZTE would share their info with FFOS developers/enthusiasts. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
On 13/10/13 09:36 AM, daniel.i...@googlemail.com wrote: I also have a bricked ZTE Open, yes one of the early ones without the later fastboot update. Mine is neither accessible via fastboot nor adb anymore, only through the diagnostics interface. I can't get into clockworkmod recovery (it hangs), so it requires some sort of low level flash. Unfortunately, ZTE refuses any support (even if you would pay for the reflash!) in this case and redirects all requests to the eBay seller who proposes to send me a new device for 80% of the price. Sorry guys, but this is absolutely unacceptable! Please - if somebody knows how to do a low level flash of this phone (i have backups of all partitions), please provide some instructions. You can download the update.zip image from ZTE directly. You put it on the SD card and boot the phone. It will update. To download For the US phone http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html For the European phone: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html I don't have a device myself but I have been told this works from people that has similar issues. Hope this helps. Hub ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hubert: Thanks, but this works unless you haven't also bricked your recovery. If you look at the instructions inside the archive you can see that it needs to be flashed from recovery. Holding down the volume rocker will not start flashing blindly but just get you into recovery. This might help for some people, but unfortunately not for me. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
El miércoles, 28 de agosto de 2013 13:31:21 UTC-5, Ernie Powell escribió: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. Hi, i try to enter into recovery mode of my zte open, but for some reason i don´t get it, not working, i hold the start button and volume up button but the cel starts with the firefox os logo and then the sitting fox but nothing happens, the fox still forever. Anyone know what happens? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi I have also briked my phone after updating to the last avaliable update in the spanish site. I have managed to install the uk update but carrier dont work and system is too unestable. From 5 boot times only one is ok. Can you help me? Thx ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Is your ZTE Open phone bought on UK eBay? I wonder what Spanish site you are referring for the package update. Best Regards, Ivan Tsay 於 9/13/13 7:35 PM, xperime...@gmail.com 提到: Hi I have also briked my phone after updating to the last avaliable update in the spanish site. I have managed to install the uk update but carrier dont work and system is too unestable. From 5 boot times only one is ok. Can you help me? Thx ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hello Ivan, I got a bricked devices and I was not able to flash the ZTE Open US update, I got verification failed errors, What can be done about this? Vlad. On Thursday, September 5, 2013 7:05:53 AM UTC-5, Ivan Tsay wrote: Hi Ernie, Thank you for the greeting. Hopefully your issue has been resolved. Best Regards, Ivan Tsay Engineering Project Manager, Firefox OS Mozilla Corporation - mozilla.com.tw TEL: +886-2-87861100 ext. 339 於 9/4/13 8:37 PM, Ernie Powell 提到: Hi Ivan, Thank you so much for facilitating this recovery. I hope you, Kevin and the rest of the Firefix team great success in the future. Best, Ernie On Wednesday, September 4, 2013, Ivan Tsay wrote: Hi Ernie, Our partner has released the US package for the recovery of ZTE Open purchased on US eBay. Please download the package from the link below and follow the instruction in PDF to recover your phone. http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html Best Regards, Ivan Tsay Engineering Project Manager, Firefox OS Mozilla Corporation - mozilla.com.tw TEL: +886-2-87861100 ext. 339 於 9/2/13 8:37 PM, Ernie Powell 提到: Hi Ivan, This is fantastic news! The purchase was made via the US eBay site. Regards, Ernie On Sunday, September 1, 2013, Ivan Tsay wrote: Hi Ernie, Our partner will release the package for the recovery of the bricked phone soon. May I know if your phone was purchased on the US eBay or UK eBay? It would be very helpful for us to provide the correct information for you to recover your phone. Thank you! Best Regards, Ivan Tsay 於 8/29/13 2:50 PM, Kevin Hu 提到: Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Ernie, Thank you for the greeting. Hopefully your issue has been resolved. Best Regards, Ivan Tsay Engineering Project Manager, Firefox OS Mozilla Corporation - mozilla.com.tw TEL: +886-2-87861100 ext. 339 於 9/4/13 8:37 PM, Ernie Powell 提到: Hi Ivan, Thank you so much for facilitating this recovery. I hope you, Kevin and the rest of the Firefix team great success in the future. Best, Ernie On Wednesday, September 4, 2013, Ivan Tsay wrote: Hi Ernie, Our partner has released the US package for the recovery of ZTE Open purchased on US eBay. Please download the package from the link below and follow the instruction in PDF to recover your phone. http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html Best Regards, Ivan Tsay Engineering Project Manager, Firefox OS Mozilla Corporation - mozilla.com.tw TEL: +886-2-87861100 ext. 339 於 9/2/13 8:37 PM, Ernie Powell 提到: Hi Ivan, This is fantastic news! The purchase was made via the US eBay site. Regards, Ernie On Sunday, September 1, 2013, Ivan Tsay wrote: Hi Ernie, Our partner will release the package for the recovery of the bricked phone soon. May I know if your phone was purchased on the US eBay or UK eBay? It would be very helpful for us to provide the correct information for you to recover your phone. Thank you! Best Regards, Ivan Tsay 於 8/29/13 2:50 PM, Kevin Hu 提到: Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Ernie, Our partner has released the US package for the recovery of ZTE Open purchased on US eBay. Please download the package from the link below and follow the instruction in PDF to recover your phone. http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html Best Regards, Ivan Tsay Engineering Project Manager, Firefox OS Mozilla Corporation - mozilla.com.tw TEL: +886-2-87861100 ext. 339 於 9/2/13 8:37 PM, Ernie Powell 提到: Hi Ivan, This is fantastic news! The purchase was made via the US eBay site. Regards, Ernie On Sunday, September 1, 2013, Ivan Tsay wrote: Hi Ernie, Our partner will release the package for the recovery of the bricked phone soon. May I know if your phone was purchased on the US eBay or UK eBay? It would be very helpful for us to provide the correct information for you to recover your phone. Thank you! Best Regards, Ivan Tsay 於 8/29/13 2:50 PM, Kevin Hu 提到: Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Ivan, This is fantastic news! The purchase was made via the US eBay site. Regards, Ernie On Sunday, September 1, 2013, Ivan Tsay wrote: Hi Ernie, Our partner will release the package for the recovery of the bricked phone soon. May I know if your phone was purchased on the US eBay or UK eBay? It would be very helpful for us to provide the correct information for you to recover your phone. Thank you! Best Regards, Ivan Tsay 於 8/29/13 2:50 PM, Kevin Hu 提到: Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. __**_ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/**listinfo/dev-b2ghttps://lists.mozilla.org/listinfo/dev-b2g __**_ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/**listinfo/dev-b2ghttps://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi Ernie, Our partner will release the package for the recovery of the bricked phone soon. May I know if your phone was purchased on the US eBay or UK eBay? It would be very helpful for us to provide the correct information for you to recover your phone. Thank you! Best Regards, Ivan Tsay 於 8/29/13 2:50 PM, Kevin Hu 提到: Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Hi, Ernie, Thank you for your information. We are handling this issue with the partner. Will update to you as soon as possible. Thank you. Thanks. Kevin Hu On Aug 28, 2013, at 11:31 AM, Ernie Powell wrote: Hi, So I bought a Firefox ZTE Open about a week ago on Ebay-- when it was the thing to do. I connected it to my wifi network and saw what it could do. Liked it. After a while, I received a request to update the OS, about a 35 MB package in total. Didn't think nothing of it so I said okay and it began downloading. Flash forward to 9 hours later and it was still downloading. For some reason, I ended up turning off the phone while it was still updating. I thought, maybe it'll just abort and I can start fresh. Wrong. Now when I power on the phone, it wont go past the the boot screen. Sadly, I didn't even think to enable the USB debugging. Is there any way to get the original image back on the phone, given that it is not in USB debugging mode? I noticed a bootloader menu screen when I hold down the power and up volume button, and a FTM (FML?) screen when I hold the other direction, but havent been successful in finding a factory ZTE Open image online. Any help would be greatly appreciated. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
