[RECOVERY] Unofficial TWRP for Elephone P9000 3.0.2-8

Search This thread

Jonny

Retired Forum Moderator
Jul 22, 2011
9,293
9,616
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



CHANGELOG for 3.0.2-0:

-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.

CHANGELOG for 3.0.1-0:

-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements

CHANGELOG for 3.0.0-0:

-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks

WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

CHANGELOG for 2.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

DOWNLOAD:
Unofficial TWRP 3.0.2-8 for Elephone P9000
Mirror 1

INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash

To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device

BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.

XDA:DevDB Information
[RECOVERY] Unofficial TWRP for Elephone P9000, Tool/Utility for the Elephone P9000

Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_elephone_p9000/tree/Omni


Version Information
Status: Stable
Current Stable Version: 3.0.2-8
Stable Release Date: 2016-08-24

Created 2016-07-26
Last Updated 2016-09-11
 

Jonny

Retired Forum Moderator
Jul 22, 2011
9,293
9,616
FAQ:

Attention ROM Devs - You need to update your ROM's updater-script to use the correct by-name parts for this recovery, the old M2 ported one had this:
Code:
/dev/block/platform/mtk-msdc.0/by-name

The correct by-name parts for the Elephone P9000 are:
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name


DEVICE-SPECIFIC CHANGELOGS:

3.0.2-8:

-Updated Kernel to an early version of my DarkSense kernel
-Possible fix for F2FS support (if it doesn't work we have a few theories as to why)

3.0.2-7:

-Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)

3.0.2-6:

-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue

3.0.2-5:

-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files

3.0.2-4:

-Fix USB-OTG Mounting

3.0.2-3:

-Use Toybox mount and grep

3.0.2-2:

-Fully built from source for Elephone P9000 - unlike the other one which was ported (repacked recovery.img) from the Elephone M2

Current TWRP "bugs" for Elephone P9000:

NONE :)
 
Last edited:

andy radical

Senior Member
Apr 15, 2016
71
12
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
 
  • Like
Reactions: Jonny

Jonny

Retired Forum Moderator
Jul 22, 2011
9,293
9,616
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..

Further info on the battery meter issue. I spoke to some of the guys over on the twrp freenode IRC channel and after a bit of experimentation it turns out that this is an issue with the way the kernel links to the battery level, some proprietary lib or bin is needed to help link them, at this moment in time I haven't a clue which one but I'll keep looking.
 
  • Like
Reactions: andy radical

Jonny

Retired Forum Moderator
Jul 22, 2011
9,293
9,616
3.0.2-5:

-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
 
Last edited:

Jtig

Senior Member
Oct 4, 2015
62
8
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.

What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
 

fatalhh

Member
Jul 14, 2016
31
2
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
 
Last edited:

fatalhh

Member
Jul 14, 2016
31
2
If you have installed this one then you have updated the recovery, unless you're asking something else?

Sent from my Elephone P9000 using XDA Labs
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
 

Jonny

Retired Forum Moderator
Jul 22, 2011
9,293
9,616
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.

Sent from my Elephone P9000 using XDA Labs
 

fatalhh

Member
Jul 14, 2016
31
2
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.

