[PORT] [TOOL] Carliv Touch Recovery for MediaTek devices

Search This thread
By:
Advanced…
OraXdaDevelopers

OraXdaDevelopers

Senior Member
Mar 11, 2012
97
17
Just I try my post here now
I have tried to porting a original recovery.img from a MTK6589 Phone HaiPai N7889 with porting tool.
Method 1 automatically
Method 2 manual

Both the tool generate e new recovery,img. Because the size is bigger as 6.1444kByte a have increase the recovery size like 1 MByte (whole 7MByte), Now a use a smaller SEC_RO.

If the new generated flash back to the phone, th phone works fine still. But...
I can not boot in the TWMR. The boot logo is freezed,

Any Idea? Please help.
 
yuweng

yuweng

Senior Member
Feb 5, 2012
1,172
4,226
praderj said:
but i didnt get a working clockworkmod.. Thats why I asked you for help..
Click to expand...
Click to collapse
OraXdaDevelopers said:
I can not boot in the TWMR.
Click to expand...
Click to collapse
There is nothing special about this porting tool, in simple term, it just copy & paste & repack your kernel with ported CWM ramdisk, Thanks to Master Shifu Michfood you can do it on Win OS... :cowboy: You can always use the manual way to check why it is not working on your PC... :cool:

It is very important for you guys to give as many info as possible such as Win OS version, did you switch off UAC Anti-Virus.. @praderj : You never mention you've ported a working TWRP with touch working & only said CWM touch is not working... ) All these infos are critical if you want it solved & AFAIK, a working CWM touch for MTK MT6575/ 77/ 89 doesn't exists... :cowboy:

Many has ported compatible CWM using this tool so there is only 3 possibility...
1) Some settings on the PC prevent this tool from working properly (UAC/ Anti-Virus/ Third-Party App conflict)
2) Ported CWM not compatible for your device
3) There is some bugs on my program... (if its proven then i would like to solve that... :eek:)

Or just attach your stock 3e recovery.img to your post, i'm sure other Master Shifu will be gladly to help you out... :cowboy:
 
Last edited:
  • Like
Reactions: Deleted member 5186178 and praderj
icoolguy1995

icoolguy1995

Senior Member
Jun 22, 2012
2,188
1,502
HARDA
Buddy we need your help to port 4.2.2 I know this is not the thread to ask but Help is needed so I asked you and our master

Sent from my Samsung GT-l9100 using XDA Premium 4 mobile app
 
P

praderj

Senior Member
Jun 26, 2013
251
177
Bangalore
www.getcooltricks.com
Thank you brother..

yuweng said:
There is nothing special about this porting tool, @yuweng bro..
I understand brother.. I've disabled UAC and antivirus.. The program is working properly and i'm getting the ported clockwork mod.. But the ported recovery is not working properly. Backup is not working.. When i click backup it just stuck.. and i've to remove my battery for reboot.. I'm uploading my stock recovery here bro.. Kindly port it for me when you get free time.. Thanks to all Developers of this porting tool...
Click to expand...
Click to collapse
 

Attachments

  • recovery.img
    4.1 MB · Views: 23
Last edited:
J

JohnnyInBriz

Senior Member
Oct 7, 2010
283
95
Brisbane
Xiaomi Mi Max 3
Samsung Galaxy A72 4G
OraXdaDevelopers said:
Just I try my post here now
I have tried to porting a original recovery.img from a MTK6589 Phone HaiPai N7889 with porting tool.
Method 1 automatically
Method 2 manual

Both the tool generate e new recovery,img. Because the size is bigger as 6.1444kByte a have increase the recovery size like 1 MByte (whole 7MByte), Now a use a smaller SEC_RO.

If the new generated flash back to the phone, th phone works fine still. But...
I can not boot in the TWMR. The boot logo is freezed,

