[RECOVERY] fairphone FP1 (1st edition, repartitioned) CWM 6.0.5.0

chrmhoffmann · Jan 18, 2014

Code:

#include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 *
 * Submitting bug reports on nightly builds is the leading 
 * cause of male impotence.
 */

CyanogenMod/CWM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.

This is CWM for the fairphone FP1 (first edition, repartitioned as of FP cherry 1.6). As there are no custom roms (yet), this might not be very useful as of now

Do not install on any other device than the fairphone FP1 first edition - repartitioned as of FP cherry 1.6.

Note:
- The recovery has been compiled from Cyanogenmod 11.0
- device tree https://github.com/chrmhoffmann/android_device_fairphone_FP1

Before proceeding please make a complete backup for ALL partitions (especially the recovery with e.g. MTK Droid Root & Tools).

Thxs go to:
- bgcngm/mtk-tools
- the guys who make MTK droid root & tools
- keesj from fairphone and tmp_ who gave us working kernel

What works
- you can adb into the CWM
- backup and restore (boot, data, cache, system)
- install from .zip files not tested but should work

Installation
a) copy the recovery to the device: adb push cwm-fp1-kk.0.1.img /storage/sdcard1
b) adb into device: adb shell
c) flash to recovery: dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery

You could also try to use a tool like mtk mobile uncle tools (not tested by me): https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox

Download:

Changelog:
kk-0.1:
- update to kitkat compliant version 6.0.5.0
- self-compiled kernel

https://goo.im/devs/chrmhoffmann/cm-11.0/fp1/cwm-fp1-kk.0.1.img
md5sum b0081650e0e3677dc0c2f38ad76282e0

Older downloads:
Changelog:
v.0.2:
- rename to FP1 so that original zips should be flashable
v.0.1:
- initial version

Download

http://goo.im/devs/chrmhoffmann/fairphone/fp1/recovery-cwm-FP1-0.2.img
md5sum ba524ae0d59125809d0c08b59e664a65

Older download

http://goo.im/devs/chrmhoffmann/fairphone/fp1/recovery-cwm-fp1-0.1.img
md5sum 78a79f83bb2fc52b5bb6074df04d6892

asmaron · Jan 18, 2014

Very nice!!! Thanks for your hard work! :good:

Atm I don't have access to an FP1 but did anybody tried it already?

Regards,
Asmaron

MoreThanADev · Jan 18, 2014

asmaron said:
Very nice!!! Thanks for your hard work! :good:

Atm I don't have access to an FP1 but did anybody tried it already?

Regards,
Asmaron

Ofc we tried ^^ (athought i suppose chrmhoffmann tried first

).

I mean it installs and starts without any noticable issue. Thanks again chrmhoffmann !

MoreThanADev · Jan 19, 2014

Issue when installing zip

MoreThanADev said:
Ofc we tried ^^ (athought i suppose chrmhoffmann tried first ).

I mean it installs and starts without any noticable issue. Thanks again chrmhoffmann !

Actually, there seems to be some issue when installing zip. (Or maybe I did not used it the right way ?)

I tried to
install zip -> chose zip from sdcard -> Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip (downloaded from FP website) -> Yes
and it failled with some error message

"assert failed: getprop("ro.product.device") = "FP1" || getprop ("ro.build.product") = "FP1"
Error ... blablabla"

Is this normal that the file default.prop located at the / of the recovery contains different value from the file Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop downloaded from FP website ?

ie :

You should be able to reproduce this easely if you own a FairPhone. Still i can provide further log if you wish.

chrmhoffmann · Jan 19, 2014

MoreThanADev said:
Actually, there seems to be some issue when installing zip. (Or maybe I did not used it the right way ?)

I tried to
install zip -> chose zip from sdcard -> Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip (downloaded from FP website) -> Yes
and it failled with some error message

"assert failed: getprop("ro.product.device") = "FP1" || getprop ("ro.build.product") = "FP1"
Error ... blablabla"

Is this normal that the file default.prop located at the / of the recovery contains different value from the file Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop downloaded from FP website ?

ie :

/default.prop as beeing seen in recovery

...

ro.product.model=Fairphone FP1
ro.product.brand=Android
ro.product.name=cm_fp1
ro.product.device=fp1
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Fairphone

Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop

...

