yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] yuweng:
Then you are on the wrong thread, my friend, for manual unpack/ repack, you should post questions on their thread instead... :cowboy:

My Auto-Port tool(Credits to Master Shifu Michfood) will upload your Stock recovery, unpack it, unpack compatible MTK CWM, mods its recovery.fstab so that any MTK device will work regardless of its partition no.(Credits to Master Shifu bgcngm), repack it & download it back to your MTK device... :cool:

Since you are here, it works both ways... :cool:

1) Unpack Stock recovery then unpack compatible MTK CWM

2) Delete ramdisk at Stock, copy CWM ramdisk folder over & repack it

or

3) Copy your Stock kernel to replace the one at CWM & repack it

Since you said your phone has no original recovery then refer to post #385... :cool:
[Miscellaneous Android Development] mogamycool:
Hi Yuweng, I made a recovery img using flash tool , and used Michfood ,but I found out that there is no recovery mode .

I repeated the steps , but whenever using Auto-Port-MTK-CWM it tells me to install usb drivers though it's installed. Before doning that when i press the volume up +power buttons a screen appears to be a recovery mode without options ,and after that whenever i press the same buttons nothing appears.

Can you tell me the steps after making recovery img?
[Miscellaneous Android Development] icoolguy1995:
Hello there,

Is there any chance of creating app for porting phil recovery ?

and for TWRP 2.6.0.0
[Miscellaneous Android Development] praderj:
Problems with the ported recovery, Kindly help

using Celkon A97i(MT6575 device) when i used the auto port tool to port a 6.0.3.0 touch and flashed everything is working fine.. But the touch recovery i got have some problems, Actually it is in touch format but touch is not working also backup is not working..I tried various versions of CWM.. Only Im facing problem with touch recovery but with the non touch recovery everything is working fine.. Kindly help me devs... I'm new to XDA..
[Miscellaneous Android Development] yuweng:
Bro, the first time you show up here & lost without a trace, 2nd time here also lost without a trace & now you come back here again & i presume it'll be the same... Conclusions, please read, google first & hands on then you'll figured out all by yourself without asking any questions as most of them are already answered... :cowboy:

PhilZ Touch 5 Recovery has been ported over to MTK but as usual doesn't backup boot & recovery b'cos its not compiled from sources for MTK devices...

Master Shifu carliv told me he has compiled a fully working Philz recovery for his V967S but its non-touch, same as CWM b'cos its closed source... :cowboy:

He has contacted [MENTION=4666971]Phil3759[/MENTION] but no reply, he presume PhilZ is too busy updating his sources to latest CM10.2 if not he would have release a full touch version for V967S... :fingers-crossed:

As for TWRP 2.6.0.0, this version has bugs too & it has affected a few devices including MTK as reported by Master Shifu Javum here if not i would've make a porting tool out of it, the same with PhilZ recovery... :cool:

AFAICR, i've mentioned this before, touch is at the kernel & if its not working then you'll have to live with it unless your device manufacturer compiles a new one with touch... :fingers-crossed:

As said at the OP, i've only tested a few recoveries listed there & if you use others then you'll have to test those out yourself whether backup/ restore works or not... :cowboy:
[Miscellaneous Android Development] dnle71:
i have tried philz recovery, i assume it was coz it has the same UI. Ported it to my phone using it's own kernel but it's in chinese, the good thing is it's touch is working.
[Miscellaneous Android Development] praderj:
TWRP working properly

AFAICR, i've mentioned this before, touch is at the kernel & if its not working then you'll have to live with it unless your device manufacturer compiles a new one with touch... :fingers-crossed:

As said at the OP, i've only tested a few recoveries listed there & if you use others then you'll have to test those out yourself whether backup/ restore works or not... :cowboy:[/QUOTE]

If it is with the kernel then how I get TWRP 2.5 working good with my mobile.. Plzz Help the junior member Devs. or just make me understand that I wont get Touch CWMR..
[Miscellaneous Android Development] icoolguy1995:
Simple cwm touch is closed source

Sent from my Xperia keyboard.
[Miscellaneous Android Development] praderj:
Please provide some recovery.

please provide some standard recovery version 6.0.3.6 for MT6575 device so that i can port it to my device..I searced several forums,.. I didnt get anything yet.. so please help me developers...
[Miscellaneous Android Development] yuweng:
Bro, everything is at the OP if you don't even bother to read it carefully then nobody will ever bother to help you...

Just for you, porting tool is here recovery.img for port is here... :cool:
[Miscellaneous Android Development] praderj:
Thank you bro..