Any Idea? Please help.
Click to expand...
Click to collapse
Just a caution re displacing sec_ro partition to allow for larger recovery. On my MoreFine S6pro at least, it seems that sec_ro partition is used. I tried porting TWRP and then install it.TWRP didn't actually work but when I rebooted the phone everything was fine until I noticed no SIMs detected. Luckily I had already ported CWM (thanks yuweng) and I then used it to flash the sec_ro image using a zip I had made and my SIMs started working again. Had to use CWM because I haven't found a version of SP_Flash tool for this phone yet. CWM was installed using MobileUncle tools.

From what I've read so far it seems the partition layout is either defined in the kernel or is passed to the kernel from uboot so make sure you have a backup or copy of the original rom before trying to instal a recovery larger than 6MB.
 
OraXdaDevelopers

OraXdaDevelopers

Senior Member
Mar 11, 2012
97
17
JohnnyInBriz said:
Just a caution re displacing sec_ro partition to allow for larger recovery.
Click to expand...
Click to collapse
You did not understand me.
I have not in the original SEC_RO written. But I have generated a to 1MB smaler SEC_RO. A dump shows that it contains only binary zeros in the last 1 Mybte.
Old SEC_RO 6,144 Kbytes starting at 0x3380000
New SEC_RO 5,120 Kbytes starting at 0x3380000

Whole flashed back by firmware upgrade!

So the new recovery.img can be greater as 6,144 and then lesser as 7,168 Kbytes.
After this the phone works well, Because The ported TWRP does not works.
 
J

JohnnyInBriz

Senior Member
Oct 7, 2010
283
95
Brisbane
Xiaomi Mi Max 3
Samsung Galaxy A72 4G
OraXdaDevelopers said:
You did not understand me.
I have not in the original SEC_RO written. But I have generated a to 1MB smaler SEC_RO. A dump shows that it contains only binary zeros in the last 1 Mybte.
Old SEC_RO 6,144 Kbytes starting at 0x3380000
New SEC_RO 5,120 Kbytes starting at 0x3380000

Whole flashed back by firmware upgrade!

So the new recovery.img can be greater as 6,144 and then lesser as 7,168 Kbytes.
After this the phone works well, Because The ported TWRP does not works.
Click to expand...
Click to collapse
My comment wasn't aimed at you in particular. Changing the starting address of sec_ro partition will allow you to use SP_Flash tool to flash a larger recovery partition but it doesn't change the partition location in the firmware. If the firmware uses this partition as my phone seems to, there can be problems.
 
  • Like
Reactions: OraXdaDevelopers
OraXdaDevelopers

OraXdaDevelopers

Senior Member
Mar 11, 2012
97
17
JohnnyInBriz said:
My comment wasn't aimed at you in particular. Changing the starting address of sec_ro partition will allow you to use SP_Flash tool to flash a larger recovery partition but it doesn't change the partition location in the firmware. ...
Click to expand...
Click to collapse
Why has then the scatterfile, readed back from phone with droid tool a changed mapping? I think a whole flash with option "firmware" change the PMT table too?
To back to my problem... The ported TWRP does not start:mad:
 
Last edited:
J

JohnnyInBriz

Senior Member
Oct 7, 2010
283
95
Brisbane
Xiaomi Mi Max 3
Samsung Galaxy A72 4G
OraXdaDevelopers said:
Why has then the scatterfile, readed back from phone with droid tool a changed mapping? I think a whole flash with option "firmware" change the PMT table too?
To back to my problem... The ported TWRP does not start:mad:
Click to expand...
Click to collapse

You may be correct as I haven't found a version of SP_Flash that works on my phone. I can read back but not download, keeps giving error 8038
 
J

JohnnyInBriz

Senior Member
Oct 7, 2010
283
95
Brisbane
Xiaomi Mi Max 3
Samsung Galaxy A72 4G
Yes thanks but I already tried editing a scatter file, and I don't have any original firmware for this phone so I'm reluctant to do a firmware upgrade. I've cross-checked the scatter file I'm using with /proc/dumchar_info so I'm reasonably sure it's ok but still error 8308 and the comment 'PMT is ready and layout has changed'
 
OraXdaDevelopers