ro.product.model=FP1
ro.product.brand=FP
ro.product.name=FP1
ro.product.device=FP1
ro.product.board=FP1
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=FP1

You should be able to reproduce this easely if you own a FairPhone. Still i can provide further log if you wish.

Hmmm... You can test the installation by removing that assert from the zip file. It must be somewhere in META-INF/..../upgrade script.

I guess I could change the ro.product.device to FP1 [EDIT: argh that changes directory structures etc...]

Chris

chrmhoffmann · Jan 19, 2014

chrmhoffmann said:
Hmmm... You can test the installation by removing that assert from the zip file. It must be somewhere in META-INF/..../upgrade script.

I guess I could change the ro.product.device to FP1 [EDIT: argh that changes directory structures etc...]

Chris

Should be fixed now. Update recovery to 0.2. See op.

Chris

CheckItOut · Jul 31, 2014

FP1U

Does this version work with the new FP1U model with only a different chipset?

chrmhoffmann · Jul 31, 2014

Don't think so. Someone who has the new one has to create it (new kernel needed, I think they also have different partitions?).

Chris

chrmhoffmann · Aug 30, 2014

Updated version 6.0.5.0. See op.

Chris

_keesj · Aug 31, 2014

CheckItOut said:
Does this version work with the new FP1U model with only a different chipset?

I tested the install on FP1U and can confirm it works.

EDIT: I only tested the KitKat install.

drcyber · Sep 1, 2014

is this new recovery compatible with 1.6 FPOS (4.2.2) too? Or do i have to flash it back to the original one after testing?

simsalonaut · Sep 1, 2014

drcyber said:
is this new recovery compatible with 1.6 FPOS (4.2.2) too? Or do i have to flash it back to the original one after testing?

Can confirm: Just flashed the new recovery 6.0.5.0 to 1.6 FPOS (Stock Android 4.2.2), perfectly compatible. Thanks a ton, Chris!

drcyber · Sep 1, 2014

when i do dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery

i always get an error:

Code:

shell@android:/ $ dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
/dev/recovery: cannot open for write: Permission denied

did i forget something?

simsalonaut · Sep 1, 2014

Before entering the command, enter

Code:

su

to grant terminal superuser access.

drcyber · Sep 2, 2014

now the error is gone but how can i check if the new recovery is installed..

when i boot to recovery it looks like Stock-Recovery..

Code:

shell@android:/storage/sdcard1 $ su dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of
=/dev/recovery
d1/cwm-fp1-kk.0.1.img of=/dev/recovery                                        <

simsalonaut · Sep 2, 2014

drcyber said:
now the error is gone but how can i check if the new recovery is installed..

In Terminal, did you get a message confirming successful file transfer?
With Xposed & Gravity Box, I have a modified power button menu, including an option for rebooting to recovery.
My phone then rebooted into CWM recovery. Important: When rebooting from CWM recovery, don't forget to disable stock recovery, as the phone may attempt to return to it - CWM will ask you before shutting down.

Hope this helps!

haffenloher · Sep 2, 2014

drcyber said:

Code:

shell@android:/storage/sdcard1 $ su dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of
=/dev/recovery
d1/cwm-fp1-kk.0.1.img of=/dev/recovery                                        <

su and dd are two separate commands. Either you execute su first to gain root privileges and write your CWM image to /dev/recovery afterwards using dd, or you can use
su -c "single command you want to execute as root"
to, sort of, combine both.

drcyber · Sep 2, 2014

it worked now

thx

drcyber · Dec 10, 2014

Is it possible to update to 1.8 with this recovery?

everytime i tried with FP-Updater after reboot it says that the signature is unknown, and if i try "ok, install" the phone reboots and i still have 1.6

simsalonaut · Dec 10, 2014

Yeah, not working here either, not even with the original Recovery.img.
Update process completed, but as with you, I'm stuck on AOSP 4.2.2, not updating to AOSP. 4.2.2-11, even though some apps, like the Fairphone updater, are different. Completely messed up my phone, even after reinstalling GApps. I'll ask them to simply provide the image for the updates, and start fresh... Seems to be the only thing one can do.

[RECOVERY] fairphone FP1 (1st edition, repartitioned) CWM 6.0.5.0

Inactive Recognized Developer

Member

Member

Member

Inactive Recognized Developer

Inactive Recognized Developer

Member

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

Senior Member

Senior Member

Member

Similar threads

Top Liked Posts