Sent from my Elephone P9000 using XDA Labs
Really confusing my friend.....I am newbie in the side of rooting....flashing....etc.....and reading a lot to learn.....everytime I flash something my stomach get butterflys.....like when you are in love:laugh::silly:
Thanks mate
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



    CHANGELOG for 3.0.2-0:

    -Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
    -Add Greek translation to some builds.

    CHANGELOG for 3.0.1-0:

    -support new CM 13.0 pattern encryption (sultanqasim)
    -fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
    -libtar updated to latest upstream and fixes (jcadduono)
    -fixes for loading custom themes (_that)
    -TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
    -translation updates - added Italian, Czech and Polish and significant updates to Dutch
    -progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
    -fix input box text display (Dees_Troy)
    -reboot option after zip install complete (bigbiff)
    -other mostly invisible bug fixes and improvements

    CHANGELOG for 3.0.0-0:

    -Completely new theme - Much more modern and much nicer looking (by z31s1g)
    -True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    -Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    -Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    -Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    -Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    -SuperSU prompt will no longer display if a Marshmallow ROM is installed
    -Update exfat, exfat fuse, dosfstools (by mdmower)
    -Update AOSP base to 6.0
    -A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    CHANGELOG for 2.8.7.0:

    -Initial ground work for software drawn keyboard (_that)
    -Fix handling of wiping internal storage on datamedia devices (xuefer)
    -Allow DataManager to set and read values from the system properties (xuefer)
    -Fix crash when taking screenshots on arm64 devices (xuefer)
    -Fix error message after an ORS script completes (Dees_Troy)
    -Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
    -Add system read only option – more details below (Dees_Troy)
    -Add resize2fs and GUI option to run resize2fs (Dees_Troy)
    -Fix crash loop caused by empty lines in AOSP recovery command file (_that)
    -Prevent duplicate page overlays such as multiple lock screens (mdmower)

    Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

    System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

    This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

    DOWNLOAD:
    Unofficial TWRP 3.0.2-8 for Elephone P9000
    Mirror 1

    INSTALLATION:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version above
    2) Reboot to TWRP
    3) Hit Install and tap the "Install Image" button in the lower right
    4) Browse to the location of the TWRP image on your device and select it
    5) Select recovery from the partition list and swipe to flash

    To install from SP Flash Tools:
    1) Download scatter file attached to this post
    2) Load scatter file into SPFT
    3) Plug USB cable into device and computer
    4) Press download in SPFT
    5) Reboot device

    BUGS:
    If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.

    XDA:DevDB Information
    [RECOVERY] Unofficial TWRP for Elephone P9000, Tool/Utility for the Elephone P9000

    Contributors
    Jonny
    Source Code: https://github.com/JonnyXDA/android_device_elephone_p9000/tree/Omni


    Version Information
    Status: Stable
    Current Stable Version: 3.0.2-8
    Stable Release Date: 2016-08-24

    Created 2016-07-26
    Last Updated 2016-09-11
    3
    FAQ:

    Attention ROM Devs - You need to update your ROM's updater-script to use the correct by-name parts for this recovery, the old M2 ported one had this:
    Code:
    /dev/block/platform/mtk-msdc.0/by-name

    The correct by-name parts for the Elephone P9000 are:
    Code:
    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name


    DEVICE-SPECIFIC CHANGELOGS:

    3.0.2-8:

    -Updated Kernel to an early version of my DarkSense kernel
    -Possible fix for F2FS support (if it doesn't work we have a few theories as to why)

    3.0.2-7:

    -Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)

    3.0.2-6:

    -Updated prebuilt kernel to 20160715 firmware version
    -Fixed MTP Mounting Issue

    3.0.2-5:

    -Updated prebuilt kernel to 20160628 firmware version
    -Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
    -Cleanup and remove useless files
    -Add Timezone data to TWRP, fixes some errors in recovery.log
    -Increase default brightness slightly, was a bit too dim before
    -Add ability to flash raw system.img files

    3.0.2-4:

    -Fix USB-OTG Mounting

    3.0.2-3:

    -Use Toybox mount and grep

    3.0.2-2:

    -Fully built from source for Elephone P9000 - unlike the other one which was ported (repacked recovery.img) from the Elephone M2

    Current TWRP "bugs" for Elephone P9000:

    NONE :)
    3
    3.0.2-7:

    -Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)

    Current TWRP "bugs" for Elephone P9000:

    -Issue with F2FS support
    3
    3.0.2-6:

    -Updated prebuilt kernel to 20160715 firmware version
    -Fixed MTP Mounting Issue
    2
    Thank you for your work.

    Does this mean we can flash Deepflex's CM ROM with this recovery as it used to be?

    Thanks
    Yes