Building for the Alcatel One Touch Fire

[Łukasz Wójciak]

Hi,

The Alcatel One Touch Fire ships with firefoxOS v 1.0.1.0 (firmware version 01005P) will it be compatible with the development version of the OS and with this install guide https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build

?

Cheers,
Luke

[rafal.piot...@gmail.com]

Hi Łukasz,

have you been able to find the ADB drivers for the Alcatel One Touch Fire? If so, where can I find those?

Regards,

Rafał

[Jan Jongboom]

Yes. You'll have to build the hamachi target.

[Jan Jongboom]

You can send an e-mail to me, I have drivers. Don't think I can just put them on the internets myself.

[jarek...@gmail.com]

On Monday, July 29, 2013 9:16:50 AM UTC+2, Jan Jongboom wrote:
> Yes. You'll have to build the hamachi target.

Thanks, that's a very useful info.

However, could you please shed some light on what actually "hamachi" is? Is this an actual device, with which OneTouch Fire is compatible, or maybe it's a codename of a hardware platform?

I understand this info is not needed to build the target ;) I'm just curious, as I would never guess that OneTouch Fire == hamachi.

[Jan Jongboom]

It's the codename for the device afaik

[Jan Jongboom]

On Tuesday, July 30, 2013 4:01:10 PM UTC+2, Jarek wrote:

And I had to actually get this info from someone at TCL because I didn't make that guess eihter :-)

[Jarek]

> And I had to actually get this info from someone at TCL because I didn't make that guess eihter :-)

OK, thanks for the explanation and for sharing this info.

[jacek.r...@gmail.com]

W dniu wtorek, 30 lipca 2013 16:35:41 UTC+2 użytkownik Jarek napisał:
> > And I had to actually get this info from someone at TCL because I didn't make that guess eihter :-)
>
>
>
> OK, thanks for the explanation and for sharing this info.

Did you guys try to update OS to 1.1 on that Alcatel? Any success?:)

--
Jacek

[Jan Jongboom]

Yep, I'm running 1.1 on my Alcatel phone. Just run

BRANCH=v1-train ./config.sh hamachi

and follow other instructions...

If anyone is interested I can provide pre-made builds for 1.1 (they may have some Telenor branding though :-))

[Łukasz Wójciak]

Hi, Thanks for the answers guys! It would be great if you could send me a prebuild of the 1.1 os version kontakt[at]wojciak.com.pl.

The drivers seem to be available now:
http://www.alcatelonetouch.com/global-en/support/faq/usbdriver.html

[BArek]

W dniu wtorek, 30 lipca 2013 17:11:29 UTC+2 użytkownik jacek.r...@gmail.com napisał:
> Did you guys try to update OS to 1.1 on that Alcatel? Any success?:)

I have Alcatel (4012X-2ATBPL1-S40 from Polish T-Mobile distribution) running 1.1.0.0-prelease. Everything works fine exept phone calls - I'm able to receive phone calls and sms but I cannot make ones. In Settings: Call Settings, Cellular & Data, SIM security - Unknown SIM card state. Strange thing.

[BArek]

Some logs:


adb logcat -b radio
E/RILD ( 148): **RIL Daemon Started**
E/RILD ( 148): **RILd param count=1**
E/RILD ( 148): RIL_Init argc = 4 client = 0
E/RILPROXY( 145): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY( 145): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY( 145): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY( 145): Could not connect to rild socket, retrying: Connection refused
W/RILC ( 148): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILC ( 148): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 148): RIL_register: RIL version 6
E/RILC ( 148): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients = 1
E/RILC ( 148): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 148): responseSimStatus: A RilCardStatus_v6 or _v5 expected
E/RILC ( 148): responseSimStatus: A RilCardStatus_v6 or _v5 expected
E/RILC ( 148): responseSimStatus: A RilCardStatus_v6 or _v5 expected
E/RILC ( 148): responseSimStatus: A RilCardStatus_v6 or _v5 expected

