Jump to content

[RECOVERY] [TWRP 2.7] Touch Recovery [martinoff]


Guest dakok

Recommended Posts

TWRP 2.7.0.0 translated / modded by martinoff

Download

 

 

Martinoff:

Warning:

PLEASE MAKE A NANDROID BACKUP WITH NVRAM INCLUDED

I dont have to tell you that you MUST have a backup with Mtk-Droid-tool also

 

Now i need some feedback from the brave men here

I have tested in my phone and it is working ok

The original TWRP is by SevenSummer from ydss forum.

 

 

Official 2.7.0.0 changelog:

TeamWin:


What's new in 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
  • 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 AOSP 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.

 

 

Screenshots (first release):

 

8ceh7rs.jpgxjkphyI.jpgEo3zApi.jpgv5COJCJ.jpg

9sYDgKr.jpgvU2csCv.jpgTVyh2GN.jpg

 

Martinoff:

I have changed the icons with the stock

in the top bar on the right there is same space if anyone want to add something, the coolpad logo maybe....

 

3TCbXFr.png

 

here is the png

TJkP2xA.jpg


 

and this is the preview logo

frM4gqR.jpg


 

you can mess with it and make some nice logos and i will repack them

please add the TeamWin letters somehow because that team make a awesome work and they deserve it   ;)  

 

i updated the link so you can redownload it

 

 

 
 
Edited by dakok
Link to comment
Share on other sites

Guest misha124
Microsoft Windows [Version 6.1.7601]
© Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
 
C:\Users\Misha>adb shell cat /proc/emmc
partno:    start_sect   nr_sects  partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 00018d00 00003000 "sec_ro"
emmc_p5: 00020500 00000800 "yl_params"
emmc_p6: 00020d00 00008000 "autobak"
emmc_p7: 00028d00 0000a000 "panic"
emmc_p8: 00038000 00280000 "android"
emmc_p9: 002b8000 00040000 "cache"
emmc_p10: 002f8000 00b8d800 "usrdata"
 
C:\Users\Misha>
Link to comment
Share on other sites

Guest misha124

is that from recovery ?

and place here inside code tag the output of

adb shell mount

because that will be long one download consoleZ so that will be readable 

Microsoft Windows [Version 6.1.7601]
© Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
 
C:\Users\Misha\Downloads\ConsoleZ.x64.1.11.0.14175>adb shell mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p9 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p10 on /emmc type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
 
C:\Users\Misha\Downloads\ConsoleZ.x64.1.11.0.14175>
Link to comment
Share on other sites

Guest misha124

is that from recovery ?

and place here inside code tag the output of

adb shell mount

because that will be long one download consoleZ so that will be readable 

I just do not understand the console, do not know what you need to make you a screenshot of the error

Link to comment
Share on other sites

Guest martinoff

can you confirm it sees SD card with correct size? I remember a past version were both internal and sd card had the same size!

yeap

 

NzA1Vpi.png

 

 

@misha124 i can see that your sd is mounted with wright permissions (rw=read-write) so i don't really know what is wrong in your recovery

pleace download it again, not any one you have allready and try again

test also with twrp 2.6 and if that fail again check your sd for problems (i/o write errors)

if the 2.6 work, i am sorry mate, stick with it

i cant change anything in recovery as it is binary and not compiled by me

 

ps: consoleZ is a better software than native cmd of windows, here it is https://github.com/cbucher/console

Edited by martinoff
Link to comment
Share on other sites

Guest misha124

Touch Backup Name:

and rename backup to something simple, without spaces, for example:

MyGoodRom

 

Then touch at Storage:

and select where to save backup

 

8ceh7rs.jpg

thank you very much dakok)))) your advice helped much) it was all in the name

Link to comment
Share on other sites

Guest martinoff

i am glad you did it  ;)

 

maybe twrp 2.6 have set permissions in that folder and the new 2.7 cant write there, so rename it and try again with autoname

and don't be sorry, that was a nice feedback for other members maybe 

Link to comment
Share on other sites

Thanks martinoff ( & dakok of course ) :-)

 

Has anyone tested restore backups using this version?

Including backups made with previous TWRP / CWM version, especially of 4.2.2 ROMs - I see "dropped support for older devices" mentioning that selinux contexts support is needed for KitKat ROMs in Changelog. Doesn't it mean that support for 4.2.2 ROMs could have been dropped in TWRP 2.7?

Link to comment
Share on other sites

Guest martinoff

Yeap, i have tested it so many times that i will kill the flash of coolpad :p

 

it can restore eavrything from TWRP 2.4, i dont tested it with cwm backups (didnt know that it can do such things, really ?)

it can flash everything like patches,apks,supeSU etc

it refuse two or three times to flash some 4.2.2 roms (jonzalvos was one of them) but i thing that this has something to do with the mount point

other that that ......

well you tell me guys :p

Link to comment
Share on other sites

Guest mindtrapper

Yeap, i have tested it so many times that i will kill the flash of coolpad :P

 

it can restore eavrything from TWRP 2.4, i dont tested it with cwm backups (didnt know that it can do such things, really ?)

it can flash everything like patches,apks,supeSU etc

it refuse two or three times to flash some 4.2.2 roms (jonzalvos was one of them) but i thing that this has something to do with the mount point

other that that ......

well you tell me guys :P

 

It refused but flashed them eventually or couldn't flash them at all?

Link to comment
Share on other sites

Guest martinoff

from logs that was mismatch for system partitions,

no error at all, twrp end up with sucsess message but when i chose reboot to system then give me the message

"No OS found, are you sure you want to reboot"

 

in jonzalvo rom (which is one of my favorite) in updater script the system has currect mount point, the same as recovery.fstab of twrp

but here i think was the trubble. 

this is jonzalvo updater script

 

format("ext4", "EMMC", "/dev/block/mmcblk0p8", "0", "/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p10", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p8", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/data");
and this is recovery.fstab from TWRP

/cache ext4		/dev/block/mmcblk0p9
/data	ext4		/dev/block/mmcblk0p10
/system	ext4		/dev/block/mmcblk0p8
which are prety the same, but jonzalvo's rom is built with android kitchen and has differnet name in build.prop from other roms

which are showing as ro.product.device=Coolpad8297W

so i think this has something to do with how android kitchen is building the rom

Edited by martinoff
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.