[RECOVERY][Nokia X] TWRP 2.7.0.2 touch recovery [2014-04-16]

Search This thread

scumpicule

Senior Member
Jun 28, 2012
431
463
Hunedoara
Hello

Thanks for the twrp !But i don't understand what to do with the patch 'twrp_normandy.patch' ? Can you explain me a little please because i really don't understand...

Thanks in advance

And to install i do :

Code:
adb reboot bootloader
fastboot -i 0x0421 flash recovery TWRP-2.7.0.1-normandy.img

It's correct procedure ? I precise i'm on windows system ;)

In normal time to flash a recovery i do only

Code:
adb reboot bootloader
fastboot flash recovery TWRP-2.7.0.1-normandy.img

What's the "-i 0x0421" ?
 
Last edited:

LluisAzm

Senior Member
Apr 19, 2008
103
12
Barcelona
I use Linux. But I have a thread in general with the Nokia drivers

Sent from my DROID RAZR HD using Tapatalk


Thanks,

I'm installing Ubuntu at VirtualBox, but it's strange, you can see at screenshot. When I connect my Galaxy S adb devices find it correctly, when I connect Nokia X with all drivers Ok it doesn't find it...

Edit: Working correctly, reboot and create the ini file even it not exist!
 

Attachments

  • adb.png
    adb.png
    141.5 KB · Views: 298
Last edited:

dhacker29

Inactive Recognized Developer
May 27, 2011
1,802
3,819
Millsboro, DE
Hello

Thanks for the twrp !But i don't understand what to do with the patch 'twrp_normandy.patch' ? Can you explain me a little please because i really don't understand...

Thanks in advance

And to install i do :

Code:
adb reboot bootloader
fastboot -i 0x0421 flash recovery TWRP-2.7.0.1-normandy.img

It's correct procedure ? I precise i'm on windows system ;)

In normal time to flash a recovery i do only

Code:
adb reboot bootloader
fastboot flash recovery TWRP-2.7.0.1-normandy.img

What's the "-i 0x0421" ?

Nokia's USB id is not yet incorporated into adb and fastboot so you have to specify it so it can find the device.
 
  • Like
Reactions: scumpicule

AngSanley

Senior Member
Apr 21, 2012
981
1,256
Medan, Indonesia
Nokia's USB id is not yet incorporated into adb and fastboot so you have to specify it so it can find the device.
If I open up Device Manager and install ADB and Fastboot drivers there? Will it recognized?

---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------

same with u :crying:
do this with fastboot in the same folder with twrp

Code:
adb reboot bootloader
fastboot -i 0x0421 flash recovery TWRP-2.7.0.1-normandy.img
 

hyperX1134

Member
Apr 18, 2015
40
18
Broken download link!

The download link for TWRP-2.7.0.2-normandy.img has broken so anyone needing this file just PM me and I will post it here! :eek:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 28
    TWRP 2.7.0.2 for Nokia X (normandy)

    This is a fully working version of the latest TWRP.

    All sources can be found at https://github.com/dhacker29?tab=repositories

    I built this in CyanogenMod cm-10.0 sources by repo init from the jellybean branch and adding https://github.com/omnirom/android_bootable_recovery to my local manifest and removing bootable/recovery.

    The following patch is required to bootable/recovery twrp_normandy.patch
    Also in device/nokia/normandy/BoardConfig.mk
    Code:
     BOARD_HAS_NO_SELECT_BUTTON := true
    -BOARD_CUSTOM_GRAPHICS := ../../../device/nokia/normandy/recovery/graphics.c
    +#BOARD_CUSTOM_GRAPHICS := ../../../device/nokia/normandy/recovery/graphics.c
     TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

    To build in the CyanogenMod cm-11.0 branch you just need this one patch to bootable/recovery:
    Code:
    diff --git a/minuitwrp/Android.mk b/minuitwrp/Android.mk
    index 4ee59d0..8e47a2b 100644
    --- a/minuitwrp/Android.mk
    +++ b/minuitwrp/Android.mk
    @@ -10,6 +10,9 @@ else
         LOCAL_SRC_FILES += graphics.c
     endif
     
    +LOCAL_ADDITIONAL_DEPENDENCIES := $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr
    +LOCAL_C_INCLUDES += $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr/include
    +
     ifeq ($(TW_TARGET_USES_QCOM_BSP), true)
       LOCAL_CFLAGS += -DMSM_BSP
       ifeq ($(TARGET_PREBUILT_KERNEL),)

    The rest of the post is shamlessly kanged from Dees Troy's official TWRP posts

    Team Win Recovery Project 2.x, or twrp2 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 2.7.0.2:
    Enabled selinux support

    CHANGELOG for 2.7.0.1:
    Fixed graphics glitch and reboot issues

    CHANGELOG for 2.7.0.0:
    -Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
    -Allow sideloading from /tmp on encrypted devices
    -Check for a crypto footer before asking for a password to prevent user confusion
    -Additional checks for validity to auto generated backup names
    -Text wrap in the console output
    -Proper caps lock support in the keyboard
    -Mouse support via USB OTG for devices with a broken digitizer
    -Improve scanning of storage locations for OpenRecoveryScript
    -Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
    -Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
    -Update SuperSU to 1.93 and improve installation process
    -Added selinux contexts restoration to fix permissions
    -Load RTC offset on Qualcomm devices to fix the date/time in recovery
    -USB Mass Storage fixes Add SELinux support checking
    -Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
    -Add 4.4 decrypt support
    -Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
    -Various SELinux fixes and bug fixes

    Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.


    DOWNLOAD: TWRP-2.7.0.2-normandy.img

    BUGS:
    If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.
    3
    don't have a github account so posting the issue here.... trying to backup the data partition crashes the recovery..... then it jusst keeps rebooting into recovery...

    Is there enough actual space on your internal storage to back up? I had to use sdcard to have enough and backup worked fine for me.
    2
    the link is kind of broken i guess it takes me to rombitch.com....i think you should make another mirror
    Download Here
    Or Newer Version Here
    2
    You sir are a champ! Now all we need is CM11 and this will be the best phone in it's price category

    Sent from my Nexus 5 using XDA Premium 4 mobile app

    I'm aiming for cm-10.2 to start as that's the last official support from Qualcomm and cm for msm7627a devices. Once that's stable I'll attempt cm-11 as unofficial.

    http://t.co/xdnSHnJ2eF


    Sent from my DROID RAZR HD using Tapatalk
    2
    Close to having a fully working caf/aosp build. CM will be a bit longer

    https://twitter.com/dhacker29/status/453133632136163328/photo/1