adb logcat
I/Gecko ( 495): -*- RILContentHelper: Received message 'RIL:VoiceInfoChanged': {"connected":true,"emergencyCallsOnly":false,"roaming":false,"network":{"rilMessageType":"operatorchange","longName":"Polska Telefonia Cyfrowa (PTC)","shortName":"Era","mcc":"260","mnc":"02"},"cell":{"gsmLocationAreaCode":45071,"gsmCellId":1072191},"type":"gsm","signalStrength":-77,"relSignalStrength":58,"state":"registered"}
I/Gecko ( 144): -*- RILContentHelper: Received message 'RIL:VoiceInfoChanged': {"connected":true,"emergencyCallsOnly":false,"roaming":false,"network":{"rilMessageType":"operatorchange","longName":"Polska Telefonia Cyfrowa (PTC)","shortName":"Era","mcc":"260","mnc":"02"},"cell":{"gsmLocationAreaCode":45071,"gsmCellId":1072191},"type":"gsm","signalStrength":-77,"relSignalStrength":58,"state":"registered"}
I/Gecko ( 144): -*- RILContentHelper: Received message 'RIL:DataInfoChanged': {"connected":false,"emergencyCallsOnly":false,"roaming":false,"network":{"rilMessageType":"operatorchange","longName":"Polska Telefonia Cyfrowa (PTC)","shortName":"Era","mcc":"260","mnc":"02"},"cell":{"gsmLocationAreaCode":45071,"gsmCellId":1072191},"type":"umts","signalStrength":-77,"relSignalStrength":58,"state":"registered"}
I/Gecko ( 495): -*- RILContentHelper: Received message 'RIL:DataInfoChanged': {"connected":false,"emergencyCallsOnly":false,"roaming":false,"network":{"rilMessageType":"operatorchange","longName":"Polska Telefonia Cyfrowa (PTC)","shortName":"Era","mcc":"260","mnc":"02"},"cell":{"gsmLocationAreaCode":45071,"gsmCellId":1072191},"type":"umts","signalStrength":-77,"relSignalStrength":58,"state":"registered"}
I/Gecko ( 465): -*- RILContentHelper: Received message 'RIL:DataInfoChanged': {"connected":false,"emergencyCallsOnly":false,"roaming":false,"network":{"rilMessageType":"operatorchange","longName":"Polska Telefonia Cyfrowa (PTC)","shortName":"Era","mcc":"260","mnc":"02"},"cell":{"gsmLocationAreaCode":45071,"gsmCellId":1072191},"type":"umts","signalStrength":-77,"relSignalStrength":58,"state":"registered"}

[Jarek]

On Wednesday, August 7, 2013 12:47:37 AM UTC+2, BArek wrote:
> Everything works fine exept phone calls

> In Settings: Call Settings, Cellular & Data, SIM security - Unknown SIM card state.

Hi,

Have you managed to solve this problem?

I'm experiencing exactly the same issue on my OneTouch Fire running v1-train built yesterday. Build info:

Gaia: 6324c3b047aabee83ec7419803224e8edf07db7c
Gecko: 700373b45b3478fcabcd3361871956ca76b2b0fa
Platform Version: 18.1

Configured with: BRANCH=v1-train ./config.sh hamachi

Everything is fine except the phone calls. The message "Unknown SIM state" is displayed on the lock screen and in the settings.

I would appreciate any suggestions on how to fix it.

[Julien Wajsberg]

how did you flash the build ?

Regards,
--
Julien

[Jarek]

On Wednesday, September 11, 2013 9:40:57 AM UTC+2, Julien Wajsberg wrote:
> how did you flash the build ?

I just used ./flash.sh to flash the build. Everything went fine, the only failure was inability to set the time on device.

So just to make it clear, the exact commands I used were:

BRANCH=v1-train ./config.sh hamachi
./build.sh clean
./build.sh
./flash.sh

[Julien Wajsberg]

So, yeah, as far as I know, doing this will replace some of the
necessary binary blobs we have in the device (yes, that's sad, and I
really hope that will change).

So for now, you'll need to have a working phone, and then do:

./flash.sh gecko && ./flash.sh gaia

I don't know how you can go back to a working state though.

--
Julien

[Krzysztof Adamski]

W dniu 11.09.2013 11:13, Julien Wajsberg pisze:

> Le 11/09/2013 10:00, Jarek a écrit :

> So, yeah, as far as I know, doing this will replace some of the
> necessary binary blobs we have in the device (yes, that's sad, and I
> really hope that will change).

If someone could provide a list of those binary blobs, it would be
great. Not only this could let other people to backup them before
flashing, but it could make it much easier for Jarek to fix his phone.

[Mike Habicher]

On 13-09-11 11:34 AM, Krzysztof Adamski wrote:
> W dniu 11.09.2013 11:13, Julien Wajsberg pisze:
>> Le 11/09/2013 10:00, Jarek a écrit :