Thank you brother.. I've already tried all these brother.. but i didnt get a working clockworkmod.. Thats why I asked you for help.. Anyhow thank you so much for your help bro...
[Miscellaneous Android Development] OraXdaDevelopers:
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.
[Miscellaneous Android Development] yuweng:
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.. [MENTION=5325910]praderj[/MENTION] : 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... :o)

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:
[Miscellaneous Android Development] icoolguy1995:
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
[Miscellaneous Android Development] praderj:
Thank you brother..
[Miscellaneous Android Development] JohnnyInBriz:
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.
[Miscellaneous Android Development] OraXdaDevelopers:
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.
[Miscellaneous Android Development] JohnnyInBriz:
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.
[Miscellaneous Android Development] OraXdaDevelopers:
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:
[Miscellaneous Android Development] JohnnyInBriz:
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
[Miscellaneous Android Development] OraXdaDevelopers:
I think his is a well-known error. Either you start with the firmware upgrade option. Or edit your Scatterfile

Original:

{

}

__NODL_FAT 0xd7780000

New:

{

}

FAT 0xd7780000
[Miscellaneous Android Development] JohnnyInBriz:
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'
[Miscellaneous Android Development] OraXdaDevelopers:
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.
[Miscellaneous Android Development] rnovino:
cm10.1 compile

Awesome [MENTION=4478781]yuweng[/MENTION] 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?
[Miscellaneous Android Development] praderj:
Use the recovery generated in upuntu... This tool works with that recovery only... I've tested it.. snd working fine....
[Miscellaneous Android Development] rnovino:
boot.img

[MENTION=4478781]yuweng[/MENTION] 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 ----------

ignore my post haha it worked now I just needed to rebuild the environment
[Miscellaneous Android Development] rnovino:
[MENTION=4478781]yuweng[/MENTION] 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 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?
[Miscellaneous Android Development] rnovino:
did you modify any file? mine compiled successfully but it seems not booting up into the recovery
[Miscellaneous Android Development] praderj:
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 [MENTION=4478781]yuweng[/MENTION] built this repack tool for windows.. try this.. [MENTION=4940526]rnovino[/MENTION] if u still face problem.. PM yuweng master.. he will help you..

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

