Re: [b2g] I can no longer access to ZTE Open nightly updates
Hello, In that way, also You must anounce OFFICIALy the END of the ZTE Open (Inari) life (and support of course). That must be because neither ZTE nor Mozilla will take anymore account about it. I think that It si not the correct way, having problems in the 1.x terminals and jumping to 2.x without solve them. After the troubles that I had with ZTE Open and seeying this blocking position of ZTE and Mozilla I (and more people I think) have something clear: - I will no change the terminal after six month because the only by the ZTE and Mozilla faulty support of it. - I will no trust more (include buy) in ZTE or Mozilla. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I can no longer access to ZTE Open nightly updates
Hello, No one answer about this? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I can no longer access to ZTE Open nightly updates
Hello, And, Why instead of completely closing access, have not been removed, for example, updates from last week, leaving some past? How do want to try the new patch updates, or if you have solved the problem if there is no access to them? Can there be some other hidden reason? ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I can no longer access to ZTE Open nightly updates
Hello, The same problem. Also I can not access to http://updates.boot2gecko.org/inari ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] v1.2 for ZTE Open from the Ebay Seller
Hello, Check this: https://groups.google.com/d/msg/mozilla.dev.b2g/pPLsGpEUqxc/_qFw4CeRTqcJ ___ 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
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
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
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
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
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
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
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
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
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