>> So, yeah, as far as I know, doing this will replace some of the
>> necessary binary blobs we have in the device (yes, that's sad, and I
>> really hope that will change).
>
> If someone could provide a list of those binary blobs, it would be
> great. Not only this could let other people to backup them before
> flashing, but it could make it much easier for Jarek to fix his phone.
>

And fix the build scripts.

--m.

[T.L.]

On 11.09.2013 11:42, Mike Habicher wrote:
> On 13-09-11 11:34 AM, Krzysztof Adamski wrote:
>> W dniu 11.09.2013 11:13, Julien Wajsberg pisze:
>>> Le 11/09/2013 10:00, Jarek a écrit :

>>> So, yeah, as far as I know, doing this will replace some of the
>>> necessary binary blobs we have in the device (yes, that's sad, and I
>>> really hope that will change).
>>
>> If someone could provide a list of those binary blobs, it would be
>> great. Not only this could let other people to backup them before
>> flashing, but it could make it much easier for Jarek to fix his phone.
>>
> And fix the build scripts.
>
> --m.
>

> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
I have a fresh Alcatel One Touch Fire from Poland here.

So if I knew what to pull from it, I'd be happy to provide that to Jarek
if it would help to get his phone working again.

Thomas

[Jarek]

I have a copy of the phone's original system partition, which was automatically created when I first executed ./config.sh. It's in backup-hamachi directory in the source tree.

However, I'm not sure if it contains the "binary blobs" that need to be recreated.

[T.L.]

Have you tried adb pushing the whole /system to the phone?

Thomas

On 11.09.2013 14:28, Jarek wrote:
> I have a copy of the phone's original system partition, which was automatically created when I first executed ./config.sh. It's in backup-hamachi directory in the source tree.
>
> However, I'm not sure if it contains the "binary blobs" that need to be recreated.

[Julien Wajsberg]

Le 11/09/2013 14:28, Jarek a écrit :
> I have a copy of the phone's original system partition, which was automatically created when I first executed ./config.sh. It's in backup-hamachi directory in the source tree.
>
> However, I'm not sure if it contains the "binary blobs" that need to be recreated.
>

I think it contains some but not all. That's the "fix the build scripts"
part in Mike's mail.

[Krzysztof Adamski]

Dnia 2013-09-11, o godz. 15:53:49
Julien Wajsberg <jwaj...@mozilla.com> napisał(a):

> Le 11/09/2013 14:28, Jarek a écrit :

> I think it contains some but not all. That's the "fix the build
> scripts" part in Mike's mail.
>

But when using 'flash.sh', is any "partition" other than 'userdata' and
'system' overwritten? Boot is not touched, that I know.

[Krzysztof Adamski]

Dnia 2013-09-11, o godz. 15:45:16
"T.L." <runda...@aol.de> napisał(a):

> Have you tried adb pushing the whole /system to the phone?

I believe that's not possible directly as adbd is running as "shell"
user. But there are workarounds like pushing it's content packaged
to /sdcard/ and then uncompressing it after using "su"...

[Eduardo González]

I have similar issues updating gonk on zte open. I'm using a commercial zte open rooted and ro.secure disabled, but fastboot method not work then i'm using CWM cli pushing system.img and userdata.img into sdcard, then mount system and userdata partition on temporary folders, delete whole content and unyaffs into folders (this method is same used by CWM recovery restoring system).

Rebooting the phone, you can see Gonk is running, you can enter into phone via adb shell and check RIL do not start phone services. I checked binary blobs is there, but rild do not start phone. Possibly is there another blobs forgotten


Edu

[Jarek]

On Wednesday, September 11, 2013 5:58:06 PM UTC+2, Krzysztof Adamski wrote:
> I believe that's not possible directly as adbd is running as "shell"
> user. But there are workarounds like pushing it's content packaged
> to /sdcard/ and then uncompressing it after using "su"...

As advised by Krzystof, I tried to copy something to the system partion via sdcard. In fact this "something" was the original rild binary, but this coudl be any file.

So I did the following:

adb push backup-hamachi/system/bin/rild /sdcard/rild
adb shell
shell@android:/ $ su
shell@android:/ #
shell@android:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
shell@android:/ # cat /sdcard/rild > /system/bin/rild

it worked just fine, so I guess it is possible to re-create the whole system partition.