Use the repack tool that [MENTION=4478781]yuweng[/MENTION] 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..
[Miscellaneous Android Development] rnovino:
that's what I did exactly but it didn't boot up :( only stock in the boot logo :(
[Miscellaneous Android Development] praderj:
How did u flashed the recovery.. using sp flash tool or mobile uncle tools.. I used SP flash tool.. In mobile uncle tools I found problems.. it shows completed but actually it didn't install anything..
[Miscellaneous Android Development] rnovino:
I use the SP flash tool also and the MTK repack itself also both didn't work maybe i missed something :(
[Miscellaneous Android Development] praderj:
Why don't you PM yuweng for help. I got success in compiling.. Sorry for the inconvinence.. If u have done everything corectly it should work in MT devices.. I compiled for 2 MT devices and it worked fine.. The same I got from the auto port tool...
[Miscellaneous Android Development] rnovino:
Yup already PM [MENTION=4478781]yuweng[/MENTION] I am trying to recompile again from the start hoping it will fix it with clean install
[Miscellaneous Android Development] praderj:
Good luck buddy... don't struggle a lot for this.. already carliv released a recovery v6.0.3.6.. I've ported it to my device as recomended by yuweng.. now my device has the latest cwm.. also I got the same recovery when compiled it in upuntu.. both seems to be the same.. try to port that one.. sorry if u ve already done that..
[Miscellaneous Android Development] rnovino:
I downloaded that also but did not work also , btw what unit did you pot the cwm
[Miscellaneous Android Development] praderj:
All your tools are working fine in wimdows 8 bro.. I tried all your tools in windows 8 only.. seems to be working fine.. recomend your tools for windows 8 also..

---------- Post added at 11:05 PM ---------- Previous post was at 10:56 PM ----------

Bro.. here is the link for my cwm recovery..

http://xdaforums.com/showthread.php?t=2434605

try this with the auto port tool.. For error free working disable your antivirus and user account control.. also in your phone download the stock recovery before using this tool.. hope this would help.. one tip brother.. check the size of the recovery that get ported before flashing it on auto port tool.. the ported recovery should be around 5 mb.. if its very small then it won't be working.. I tried almost 30 recoveries with this tool.. only few were working others didn't.. as you said it stuck in boot logo.. use only mediatek device recovery.. this tool works on other recoveries too.. but they won't work when installed.. this is my experience with this tool..

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

Post your stock bro.. let me try that.. I love porting recoveries with this tool...
[Miscellaneous Android Development] D@nge1:
Ported TWRP 2.5.0.0 recovery not start. Smart - ThL W9, section recovery increased to 7Mb ... The stock, CWM and TWRP to the size of 6Mb start rules, where to dig?
[Miscellaneous Android Development] praderj:
read the thread completely... means the first page on TWRP 2.5 port tool.. There is a link to a page that will guide you to permanently increase the recovery partition size.... Hopr this will be useful...
[Miscellaneous Android Development] D@nge1:
You think I have not read? I have read and did everything according to instructions. It does not work TWRP ...
[Miscellaneous Android Development] yuweng:
praderj is correct, you gotta read the whole thread, there are a few great inputs from DEVs & also users input... :cowboy:

If you have read it completely then you would have found the answers here & here & here... :cool:

Its applicable for both TWRP & CWMR
[Miscellaneous Android Development] D@nge1:
All this and read more than once! Such problems running not only for me, but still have a few people with china-iphone.ru, but the problem has not been solved .... TWRP does not start if the image size exceeds 6291456 bytes. Again - the section in the firmware recovery increased to 7Mb.
[Miscellaneous Android Development] KopiJahe:
Hi there,

I successfully ported TWRP 2.5.0.0 to ZTE N986, the only thing that didn't work is the screen won't go off, but that's doesn't really matter at all :)

Now, my ZTE N986 just got updated, and it's now featuring "datamedia" layout (no more virtual internal memory), which is awesome for some people (including me), but, it also breaks TWRP (showing "cannot mount /emmc" errors).

I tried to change the recovery.fstab, by deleting /emmc entry, but now twrp is showing "cannot mount /sdcard" :eek:

and then, I tried to change the /emmc's mountpoints to be the same as /data (which is located at /emmc@usrdata), it didn't show any error on my side, but on my friend's phone, it still showing "cannot mount /emmc" error, even some of them claim that they cannot install anything from recovery :confused:

can you help me with this one? I tried to read the thread, but I can't seem to find the answer.

Thanks in advance

PS: Here's the link to ported TWRP for ZTE N986 (with dual partition system): download
[Miscellaneous Android Development] yuweng:
Bro, i have mention this many times, i can't help you when you have given no lead at all...

Did you download your whole Factory ROM with the modded 7Mb scatter.txt... :confused: Pls list out whole procedure you did then i may find a clue where it went wrong... :cool:

Congrats Bro, you manage to get the 7Mb mod to work on your MT6589...

i'm teaching you how to fish... :cowboy:

1) adb shell -> ls & see what is the new datamedia listed as... There should be the normal emmc@android, emmc@cache, emmc@ebr1, emmc@fat, emmc@sec_ro, emmc@usrdata

2) Open init.rc & add mkdir /datamedia after mkdir /emmc

3) Add /datamedia	ext4	/emmc@datamedia or /datamedia	vfat	/emmc@datamedia if its the internal memory or whatever that is listed at step 1 for datamedia & trial & error...

Good Luck... :o
[Miscellaneous Android Development] D@nge1:
I changed changed scatter: SEC_RO 0x3600000 -> SEC_RO 0x3700000 and sewing of the factory flashed through Firmware Upgrade. The smartphone will start normally, just start reсovery stock and CWM, run and TWRP, provided that the size of the image is not prevshaet stock recovery. If you collect a larger size, it will not start, although the re-initialization has completed successfully!
[Miscellaneous Android Development] KopiJahe:
Actually, ZTE N986 did have 7MB recovery partition from the beginning :)

and about "datamedia" layout, I don't want to get you wrong, but what I mean was: the previously virtual internal memory (emmc@fat) is now combined with internal memory (emmc@usrdata). I even tried to put the mount point to /emmc@usrdata/media :laugh:

I ended up deleting /emmc entries on recovery.fstab, and suprisingly, there's no error (not like before :confused: ), but now there's no option to wipe .android_secure
[Miscellaneous Android Development] yuweng:
Hmm, now i'm even more confused with your explanation... :laugh:

Ok, AFAIK, typically MTK Android layout is as below...

[COLOR="Blue"]Internal - Typical 512MB - System - Non-mountable

Internal - Typical 1.5GB - emmc(SDcard) - Mountable

External - Typical 1 to 32 GB - vfat(SDcard2) - Mountable[/COLOR]