OraXdaDevelopers

Senior Member
Mar 11, 2012
97
17
Only with the "Firmware upgrade" of FT option with all images it is possible to change the PMT Tables to back of original. Some times hasn't the original flash archive sec_to, cache and userdata images. Use similarly from other ROM and flash after this.
 
Last edited:
rnovino

rnovino

Senior Member
Nov 7, 2012
104
37
cm10.1 compile

yuweng said:
-------------------------
Added on Sept 1, 2013 - Compile CWM for MT6575/ 77/ 89 from CM 10.1 Sources on Oracle Virtualbox
i've wrote an AIO bash script for compiling CWM from CM10.1 Sources for MTK devices on ubuntu 13.04 x64 on Virtualbox... :cowboy:
So now anyone also can compile from source & you can proudly say i compile my own CWM for my MTK device...
ag_zps1e5a29ec.gif


Credits to Master Shifu carliv & nolinuxnoparty

Good Luck & Cheers.... :cowboy:
Click to expand...
Click to collapse

Awesome @yuweng will definetely try script, just quick question is it required to use the recovery.img that was generated in the ubuntu? or we can just grab our own recovery.img from our backup stock rom?
 
P

praderj

Senior Member
Jun 26, 2013
251
177
Bangalore
www.getcooltricks.com
rnovino said:
Awesome @yuweng will definetely try script, just quick question is it required to use the recovery.img that was generated in the ubuntu? or we can just grab our own recovery.img from our backup stock rom?
Click to expand...
Click to collapse

Use the recovery generated in upuntu... This tool works with that recovery only... I've tested it.. snd working fine....

Sent from my Celkon A97i using xda app-developers app
 
rnovino

rnovino

Senior Member
Nov 7, 2012
104
37
boot.img

praderj said:
Use the recovery generated in upuntu... This tool works with that recovery only... I've tested it.. snd working fine....

Sent from my Celkon A97i using xda app-developers app
Click to expand...
Click to collapse

@yuweng I paste the boot.img in the cm10.1 root folder but it seems it is not detecting it where do I paste it so it will properly work?

---------- Post added at 07:51 PM ---------- Previous post was at 07:32 PM ----------
rnovino said:
@yuweng I paste the boot.img in the cm10.1 root folder but it seems it is not detecting it where do I paste it so it will properly work?
Click to expand...
Click to collapse

ignore my post haha it worked now I just needed to rebuild the environment
 
rnovino

rnovino

Senior Member
Nov 7, 2012
104
37
@yuweng on your script if I resync the cm10.1 again thus it start again from the start or it just update?

also when I compiled it showed this one
3nRA2E8.png
it's jb 4.2.2 but my unit is only 4.2.1 I think that is the reason it doesn't load the cwm recovery when I flashed it is there a way to edit it before I recompile again?
 
Last edited:
rnovino

rnovino

Senior Member
Nov 7, 2012
104
37
praderj said:
Use the recovery generated in upuntu... This tool works with that recovery only... I've tested it.. snd working fine....

Sent from my Celkon A97i using xda app-developers app
Click to expand...
Click to collapse

did you modify any file? mine compiled successfully but it seems not booting up into the recovery
 
P

praderj

Senior Member
Jun 26, 2013
251
177
Bangalore
www.getcooltricks.com
Copy the compiled recovery from upuntu.. If I'm correct this repack utility is compatible in windows only.. open the repack tool folder.. now paste the recovery... then start the tool... this is the procedure I used.. mine is working perfectly.. tje recovery u get from upuntu won't boot.. that's u @yuweng built this repack tool for windows.. try this.. @rnovino if u still face problem.. PM yuweng master.. he will help you..

Sent from my Celkon A97i using xda app-developers app

---------- Post added at 10:00 PM ---------- Previous post was at 09:54 PM ----------
rnovino said:
did you modify any file? mine compiled successfully but it seems not booting up into the recovery
Click to expand...
Click to collapse