Now I would appreciate a tip on how I can package the contents of the partition into a single file, such that I could then upackage it on the device.

[Krzysztof Adamski]

Dnia 2013-09-11, o godz. 12:36:45
Jarek <jarek...@gmail.com> napisał(a):

> Now I would appreciate a tip on how I can package the contents of the
> partition into a single file, such that I could then upackage it on
> the device.

You mean like compressing the whole folder on host machine to one file
and then ucompressing it on the phone? I don't think there's any such
tool available by default on FirefoxOS images. You could, however, put
busybox binary there, and then just use something like
"cd /system; bin/busybox tar -xzf file.tar.gz"

You don't have to install all the busybox symlinks, just place the
statically linked executable. If you don't have, e-mail me and I will
send you one.

[Naoki Hirata]

Just to note, I believe adb remount should work as well if you update
your adb.
It's a lot easier to remember than

mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system

Cheers,
Naoki

[Krzysztof Adamski]

W dniu 12.09.2013 02:03, Naoki Hirata pisze:

> Just to note, I believe adb remount should work as well if you update
> your adb.
> It's a lot easier to remember than
>

> mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system

But in order to use adb remount, adbd has to be running as root, not as
shell. It should be possible to force adb running as root without
touching /boot/ partition, however. Since we have access to /system/
parition, it's a matter of changing one of the binaries there to custom
compiled adbd that wont check ro.secure setting. Creating such binary is
easy and I can provide one if someone is interested.

If Alcatel did not change this, /init.b2g.rc should run
/system/bin/fakeperm binary as root while booting.

Something like:
adb push adbd-root /data/local/tmp/
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mv /data/local/tmp/adbd-root /system/bin/
# chmod 755 /data/local/tmp/adbd-root
# mv /system/bin/fakeperm /system/bin/fakeperm.org
# cat > /system/bin/fakeperm << _END
#!/system/bin/sh
/system/bin/adbd-root & /system/bin/fakeperm.org
_END
# chmod 755 /system/bin/fakeperm

should run adbd-root as root on startup. We have to _disable remote
debugging_ so that normal adbd is not started before our fake one. I
haven't tryied this as I don't have access to the hardware right now,
however.

Wow, that message ended up being quite long and I was mean to be only
degresion :)

[Naoki Hirata]

No worries. I found this quite educational. Thank you. ^_^

Naoki

On 9/12/13 9:59 AM, Krzysztof Adamski wrote:
> W dniu 12.09.2013 02:03, Naoki Hirata pisze:
>> Just to note, I believe adb remount should work as well if you update
>> your adb.
>> It's a lot easier to remember than
>>

>> mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
>

[Jarek]

On Wednesday, September 11, 2013 11:13:03 AM UTC+2, Julien Wajsberg wrote:
> So, yeah, as far as I know, doing this will replace some of the
> necessary binary blobs we have in the device (yes, that's sad, and I
> really hope that will change).

Julien (and others),

This problem is currently being discussed in
https://bugzilla.mozilla.org/show_bug.cgi?id=877757

If you could provide any thoughts that would help track down the cause of the problem, please comment on the issue in bugzilla.

Thanks.

[jerzyg...@gmail.com]

I cannot connect Alcatel OT Fire to Ubuntu nor Windows 7 PC. In Ubuntu, lsusb shows:

Bus 001 Device 004: ID 05c6:9026 Qualcomm, Inc.

I added the /etc/udev/rules.d/99-alcatel.rules file containing:

SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"

After restarting udev, adb devices shows empty list of devices.

In Windows 7, I have the following drivers installed:

Qualcomm HS-USB Android Modem 9026, ver. 2.0.8.7
Qualcomm HS-USB Diagnostics 9026, ver. 2.0.8.7
Qualcomm HS-USB NMEA 9026, ver. 2.0.8.7
Qualcomm Wireless HS-USB Ethernet Adapter 9026, ver. 1.0.6.5

But still adb devices shows empty list. What's wrong?

[Krzysztof Adamski]

W dniu 30.09.2013 11:03, jerzyg...@gmail.com pisze:

You have to enable remote debugging in your device's settings. You can
find it in Device Information > More Information > Developer. Double
check that it is enabled.

[jerzyg...@gmail.com]

But Alcatel One Touch Fire doesn't have this option. Any solutions?

[jerzyg...@gmail.com]