So which is the one did you say that the latest MTK devices had it combined... :cowboy:
[Miscellaneous Android Development] KopiJahe:
Here's my partition table:

Before upgrade

Internal - 900 mb - /system (/emmc@android)
Internal - 1.25 gb - /data (/emmc@usrdata)
Internal - 1.25 gb - /emmc (/emmc@fat)
External - x.x gb - /sdcard

After upgrade

Internal - 900 mb - /system (/emmc@android)
Internal - 2.5 gb - /data (/emmc@usrdata)
External - x.x gb - /sdcard
[Miscellaneous Android Development] bgcngm:
It's a fact. Some MTK devices now have a datamedia partition.

Tomorrow I can share the working recovery.fstab of S6000-H, which has also been upgraded and also features datamedia partition.
[Miscellaneous Android Development] bgcngm:
[MENTION=2689045]awaaas[/MENTION]

There you go:

# mount point	fstype	device	[device2]

/boot	emmc	/dev/bootimg
/cache	ext4	/emmc@cache
/data	ext4	/emmc@usrdata
/misc	emmc	/dev/misc
/recovery	emmc	/dev/recovery
/system	ext4	/emmc@android
/sdcard	datamedia	/dev/null
/external_sd	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1

It is working perfectly on CWM recovery. :cool:
[Miscellaneous Android Development] KopiJahe:
In twrp, there's error

E: Unknown File System: 'datamedia'

I'll dig more into it, thanks :good:
[Miscellaneous Android Development] bgcngm:
Ohhh, works fine with CWM. :p

Hint: try to find a TWRP recovery for one HTC phone which has datamedia partition (HTC One, for example). ;)
[Miscellaneous Android Development] :
Good Evening Masters [MENTION=4209278]ywen[/MENTION]g & [MENTION=455439]bgcngm[/MENTION]

I have successfully ported the Philz Recovery for my device Micromax A110 with MTK6577 in it. I am getting few small problems :-

1) Backup & restore of both boot & recovery is not working.

2) touch is not working.

I asked Dev Phil3759 for this but he told to compile CM10 from sources which is impossible for a guy like me.

So now expecting some help from the gurus here. Would anyone mind to take a look on this. I will be grateful for the help received.

Though I don't need touch, just to solve the restore and backup of boot & recovery only.

Thanks for your time masters. Will be waiting for a positive reply.
[Miscellaneous Android Development] icoolguy1995:
Cant we give him our non booting cm10.1
[Miscellaneous Android Development] bgcngm:
A solution for compiling from sources has been already released (even with the correct backup of boot and recovery partition on MT6589 devices), just read the OP. You won't get touch though, as it is not open source.
[Miscellaneous Android Development] yuweng:
Bro, why don't you use my Auto-Port tool to port my Master Shifu's COT over to your device...

1) Backup & Restore of both boot & recovery IS working.

2) Touch IS working

3) Support custom Theme (Since you're themer, it'll be great for you to create custom themes for it... :good:)

Supports MT6575/ 77 / 89 & it works on either emmc or mtd filesystems too...
[Miscellaneous Android Development] Sk.D:
The link of your porting tool is not working!! :) please update
[Miscellaneous Android Development] wahuka:
hello all.

I have a Bluebo B6000 MT6589T and have cwm recovery from Taiwan101.

I have no idea on programing so i come here in search of help for my B6000.

It would be possible for any member who can compile, TWPR port to recovery for my B6000.

Tell me if you need any file from phone, rom, etc..

I'd be very grateful if someone could make me a TWPR.

I hope some answers

regards
[Miscellaneous Android Development] praderj:
Read the op first.. it does not need any programming skills.. if you have a windows pc and the tool in it you can easily port it automatically... for example if you wanna port to twrp download the twrp 2.5.00 port tool in the op that is the first page of the thread.. for using this tool you should have root access.. run the tool.. the tool asks you to disable UAC in your computer. Click ok to restart your computer.. run the tool after restarting your pc and follow the instruction.. it will also installs the ported recovery to your device and boot your device to recovery.. these are all for auto.. if you want to manually port it copy the stock recovery to the tool folder and follow the instruction.. scince its touch recovery be aware of your phones resolution.. if you still don't know to port pm me your phone specs like resolution and partition(emmc or mtd) and your stock recovery.. I'll port it for you...

Sent from my Celkon A97i
[Miscellaneous Android Development] andrman1:
I have error Aborting, an error has been detected... > i tried with twrp and cot but nothing