Closed
Bug 956584
Opened 10 years ago
Closed 10 years ago
ZTE Open can't apply any updates from SD card and is inaccessible to adb and fastboot
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: znmeb, Unassigned)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140104030204 Steps to reproduce: 1. Bought a US ZTE Open from eBay (September 2013) 2. Updated it to 1.1 in late December via http://download.ztedevices.com/UpLoadFiles/product/643/3601/soft/2013121011161582.zip 3. Updated it to 1.2 via https://hacks.mozilla.org/2013/12/upgrading-your-zte-open-to-firefox-os-1-1/comment-page-1/#comment-2156531 The phone worked for a while at 1.2 but I decided to go back to 1.1 and did a reset to factory settings. The phone didn't boot back up all the way. Now the phone will not respond to adb or fastboot from either Fedora Linux or Windows 8.1. The USB drivers do see it but it isn't responding. And I can't install updates from an SD card any more. They all crash with signature verification failures. I'm attaching a 'recovery.log' Actual results: Phone can no longer be updated or flashed Expected results: I should be able to re-flash the phone via adb/fastboot or apply an update using the SD card.
P.S.: There are numerous similar cases in the forums - at least two separate threads plus the discussion on the Mozilla hacks blog describing the ZTE 1.1 update process. I'm watching most of them and most of the ZTE Open bugs here. There's also a discussion on the B2G Google group.
Here's one of the forum threads: https://support.mozilla.org/en-US/questions/976414
Another forum thread: https://support.mozilla.org/en-US/questions/980006
In Spanish, but Google Translate does fairly well with it: http://www.google.com/url?q=http%3A%2F%2Fgnulinuxvagos.es%2Ftopic%2F2187-he-brickeado-mi-zte-open-%25C2%25BFy-ahora-qu%25C3%25A9%2F&sa=D&sntz=1&usg=AFQjCNH1mjeFBBdanI2c2ZyK3-I8EmzDJA
Google Groups thread: https://groups.google.com/forum/?hl=en#!searchin/mozilla.dev.b2g/zte$20open$20bricked|sort:date/mozilla.dev.b2g/pPLsGpEUqxc/NRf6vfkUQmMJ
Comment 6•10 years ago
|
||
Bug followed from https://support.mozilla.org/en-US/questions/976414?page=2#answer-519520 Flagging Naoki
Flags: needinfo?(nhirata.bugzilla)
One ZTE thread has been closed with a 'solution' - send the device back to seller. :-( https://support.mozilla.org/en-US/questions/981676#answer-518860
(In reply to Andrew Truong [:feer56] from comment #6) > Bug followed from > https://support.mozilla.org/en-US/questions/976414?page=2#answer-519520 > > Flagging Naoki Is there any known way to recover access to the ZTE Open? I've had it since mid-September - I'm not sure I can still send it back to the seller.
Try reseting the cache either by fastboot or system recovery.
ie : adb reboot bootloader fastboot erase cache or hold power + vol. up on reboot and select the erase cache option. I'm not 100 % sure it will work. Also to note, 1.2 data -> 1.1 data isn't supported so you may have to delete the data part as well now that I think about it. we have migration code from 1.1 to 1.2, not vice versa.
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 11•10 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #10) > ie : > adb reboot bootloader > fastboot erase cache > > or > hold power + vol. up on reboot > and select the erase cache option. > > I'm not 100 % sure it will work. Also to note, 1.2 data -> 1.1 data isn't > supported so you may have to delete the data part as well now that I think > about it. we have migration code from 1.1 to 1.2, not vice versa. I've tried both and neither works. I can get to recovery mode and erase cache or do a factory reset, but neither Linux nor Windows adb / fastboot see the device in any mode.
Comment 12•10 years ago
|
||
(In reply to znmeb from comment #0) > Now the phone will not respond to adb or fastboot from either Fedora Linux > or Windows 8.1. The USB drivers do see it but it isn't responding. And I > can't install updates from an SD card any more. They all crash with > signature verification failures. I'm attaching a 'recovery.log' Did you try flashing the ZIP file pointed to by the Spanish thread using the SD-card update method? This is the link that appears in that thread: http://uploaded.net/file/sg97g0qj
Comment 13•10 years ago
|
||
BTW the problem with the "signature verification failure" issue seem to be caused by the 1.2 update installing the AOSP keys on the device instead of the ZTE ones which make all ZTE provided images unusable with the SD-card upgrade method.
Reporter | ||
Comment 14•10 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #12) > (In reply to znmeb from comment #0) > > Now the phone will not respond to adb or fastboot from either Fedora Linux > > or Windows 8.1. The USB drivers do see it but it isn't responding. And I > > can't install updates from an SD card any more. They all crash with > > signature verification failures. I'm attaching a 'recovery.log' > > Did you try flashing the ZIP file pointed to by the Spanish thread using the > SD-card update method? This is the link that appears in that thread: > http://uploaded.net/file/sg97g0qj Not yet - that's on one of those affiliate download sites - I get one shot at a 38-minute download for free every hour, or I pay them money to get it in 19 seconds. Sorry, I don't do that stuff and neither should Mozilla or ZTE!
Reporter | ||
Comment 15•10 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #13) > BTW the problem with the "signature verification failure" issue seem to be > caused by the 1.2 update installing the AOSP keys on the device instead of > the ZTE ones which make all ZTE provided images unusable with the SD-card > upgrade method. In that case can I get an image signed with AOSP keys into a zip file, copy the zip file to the SD card and update the device in the recovery menu?
Comment 16•10 years ago
|
||
(In reply to znmeb from comment #14) > Not yet - that's on one of those affiliate download sites - I get one shot > at a 38-minute download for free every hour, or I pay them money to get it > in 19 seconds. Sorry, I don't do that stuff and neither should Mozilla or > ZTE! Unfortunately Mozilla cannot host those images due to legal reasons about distributing ZTE's binary blobs otherwise we would already have :-( (In reply to znmeb from comment #15) > In that case can I get an image signed with AOSP keys into a zip file, copy > the zip file to the SD card and update the device in the recovery menu? Yes, it should, and I think that's basically what they've done in the image provided by that link. If you want to try your luck with a more recent build you could experiment with the patches in bug 935059. They add build targets for creating FOTA images from our sources. We haven't given them much testing on the ZTE Open so tread carefully.
Reporter | ||
Comment 17•10 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #16) > (In reply to znmeb from comment #14) > > Not yet - that's on one of those affiliate download sites - I get one shot > > at a 38-minute download for free every hour, or I pay them money to get it > > in 19 seconds. Sorry, I don't do that stuff and neither should Mozilla or > > ZTE! > > Unfortunately Mozilla cannot host those images due to legal reasons about > distributing ZTE's binary blobs otherwise we would already have :-( > > (In reply to znmeb from comment #15) > > In that case can I get an image signed with AOSP keys into a zip file, copy > > the zip file to the SD card and update the device in the recovery menu? > > Yes, it should, and I think that's basically what they've done in the image > provided by that link. > > If you want to try your luck with a more recent build you could experiment > with the patches in bug 935059. They add build targets for creating FOTA > images from our sources. We haven't given them much testing on the ZTE Open > so tread carefully. I think I'll try that - I've got all the scripting to build from source already done, and that's why I bought the phone in the first place. ;-)
Reporter | ||
Comment 18•10 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #16) > (In reply to znmeb from comment #14) > > Not yet - that's on one of those affiliate download sites - I get one shot > > at a 38-minute download for free every hour, or I pay them money to get it > > in 19 seconds. Sorry, I don't do that stuff and neither should Mozilla or > > ZTE! > > Unfortunately Mozilla cannot host those images due to legal reasons about > distributing ZTE's binary blobs otherwise we would already have :-( Well - it turns out you have to wait *three* hours between downloads for the free version *and* if the download fails, which it did after about five minutes, you're out of luck. I am *not* giving these clowns a credit card number for something that may or may not work and may or may not violate someone's intellectual property laws in China, Spain, Latin America or Switzerland. > > (In reply to znmeb from comment #15) > > In that case can I get an image signed with AOSP keys into a zip file, copy > > the zip file to the SD card and update the device in the recovery menu? > > Yes, it should, and I think that's basically what they've done in the image > provided by that link. > > If you want to try your luck with a more recent build you could experiment > with the patches in bug 935059. They add build targets for creating FOTA > images from our sources. We haven't given them much testing on the ZTE Open > so tread carefully.
Reporter | ||
Comment 19•10 years ago
|
||
Latest status - the phone is now running the ZTE European 1.1 software. The guts of what has to happen to unbrick the phone can be found in this forum thread. https://support.mozilla.org/en-US/questions/976414 So - where do we go from here? Certainly there's some documentation that needs to happen but I don't think there's a Mozilla software bug here. So I'm going to mark it 'RESOLVED - INVALID' - I'd be happy to help test out documentation now that I have a path back to sanity. Thanks to 'mautematico' for creating an SD zip archive that unbricked the phone!
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•