FP2 bricked during update to 1.4.2 - no recovery mode

[Lomig]

@freibadschwimmer : thanks for your concern and help. I already tested what you’re suggesting.

@jaymanu: just tested your idea, trying to run the TWRP from the FP OS latest version. I’m getting an error when trying to boot either recovery.img and boot.img:

bassan:fp2-sibon-16.06.0-image-userdebug lomig$ fastboot devices
fbecf69c    fastboot
bassan:fp2-sibon-16.06.0-image-userdebug lomig$ ls -l
total 1234416
-rw-r--r--@ 1 lomig  staff         10 14 jui 19:06 android-info.txt
-rw-------@ 1 lomig  staff   14051328 31 déc  2008 boot.img
-rw-------@ 1 lomig  staff   12820796 31 déc  2008 cache.img
-rw-------@ 1 lomig  staff   15687680 31 déc  2008 recovery.img
-rw-------@ 1 lomig  staff  447111660 31 déc  2008 system.img
-rw-------@ 1 lomig  staff  142333212 31 déc  2008 userdata.img
bassan:fp2-sibon-16.06.0-image-userdebug lomig$ fastboot boot recovery.img 
downloading 'boot.img'...
OKAY [  0.481s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.482s
bassan:fp2-sibon-16.06.0-image-userdebug lomig$ fastboot boot boot.img 
downloading 'boot.img'...
OKAY [  0.431s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.432s
bassan:fp2-sibon-16.06.0-image-userdebug lomig$

[jaymanu]

Well that’s sad.

I guess that error message “remote: bootimage: incomplete or not signed” is not to be taken litterally, as 1/ FP2 bootloader is not locked and doesn’t enforce signing, and 2/ your file should be correct if you unzipped the official package.

Could you send us the result of a “fastboot getvar all” ? It might give us some more details about whats going on.

[Lomig]

I’m afraid this is not good news…

bassan:~ lomig$ fastboot getvar all
all: 
finished. total time: 0.001s
bassan:~ lomig$ 

I’m wondering whether I should try installing an older version like 1.1.7, just to see if there’s any difference. Also could try installing another OS like Sailfish ?

[freibadschwimmer]

You could try other versions.

Be aware that for installing Sailfish you will also need to have Android running first.

btw: Have you ever checked the checksum of your OS file that you downloaded? Maybe the file is corrupted?

[jaymanu]

Oops you are right, I’m also getting empty result with getvar all.
This feature might not be implemented in the FP2 bootloader, not an error specific to your phone.

[Lomig]

No boot with 1.1.7 either. There should be something bricked in the bootloading process, or the boot images are not correctly written, or…

@freibadschwimmer: I checked the md5 checksum for the two images that I tried to install, and they are correct.

[duboism]

I was about to update my FP2 but this thread is a bit scaring… Does this problem affect many users?

[freibadschwimmer]

@duboism

Does this problem affect many users?

Judging on this thread, I’d say four.

[duboism]

OK, I will try updating my phone then… Don’t hesitate to cross your fingers

[duboism]

Well apparently I was lucky (you can un-cross your fingers - thanks for that): the update went smooth and fast (30mn for download and installation). Kudos to the FP team and good luck for the people that had problems (I contacted FP return service for a DOA screen and they were great).