Sorry, Alcatel has this option, although hidden under a misleading name "Autor". I have enabled remote debugging and now it is recognized by adb.

Thanks!

[Alexandre Lissy]

Le 30/09/2013 20:07, jerzyg...@gmail.com a écrit :
> Sorry, Alcatel has this option, although hidden under a misleading name "Autor". I have enabled remote debugging and now it is recognized by adb.

« Author » ?

Can you screenshot this (power + home) ? I'd bet on a localization bug.

>
> Thanks!

[jerzyg...@gmail.com]

Yes. here is the screenshot: http://imm.io/1hfCz

[Alexandre Lissy]

Le 01/10/2013 14:33, jerzyg...@gmail.com a écrit :
> Yes. here is the screenshot: http://imm.io/1hfCz

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

This should mean « Developers », does it?

[Frederik Braun]

I don't speak your language but while we're trying to capture possible
l10n bugs -- does the part above it "Ustawienia dla programistów" make
senses though?

A more verbose string could be less confusing. Instead of showing the
word "Developer" (in whatever language), it could show "Developer options".

[Krzysztof Adamski]

W dniu 01.10.2013 15:20, Frederik Braun pisze:

> On 30.09.2013 20:07, jerzyg...@gmail.com wrote:

> I don't speak your language but while we're trying to capture
> possible l10n bugs -- does the part above it "Ustawienia dla
> programistów" make senses though?
>
> A more verbose string could be less confusing. Instead of showing
> the word "Developer" (in whatever language), it could show "Developer
> options".

"Ustawienia dla programistów" makes perfect sense. In direct translation
to English it is "Settings for programmers". So only "Autor" is confusing.

[Alexandre Lissy]

Le 01/10/2013 15:41, Krzysztof Adamski a écrit :
> W dniu 01.10.2013 15:20, Frederik Braun pisze:
>> On 30.09.2013 20:07, jerzyg...@gmail.com wrote:

>> I don't speak your language but while we're trying to capture
>> possible l10n bugs -- does the part above it "Ustawienia dla
>> programistów" make senses though?
>>
>> A more verbose string could be less confusing. Instead of showing
>> the word "Developer" (in whatever language), it could show "Developer
>> options".
>
> "Ustawienia dla programistów" makes perfect sense. In direct translation
> to English it is "Settings for programmers". So only "Autor" is confusing.

Reported in https://bugzilla.mozilla.org/show_bug.cgi?id=922629

Feel free to add yourself in Cc

[jerzyg...@gmail.com]

Thanks for fixing this bug.

however, I have a problem building B2G in Ubuntu 12.04 LTS x86_64 with gcc 4.6.3 and Android NDK r7, I am typing these commands:

~/B2G$ ./config.sh hamachi
(success)
~/B2G$ ./build.sh -j1 showcommands
(fail on this command)
target arm C: libc <= bionic/libc/bionic/pthread.c
prebuilt/linux-x86/ccache/ccache cc -I bionic/libc/stdlib -I bionic/libc/string -I bionic/libc/stdio -I bionic/libc -I out/target/product/hamachi/obj/SHARED_LIBRARIES/libc_intermediates -I dalvik/libnativehelper/include/nativehelper -isystem system/core/include -isystem hardware/libhardware/include -isystem hardware/libhardware_legacy/include -isystem hardware/ril/include -isystem dalvik/libnativehelper/include -isystem frameworks/base/include -isystem frameworks/base/opengl/include -isystem frameworks/base/native/include -isystem external/skia/include -isystem out/target/product/hamachi/obj/include -isystem bionic/libc/arch-arm/include -isystem bionic/libc/include -isystem bionic/libstdc++/include -isystem bionic/libc/kernel/common -isystem bionic/libc/kernel/arch-arm -isystem bionic/libm/include -isystem bionic/libm/include/arm -isystem bionic/libthread_db/include -c -fno-exceptions -Wno-multichar -msoft-float -fpic -ffunction-sections -fdata-sections -funwind-tables -fstack-protector -Wa,--noexecstack -Werror=format-security -fno-short-enums -march=armv7-a -mfloat-abi=softfp -mfpu=neon -include system/core/include/arch/linux-arm/AndroidConfig.h -I system/core/include/arch/linux-arm/ -Wno-unused-but-set-variable -fno-builtin-sin -fno-strict-volatile-bitfields -Wno-psabi -mthumb-interwork -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -DNDEBUG -g -Wstrict-aliasing=2 -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DNDEBUG -UDEBUG -O2 -fomit-frame-pointer -fstrict-aliasing -funswitch-loops -DWITH_ERRLIST -DANDROID_CHANGES -DUSE_LOCKS -DREALLOC_ZERO_BYTES_FREES -D_LIBC=1 -DSOFTFLOAT -DFLOATING_POINT -DINET6 -Ibionic/libc/private -DUSE_DL_PREFIX -DPOSIX_MISTAKE -DLOG_ON_HEAP_ERROR -DTM_GMTOFF=tm_gmtoff -DUSG_COMPAT=1 -fstrict-aliasing -DHAVE_ARM_TLS_REGISTER -DSPARROW_NEON_OPTIMIZATION -DCORTEX_CACHE_LINE_32 -DANDROID_SMP=1 -MD -MF out/target/product/hamachi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/pthread.d -o out/target/product/hamachi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/pthread.o bionic/libc/bionic/pthread.c
cc1: error: unrecognized command line option ‘-mfloat-abi=softfp’
cc1: error: unrecognized command line option ‘-mfpu=neon’
cc1: error: unrecognized command line option ‘-mthumb-interwork’
bionic/libc/bionic/pthread.c:1:0: error: bad value (armv7-a) for -march= switch
make: *** [out/target/product/hamachi/obj/SHARED_LIBRARIES/libc_intermediates/bionic/pthread.o] Error 1