Use the repack tool that @yuweng compiled.. it will repack the recovery.. Then only it will boot.. if u r using raw recovery compiled in upuntu it won't boot up..

Sent from my Celkon A97i using xda app-developers app
 
Last edited:
rnovino

rnovino

Senior Member
Nov 7, 2012
104
37
praderj said:
Use the recovery generated in upuntu... This tool works with that recovery only... I've tested it.. snd working fine....

Sent from my Celkon A97i using xda app-developers app
Click to expand...
Click to collapse

praderj said:
Copy the compiled recovery from upuntu.. If I'm correct this repack utility is compatible in windows only.. open the repack tool folder.. now paste the recovery... then start the tool... this is the procedure I used.. mine is working perfectly.. tje recovery u get from upuntu won't boot.. that's u @yuweng built this repack tool for windows.. try this.. @rnovino if u still face problem.. PM yuweng master.. he will help you..

Sent from my Celkon A97i using xda app-developers app

---------- Post added at 10:00 PM ---------- Previous post was at 09:54 PM ----------



Use the repack tool that @yuweng compiled.. it will repack the recovery.. Then only it will boot.. if u r using raw recovery compiled in upuntu it won't boot up..

Sent from my Celkon A97i using xda app-developers app
Click to expand...
Click to collapse

that's what I did exactly but it didn't boot up :( only stock in the boot logo :(
 
You must log in or register to reply here.

Similar threads

bucefal82
Cyanogenmod for mediatek devices
Replies
7K
Views
2M
flux_capacitor
flux_capacitor
yuweng
  • Locked
[TUT] [TOOL] MT65xx ROM Porting
Replies
2K
Views
792K
justmpm
justmpm
D
  • Locked
[EOL][RECOVERY]CarlivTouchRecovery v2.7(4.2.2) for port to MTK phones[EOL]
Replies
763
Views
469K
S
sawdoctor
S
Intel Android Devices Root / Temp Recovery Session
Replies
1K
Views
961K
Fancheinux
Fancheinux
superdragonpt
[RECOVERYs] [ROMs] [UNLOCK BL] ASUS Memo Pad HD 7 (me173x) [MT8125] [MULTILANG]
Replies
2K
Views
1M
k1dehner
k1dehner

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 262
    yuweng
    yuweng
    Old Tool
    Added on Mar 05, 2014
    Updated CTR v2.2 for MTK devices with ubifs ONLY
    And Thanks to dhinesh77 for countless beta-testing & most importantly, Master Shifu carliv for looking into those ubifs source code to make it work on MTK devices....
    salute_zps09342dc6.gif


    Download link here...

    Solution to cannot see whole sdcard is here by Master Shifu himself, it is actually a new feature/ function... :laugh:
    ----------------------------------------------------------
    Added on Jan 27, 2014
    Updated CTR v2.2 Recovery for MT6575,15, 77, 17, 89, 82, 88, 92
    MT6572 (ext4 only, ubifs not supported)

    Pls support by donation or at least drop your thanks here to encourage Master Shifu for further development...
    rclxms_zps452ba9d3.gif


    Download link here

    ----------------------------------------------------------
    Added on June 02, 2014
    New Porting Tool CTRv-1.4 for ext4 devices ONLY. . .

    Known problems : Touch not working on some MTK devices . . . :cowboy:

    Any bugs report here . . . :cool:
    ----------------------------------------------------------
    Added on June 10, 2014
    New AIO Porting Tool Easy Magic CTR v2.4 Installer for MTK for ALL MTK Cortex-A9/ A7 devices ONLY with either mtd, emmc, ubifs or custpack partition . . . :cowboy:

    Any bugs report here . . . :cool:

    Updates
    Thanks to surfturtle for reporting . . . :eek:

    Workaround : Use Manual mode & select 720x1024 that is the screen res for 720x1280 . . .

    This is an AIO porting tool so go ahead & try the differrent res at Manual mode, the unpack/ repack feature, play around with it & you'll learn what is needed for porting custom recoveries . . . :cool:
    ----------------------------------------------------------
    Added on June 17, 2014
    Users using XP & 720x1280 MTK devices use this fix . . . :eek:
    ----------------------------------------------------------
    Added on July 01, 2014
    CTRv2.5 refer to here . . . :cowboy:
    ----------------------------------------------------------
    Notice to annoying n00bs & newbies

    Most of your questions are already answered on this thread so pls read it...
    alamak_zps2e31ed77.gif


    1) Either your MTK is still ro.secure=1 then use this method here then EXIT/ CLOSE it first then re-start the porting tool...

    2) i've already put in alot of error checking to make sure this porting tool works, either the Auto or Manual port, it will leave behind Ported-CTR folder then manually install it via SPFT when it fail to auto install.... Most probably why it fail to install is b'cos you use SuperSu did you bother to look at your MTK device & grant access to Root Shell... There has been cases where the stock recovery is already corrupted then this tool will also port a corrupted CTR too. Re-install your stock 3e recovery.img & make sure you can boot into it then only use the porting tool again or just use the manual port... The differences is Auto will upload whatever recovery already at your device be it older CWM or TWRP & it will repack it with CTR ramdisk. While Manual will use whatever at your stock 3e -> factory_init.project.rc, meta_init.modem.rc, ueventd.rc & etc... Refer to this by Master Shifu carliv... :good: This tool has no log b'cos it is actually a simple copy & paste program, thats what it actually do.... :laugh:

    3) Pls bear in mind that this porting tool has been downloaded by many & confirmed working BUT i can't guarantee that it will work flawlessly on your MTK device so continue trying & report back the solution if you found one... :cowboy:

    4) This has been mentioned many times on this thread, if you really can't get it to work then don't just say your porting tool doesn't work...
    alamak_zps2e31ed77.gif


    Instead list out everything then it'll be easier to trouble-shoot
    a) What OS you are using on the PC & your MTK...
    b) Did you disable UAC & Anti-Virus on your PC
    c) Did you execute the porting tool at C:\ drive if you're using XP else then at your Desktop READ what the porting tool says & it will ask you to wait then wait for it to continue without pressing the OK button...

    As said many times, this porting tool uses Russian Master Shifu Michfood Repack Utils Huge Credits to him, it is actually DOS program with cygwin dll working at the back so all DOS limitation still applies such as it will ONLY operate properly when it is executed at the Desktop on latest OS... Tested working on XP to 8.1

    As much info as possible then it'll be easy to identify where it goes wrong & did you bother to read 5 to 10 pages from the back then you would have know what is the latest story... :rolleyes:

    Last but not least, i didn't compile CTR so any features not working / bugs found pls report it here BUT again, read the whole thread first as most already answered at that thread...

    Q&A

    1) Touch not working, refer to here...
    2) MTK Alcatel devices refer to here & here... Supported on CTRv2.4
    3) All MTK devices supported except this...
    4) Inverted screen solutions -> Compile your own
    5) CTRv2.5
    View
    24
    yuweng
    yuweng
    Guys, i can't keep up with all the different porting tools i've made, pls DIY if you want CTRv2.5. . .

    The porting tool has everything & already given you all the info you need . . .

    Step 1
    • If yours is emmc/ mtd refer to here & download your device res
    • If yours is custpack refer to here & download your device res
    • If yours is ubifs refer to here & download your device res

    Step 2
    1. Use the Unpack/ Repack recovery.img -> Unpack recovery.img, copy downloaded CTRv2.5 Eg: port_CarlivTouch-recovery-2_5-480x854.img & rename it to recovery.img & press OK
    2. Goto CTRv2.4\UnpackRepack\recovery\rmdisk & copy whole res folder out
    3. Goto CTRv2.4\UnpackRepack\recovery\rmdisk\sbin & copy the binary file named recovery out

    Step 3
    1. Use the Unpack/ Repack recovery.img -> Unpack recovery.img again to unpack the earlier working CTRv2.4 recovery.img for your device
    2. Delete res folder & replace it with res from CTRv2.5
    3. Replace recovery from CTRv2.5 to sbin
    4. Manual edit CTRv2.4\UnpackRepack\recovery\rmdisk\etc\recovery.fstab with Notepad++ & add the below accordingly
      Code: 
      /boot        emmc    /dev/bootimg
