Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
New Device, Alcatel OneTouch Fire E (6015X)
712 views
Skip to first unread message
Daniel Wacker
Aug 19, 2014, 5:44:31 AM8/19/14
to mozilla...@lists.mozilla.org
Hi, I just got a brand-new OneTouch Fire E. It's running 1.3.0 and I want to upgrade to 1.4 or 2.0 but I'm afraid of bricking.
lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
Fabrice Desré
Aug 19, 2014, 1:57:08 PM8/19/14
to Daniel Wacker, mozilla...@lists.mozilla.org
Hi Daniel,
On 08/19/2014 02:44 AM, Daniel Wacker wrote:
> Hi, I just got a brand-new OneTouch Fire E. It's running 1.3.0 and I want to upgrade to 1.4 or 2.0 but I'm afraid of bricking.
>
> lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
No, an hamachi build will not work. TCL usually publishes their source
code on sourceforge, but I can't find a link right now...
> For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
Enabling remote debugging in the settings app will give you adb access.
Fabrice
--
Fabrice Desr�
b2g team
Mozilla Corporation
On 08/19/2014 02:44 AM, Daniel Wacker wrote:
> Hi, I just got a brand-new OneTouch Fire E. It's running 1.3.0 and I want to upgrade to 1.4 or 2.0 but I'm afraid of bricking.
>
> lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
code on sourceforge, but I can't find a link right now...
> For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
Fabrice
--
Fabrice Desr�
b2g team
Mozilla Corporation
Daniel Wacker
Aug 19, 2014, 6:44:10 PM8/19/14
to Fabrice Desré, mozilla...@lists.mozilla.org
Hi, thanks for the info!
>> Hi, I just got a brand-new OneTouch Fire E. It's running 1.3.0 and I want to upgrade to 1.4 or 2.0 but I'm afraid of bricking.
>>
>> lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
>
> No, an hamachi build will not work. TCL usually publishes their source
> code on sourceforge, but I can't find a link right now...
I think you mean this URL:
http://sourceforge.net/projects/alcatel/files/
Unfortunately, no files for the OneTouch Fire E 6015X, yet. So at first I issued a request to the Alcatel support and also to the TCL guy.
Then I got somebody of the OneTouch support team on the phone saying that in 1-2 months, there will be more infos / files available for the phone.
>> For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
>
> Enabling remote debugging in the settings app will give you adb access.
Too late, already bricked :(
Opening it up, I saw the same processor (Snapdragon 200, MSM8210) that is inside of the Flame and the ZTE Open C, so I tried their images.
Actually, using the Flame Image, the phone seems to be booting up, but there's no graphics output. Black screen only.
So I just ordered another one of these awesome phones, maybe I can rescue the first one by transferring images. Which tools would be suitable for that task?
Kind regards to all the b2g team, doing a great job in enabling a truly open mobile web!
Daniel
>> Hi, I just got a brand-new OneTouch Fire E. It's running 1.3.0 and I want to upgrade to 1.4 or 2.0 but I'm afraid of bricking.
>>
>> lsusb shows 'Qualcomm' so I think there's a Snapdragon inside. Will the hamachi kernel config / precompiled hamachi images work?
>
> No, an hamachi build will not work. TCL usually publishes their source
> code on sourceforge, but I can't find a link right now...
http://sourceforge.net/projects/alcatel/files/
Unfortunately, no files for the OneTouch Fire E 6015X, yet. So at first I issued a request to the Alcatel support and also to the TCL guy.
Then I got somebody of the OneTouch support team on the phone saying that in 1-2 months, there will be more infos / files available for the phone.
>> For now, only fastboot works. How can I get adb access to the device, in order to do system backups?
>
> Enabling remote debugging in the settings app will give you adb access.
Opening it up, I saw the same processor (Snapdragon 200, MSM8210) that is inside of the Flame and the ZTE Open C, so I tried their images.
Actually, using the Flame Image, the phone seems to be booting up, but there's no graphics output. Black screen only.
So I just ordered another one of these awesome phones, maybe I can rescue the first one by transferring images. Which tools would be suitable for that task?
Kind regards to all the b2g team, doing a great job in enabling a truly open mobile web!
Daniel
Gabriele Svelto
Aug 20, 2014, 4:55:33 PM8/20/14
to Daniel Wacker, Fabrice Desré, mozilla...@lists.mozilla.org
On 20/08/2014 00:44, Daniel Wacker wrote:
> So I just ordered another one of these awesome phones, maybe I can rescue the first one by transferring images. Which tools would be suitable for that task?
You can backup the partitions from a working phone using 'dd' to dump
> So I just ordered another one of these awesome phones, maybe I can rescue the first one by transferring images. Which tools would be suitable for that task?
them (you can find the relevant devices under /dev/block) and then use
fastboot to flash them on the bricked phone (provided that fastboot
still works).
Gabriele
Gabriele Svelto
Nov 10, 2014, 8:43:24 AM11/10/14
to Daniel Wacker, Fabrice Desré, mozilla...@lists.mozilla.org
On 10/11/2014 14:29, Daniel Wacker wrote:
> Thanks for the info! I am familiar with dd, but this would require me to have adb root access.
> How to get adb root access on the OT-6015X?
To read the partitions (in order to back them up) you shouldn't need
root access, regular adb access should be enough. Run 'adb shell mount'
to see which partitions are available and where they're mounted. You
should backup 'system' at the very least if you want to experiment. You
might also want to check for /dev/block/platform/msm_sdcc.1/by-name or
something similar under /dev to see if you have functional names for all
the phone's partitions if you want to back all of them up. Once you
found the partitions you're interested in just us 'dd' to copy them to
an external sd-card. You will need to use fastboot to flash them back
later so check if you can enter fastboot on your device (by some
power-on key combination).
> By the way, after several months now, Alcatel/TCL still doesn't offer source files for the device, though they are in my understanding legally required to!
> see http://sourceforge.net/projects/alcatel/files/
>
> What is your opinion on this at mozilla?
IIRC until now Alcatel has always provided their sources. Not sure how
timely they were with that though.
Gabriele
> Thanks for the info! I am familiar with dd, but this would require me to have adb root access.
> How to get adb root access on the OT-6015X?
To read the partitions (in order to back them up) you shouldn't need
root access, regular adb access should be enough. Run 'adb shell mount'
to see which partitions are available and where they're mounted. You
should backup 'system' at the very least if you want to experiment. You
might also want to check for /dev/block/platform/msm_sdcc.1/by-name or
something similar under /dev to see if you have functional names for all
the phone's partitions if you want to back all of them up. Once you
found the partitions you're interested in just us 'dd' to copy them to
an external sd-card. You will need to use fastboot to flash them back
later so check if you can enter fastboot on your device (by some
power-on key combination).
> By the way, after several months now, Alcatel/TCL still doesn't offer source files for the device, though they are in my understanding legally required to!
> see http://sourceforge.net/projects/alcatel/files/
>
> What is your opinion on this at mozilla?
IIRC until now Alcatel has always provided their sources. Not sure how
timely they were with that though.
Gabriele
Gabriele Svelto
Nov 10, 2014, 9:35:32 AM11/10/14
to Daniel Wacker, Fabrice Desré, mozilla...@lists.mozilla.org
On 10/11/2014 15:16, Daniel Wacker wrote:
> This is exactly hat I was trying to do, but sadly I'm coming upon a closed/locked system:
That's locked down a lot more then what I was expecting :( Have you
found a way to enter fastboot mode somehow?
Gabriele
> This is exactly hat I was trying to do, but sadly I'm coming upon a closed/locked system:
That's locked down a lot more then what I was expecting :( Have you
found a way to enter fastboot mode somehow?
Gabriele
Gabriele Svelto
Nov 11, 2014, 4:35:38 AM11/11/14
to Daniel Wacker, Fabrice Desré, mozilla...@lists.mozilla.org
On 10/11/2014 15:51, Daniel Wacker wrote:
> Yes, fastboot is working after holding volume down on reboot.
> But what is it good for without having any kernel image (or source) to flash or boot?
Good point. Though you should be able to flash the system image this way
which might allow you to replace gecko/gaia.
> Since the ZTE Open C has a similar chipset, the device seems to boot using their images.
> Downside: Black screen only. Apparently it has a different graphics device.
It could also be due to incompatible graphics binary blobs.
> Heck it's not even documented which kernel configuration to use in case alcatel would publish anything:
> flo, otoro, unagi, inari, keon, peak, leo, hamachi, helix, wasabi, fugu, tarako, tara, dolphin, pandaboard, vixen, flatfish, ... <-- which one?
I don't think we have an entry for it yet. Is it a JB-based device? You
might build a working gecko using the 'flame' device (note, not the
'flame-kk'). Naturally, if you build this way don't try to flash
anything else besides gecko/gaia.
Gabriele
> Yes, fastboot is working after holding volume down on reboot.
> But what is it good for without having any kernel image (or source) to flash or boot?
Good point. Though you should be able to flash the system image this way
which might allow you to replace gecko/gaia.
> Since the ZTE Open C has a similar chipset, the device seems to boot using their images.
> Downside: Black screen only. Apparently it has a different graphics device.
It could also be due to incompatible graphics binary blobs.
> Heck it's not even documented which kernel configuration to use in case alcatel would publish anything:
> flo, otoro, unagi, inari, keon, peak, leo, hamachi, helix, wasabi, fugu, tarako, tara, dolphin, pandaboard, vixen, flatfish, ... <-- which one?
I don't think we have an entry for it yet. Is it a JB-based device? You
might build a working gecko using the 'flame' device (note, not the
'flame-kk'). Naturally, if you build this way don't try to flash
anything else besides gecko/gaia.
Gabriele
André Jaenisch
Nov 11, 2014, 8:19:11 AM11/11/14
to mozilla...@lists.mozilla.org
Am 2014-11-10 15:16, schrieb Daniel Wacker:
> This is exactly hat I was trying to do, but sadly I'm coming upon a
> closed/locked system:
>
> # mount
> This is exactly hat I was trying to do, but sadly I'm coming upon a
> closed/locked system:
>
> ...
> /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ...
> ...
> /dev/block/vold/259:1 /storage/sdcard0 vfat ...
> /dev/block/vold/179:65 /storage/sdcard1 vfat ...
>
> # ls -l
> lrwxrwxrwx root root 1970-01-01 01:00
> /dev/block/platform/msm_sdcc.1/by-name/system -> /dev/block/mmcblk0p12
> brw------- root root 179, 12 1970-01-01 01:00
> /dev/block/mmcblk0p12
>
> Also, no permission to access the external sdcard:
>
> # ls -l /dev/block/vold/
> opendir failed, Permission denied
>
> # ls -l /dev/block/vold/259:1
> /dev/block/vold/259:1: Permission denied
>
> # ls -l /storage
> dr-xrwx--- system sdcard_rw 1970-01-01 01:00 sdcard0
> dr-xrwx--- system media_rw 1970-01-01 01:00 sdcard1
>
> # ls -l /storage/sdcard1
> opendir failed, Permission denied
Same holds true for Alcatel OneTouch Fire (aka Hamachi).
Not accessible without root :-(
Gabriele Svelto
Nov 11, 2014, 9:01:46 AM11/11/14
to Daniel Wacker, mozilla...@lists.mozilla.org
On 11/11/2014 12:32, Daniel Wacker wrote:
> Sounds good, but my main problem now is that I have two devices one of which is bricked (since I accidentally did a "fastboot flash" instead of a "fastboot boot").
>
> So I need a way to get the boot image off the working phone, on which I don't have any permission to.
Without the sources and without access to the partitions via adb I'm not
aware of any way to recover the boot partition. The only thing that
comes to mind is that Alcatel has a Windows tool for installing offline
updates (presumably via fastboot):
http://www.alcatelonetouch.com/global-en/support/download/fire_e.html
Maybe you'll be able to recover the standard image using that. I'll also
try to see what can be done for making Alcatel release their sources.
> JB as in Jelly Bean? I think yes. At least the entries in /system/build.prop point to Android 4.3:
Yes, then you'll need a gecko/gaia build for a JB device.
Gabriele
> Sounds good, but my main problem now is that I have two devices one of which is bricked (since I accidentally did a "fastboot flash" instead of a "fastboot boot").
>
> So I need a way to get the boot image off the working phone, on which I don't have any permission to.
Without the sources and without access to the partitions via adb I'm not
aware of any way to recover the boot partition. The only thing that
comes to mind is that Alcatel has a Windows tool for installing offline
updates (presumably via fastboot):
http://www.alcatelonetouch.com/global-en/support/download/fire_e.html
Maybe you'll be able to recover the standard image using that. I'll also
try to see what can be done for making Alcatel release their sources.
> JB as in Jelly Bean? I think yes. At least the entries in /system/build.prop point to Android 4.3:
Yes, then you'll need a gecko/gaia build for a JB device.
Gabriele
Max
Nov 16, 2014, 11:39:16 AM11/16/14
to dev...@lists.mozilla.org
> Now is my device in authorized service before my fight for
> root acces & ffos 2.0 begin again.
did you guys have any success flashing it with the ffos 2.0 so far?
> root acces & ffos 2.0 begin again.
did you guys have any success flashing it with the ffos 2.0 so far?
Gabriele Svelto
Feb 26, 2015, 5:19:10 PM2/26/15
to kissingwi...@gmail.com, mozilla...@lists.mozilla.org
On 15/02/2015 21:56, kissingwi...@gmail.com wrote:
> Anyone has some luck with this device so far? I'm in the desperate need of a recovery image as I tried to upgrade to 2.x as well but all I achieved is a pitch black, non-working screen so I'm trying to find any original image I could fastboot back to use the phone.
Alcatel has a windows-only tool for devices available in their support
pages. IIRC it's used to allow users to flash the updates they
distribute so it might also be able to restore the phone to the stock
configuration. It's definitely worth a try.
Gabriele
> Anyone has some luck with this device so far? I'm in the desperate need of a recovery image as I tried to upgrade to 2.x as well but all I achieved is a pitch black, non-working screen so I'm trying to find any original image I could fastboot back to use the phone.
Alcatel has a windows-only tool for devices available in their support
pages. IIRC it's used to allow users to flash the updates they
distribute so it might also be able to restore the phone to the stock
configuration. It's definitely worth a try.
Gabriele
0 new messages