Any ideas?

[Padmaja.M...@paradigmcreatives.com]

Hi,

Can you help us with the drivers for Alcatel One Touch Fire(4012A). We want to deploy an application

Thanks,
Padmaja

[Jan Jongboom]

What do you mean with drivers for One Touch Fire? If you're building for the hamachi target it'll pull the drivers of the phone.

[jerzyg...@gmail.com]

Finally I managed to successfully build the master branch for Alcatel OT Fire by using:
./config.sh hamachi && ./build.sh
If you have problems building it, here are some prebuilt images:
http://b2g.vegnux.org.ve

But how should I flash the device? When I run:
./flash.sh
I get this:
adbd cannot run as root in production builds
remount failed: Operation not permitted
push: /home/user/B2G/objdir-gecko/dist/b2g/dictionaries/en-US.aff -> /system/b2g/dictionaries/en-US.aff
failed to copy '/home/user/B2G/objdir-gecko/dist/b2g/dictionaries/en-US.aff' to '/system/b2g/dictionaries/en-US.aff': Read-only file system

When I run:
./flash.sh -f
then my Alcatel reboots into fastboot (white screen), but the command hangs on:
< waiting for device >
adb devices shows an empty list and lsusb shows 18d1:d00d (Google Inc.) instead of 05c6:9025 Qualcomm, Inc.

Could anybody write a comprehensive guide on how to flash the latest B2G to the stock Alcatel OT Fire? Thanks!

[Johannes Bauer]

Have you read the guide of Krzysztof Adamski? He describes how to get a
boot image from the stock image that can then be used to flash the phone
(when you have root). It can be found here:
http://k.japko.eu/alcatel-otf-hackers-guide-1.html

His guide is extremely helpful. However I currently have some trouble.
Actually just 5 minutes ago I bricked my phone and cannot revert to the
backup I've created using the guide :-( Still have to figure out what's
going on there.

Best of luck,
Joe

[Julien Wajsberg]

Le 01/10/2013 15:48, Alexandre Lissy a écrit :
> Le 01/10/2013 15:41, Krzysztof Adamski a écrit :
>> W dniu 01.10.2013 15:20, Frederik Braun pisze:
>>> On 30.09.2013 20:07, jerzyg...@gmail.com wrote:

>>> I don't speak your language but while we're trying to capture
>>> possible l10n bugs -- does the part above it "Ustawienia dla
>>> programistów" make senses though?
>>>
>>> A more verbose string could be less confusing. Instead of showing
>>> the word "Developer" (in whatever language), it could show "Developer
>>> options".
>> "Ustawienia dla programistów" makes perfect sense. In direct translation
>> to English it is "Settings for programmers". So only "Autor" is confusing.
> Reported in https://bugzilla.mozilla.org/show_bug.cgi?id=922629
>
> Feel free to add yourself in Cc
>

Seems to be fixed in v1.2, see the duped bug.

--
Julien

[marvin...@gmail.com]

Could you send me the ADB to reconnoitre it by usb?