/recovery    emmc    /dev/recovery
/uboot       emmc    /dev/uboot
/nvram       [COLOR="red"]emmc[/COLOR]    /dev/nvram[COLOR="Red"] <- Add this new line[/COLOR]

[B][COLOR="Blue"]OR[/COLOR][/B]

/nvram       [COLOR="Red"]mtd[/COLOR]      nvram
    5. Use the Repack recovery.img & let it auto-install the new CTRv2.5 to your device, thats it !

    View
    14
    yuweng
    yuweng
    Yo, Bala bro, been quite busy with work, until now only manage to finish this tut... :eek:

    Yeah, i was thinking about that too, to mod dsixda's android kitchen just for MT6573 platform that includes Bruno Martins's unpack/ repack boot.img, unpack/ repack recovery & port it to CWMR like this tut, replace a2sd with data2ext or ad2sdx; only this two mod stable on MT6573 platform so far that i have tested...

    actually did try but give up half way as my scripting skill is still at novice level... :eek:

    did read it on some other forum that someone is actually doing that too but i never see it got release though...:p

    Well i guess we need dsixda expertise to be able to do that but he is retired now...
    ids_emoticon_wilted.gif


    Added on Sept 04, 2012 Info Update
    Dark Tremor's a2sd/ Apps2sd works well on MT6573 platform after all... :eek:

    i was using the last version 2.7.5.3 Beta 04 all this while & i always use a2sd datasd all the time & it FC all apps after a few weeks of using/ sometimes a few days even after a fresh install...

    After all, DT_a2sd/ apps2sd is actually apps to sd & i always push it as data2sd... :eek:

    Only until recently that i play with Android Kitchen, use it to extract my system.img & update it with its built-in Darktremor Apps2SD version 2.7.5.2, it works extremely well because 2.7.5.2 doesn't support a2sd datasd feature...

    So guys, if you are using DT_a2sd beta 4, don't use the command a2sd data2sd instead use a2sd cachesd...

    You can checkout my other post here
    View
    12
    bgcngm
    bgcngm
    Okay, here's CWM recovery v6.0.2.8 (ramdisk only) for anyone that wants to port it to MT65xx based devices. Please note that this ramdisk contains my Huawei U8836D specific files and properties, but it should at least be portable for the majority of MT6577 phones out there. Important note is that init.usb.rc (only needed for MT6577 devices) is device specific and while porting the original must be taken from stock boot.img.

    Other than that, nandroid backup is fully working for devices with eMMC partitions, unlike other recoveries that get stuck while backing up boot partition.

    Happy porting (and don't forget to hit "Thanks" button)! :D
    View
    11
    yuweng
    yuweng
    hello y2yu,

    Glad you find it informative... :D

    According to this site, there will be another 2 new cpu after MT6575/ MT6577... (use google chrome for translation)

    This means MT6573 is 5 generation behind MT6588 & it is still unexploit with all info/ tools scattered all over the web...

    Thats where i decided to compile all these info & put it here... :good:

    Now that i check, i've bought my first mediatek back in 2008...( never knew it until i check it just now ) :silly: It has serve me well for almost 2 years in spite of dropping, a few times from 8 feet height when i was on a ladder & it still works ! It was the last drop that spoilt the mic & render it unuseful. It can still make & receive call to date but the other side can't hear what i say... :eek:

    At that time, made in china phone was famous for its extra loud speaker/ ringtone but doesn't support android back then...

    haha, enough of history, have you manage to port CWMR to your MT6573 ? In fact, i have manage to create a plugin for dsixda's Android Kitchen which can port CWMR to any MT6573 with a few copy & paste features just like Android Kitchen... :good:

    Still testing it, may be you would like to be the first beta tester... :confused:
    View

New posts