Did you make a backup of your boot.img? If you did you can try to boot it with fastboot: first boot your phone into "fastboot mode" either by pressing the power and volume (down I think, but it might be up), or by running: $ adb reboot bootloader (when it's running in recovery mode) next boot the boot.img $ fastboot boot boot.img If your phone boots normally, you can flash that image using: $ fastboot flash boot boot.img If you did not make a backup, you could either build a new boot image, or download one form the internet (test it before flashing it).

I didn't backup my phone to boot.img.

Phone writes:

E:failed to mount/data(Invalid... E:Can't mount/data/recovery l E:Can't open /data/recovery.lo

I can only see only info on this size of wide display.

$ fastboot boot boot.img - provides to: < waiting for device > that's all

Can I use micro SD card for update? If yes in which form of data?

mexmode intallation:

hdmii@hdmii-X75VBP:~$ sudo ./linux.sh [sudo] password for hdmii:

• MexMod *
• Thanks for use our files :D *
• Visit us in www.mexmod.com *
• FirefoxOSv2.2byPenserbjorne *

y

• daemon not running. starting it now on port 5037 *
• daemon started successfully *

error: device not found erasing 'cache'... OKAY [ 0.091s] finished. total time: 0.091s sending 'boot' (6144 KB)... OKAY [ 0.203s] writing 'boot'... OKAY [ 0.222s] finished. total time: 0.424s sending 'userdata' (4 KB)... OKAY [ 0.003s] writing 'userdata'... OKAY [ 0.004s] finished. total time: 0.007s sending 'system' (180369 KB)... OKAY [ 5.795s] writing 'system'... OKAY [ 6.638s] finished. total time: 12.433s rebooting...

finished. total time: 0.001s hdmii@hdmii-X75VBP:~$

phone is rebooting into "Alcatel Touch Fire e" logo

Erik

The link you posted shows files for the alcatel one touch fire (4012X) while you posted that you have a 6015x which is an alcatel one touch fire E. I don't think you can use those files for the E version, which might explain why it isn't working anymore, luckily for you someone has backup images for the E version on github here: https://github.com/cookiengineer/alcatel-6015x . There is a boot.img in the backup folder, i suggest you try to boot that one, instructions are in the readme and my previous post.

adb server is out of date. killing...

• daemon started successfully *

error: device not found < waiting for device >

hdmii@hdmii-X75VBP:~$ adb reboot bootloader error: device not found hdmii@hdmii-X75VBP:~$

hdmii@hdmii-X75VBP:~$ cat /etc/udev/rules.d/android.rules; cat: /etc/udev/rules.d/android.rules: Adresár alebo súbor neexistuje hdmii@hdmii-X75VBP:~$ SUBSYSTEM="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev" ATTR{idVendor}==05c6,: command not found hdmii@hdmii-X75VBP:~$

the only way to communicate with phone is via adb sideload

hdmii@hdmii-X75VBP:~$ adb devices

• daemon not running. starting it now on port 5037 *
• daemon started successfully *

List of devices attached 6292e056 sideload

but,

E:footer is wrong E:signature verification failed Instalation aborted

files I sideload are from:

https://github.com/cookiengineer/alcatel-6015x/tree/master/backup

Any idea?

Can you put the phone in fastboot (bootloader) mode (power + volume up or down)? The phobe should turn on and stop at the alcatel logo, if it instead shows the recovery menu try again with the other volume key. When in fastboot mode you should be able to access the phobe using the fastboot comnand (adb wont work). Check if it worked using "fastboot devices" If it returns your phone you might be able to boot the boot.img using "fastboot boot boot.img". You cant sideload a boot.img ( I think) which is why it returns those errors.

little bit better, phone still in alcatel logo

hdmii@hdmii-X75VBP:~$ fastboot devices 6292e056 fastboot hdmii@hdmii-X75VBP:~$ fastboot boot boot.img downloading 'boot.img'... OKAY [ 0.485s] booting... OKAY [ 0.068s] finished. total time: 0.554s hdmii@hdmii-X75VBP:~$ fastboot flash boot boot.img < waiting for device > target reported max download size of 301989888 bytes sending 'boot' (15360 KB)... OKAY [ 0.499s] writing 'boot'... OKAY [ 0.557s] finished. total time: 1.056s hdmii@hdmii-X75VBP:~$ fastboot flash modem firmware.img target reported max download size of 301989888 bytes sending 'modem' (65536 KB)... OKAY [ 2.063s] writing 'modem'... OKAY [ 2.414s] finished. total time: 4.477s hdmii@hdmii-X75VBP:~$ fastboot flash recovery recovery.img target reported max download size of 301989888 bytes sending 'recovery' (15360 KB)... OKAY [ 0.488s] writing 'recovery'... OKAY [ 0.566s] finished. total time: 1.054s hdmii@hdmii-X75VBP:~$ fastboot reboot rebooting...

finished. total time: 0.001s

what I am doing wrong?

The boot.img seems to be booting oke, you might need a new system image aswell if it isn't starting normally at this stage. I'm not sure where you could find one, maybe someone else knows? You could always build them yourself using the guide on the firefoxos website, but i haven't done that myself so i probably won't be able to help you with that. Also you normally need to put the phone back into fastboot mode before flashing the image. But if it worked like this, it is probably an indication that it went back into fastboot mode after booting, which means that there is something wrong with what happens after booting. Which makes me think your boot.img isn't compatible with the system.img. Which FFOS version where you running when your phone was still working?

ffos 2.0

Try this boot.img: https://www.dropbox.com/s/1qq10ie52v6ecnf/boot.img?dl=0 I extracted that from my own device, so it should be working for ffos 2.0. If it doesn't work you probably have something else wrong on your phone, you might need a new system.img, but you'll probably have to build that yourself.

thanks for help, I try to build something