yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] imaulana:
Dear, Master yuweng

I did what you told me to do in the last post. And i got the new recovery.img, but when i want to repack it with your MTK Repacker, it said : Aborting, error been detected. Is there something that i missed? Or is there something i have to install in Windows before i use the tool?

When i do this for CWM v6.0.3.6 --> there's no such an error like this.

BTW, i use Windows 8 32 bit, Avira antivirus is OFF, Net.Framework 4.5

Oh yeah: one more: when i use MTK Unpack.bat --> it said: Error end offset is lower than start offset
[Miscellaneous Android Development] yuweng:
Been very busy at work lately... :o Hmm, just now only tested the same 6036 script & it compiled out 6040 alright... :cowboy:

i think you didn't do the Menu 7 -> Cleaning up Build Environment which is a must before compiling on a new repo or a new device... :cool:
[Miscellaneous Android Development] imaulana:
Thank you for your answer, master. i already do the Menu 7. But when i use this code:

cd ~/cm10.1 && rm -rf ~/cm10.1/.repo/manifests && rm ~/cm10.1/.repo/manifest.xml && repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1 && repo sync -f -j4

It always give me this in the terminal:

Your identity is: xdausers <xdausers@gmail.com>
If you want to change this, please re-run 'repo init' with --config-name

repo has been initialized in /home/indra/cm10.1
Fetching projects: 0% (1/365) From git://github.com/carliv/mtk6589_bootable_recovery
+ 185f2e2...d6af841 master -> github/master (forced update)
Fetching projects: 100% (365/365), done.
info: A new version of repo is available

object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <cco3@android.com> 1380645867 -0700

repo 1.12.4

gpg: Signature made Tue 01 Oct 2013 11:44:27 PM WIT using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'

warning: Skipped upgrade to unverified version
Deleting obsolete path /home/indra/cm10.1/device/ti/panda
Syncing work tree: 100% (365/365), done.

bootable/recovery/: discarding 1025 commits

and then, when i use this code:

cd ~/cm10.1 && repo sync -f -j4

no matter which repo that i used, it always give me this :

Fetching projects: 100% (365/365), done.
info: A new version of repo is available

object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <cco3@android.com> 1380645867 -0700

repo 1.12.4

gpg: Signature made Tue 01 Oct 2013 11:44:27 PM WIT using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'

warning: Skipped upgrade to unverified version
error: Cannot remove project "device/ZTE/V967S": uncommitted changesare present
commit changes, then run sync again

i really don't know why?

Any answer will be great.

Thank you

--------------------------------------------------------------------------------SOLVED----------------------------------------------------------------------------------------------------------------------------------------

I Keep trying and trying and suddenly it works but i don't know why and how. And right now i just have CWM 6.0.4.0 for my device, and it is fully working.

Thanks again Master yuweng
[Miscellaneous Android Development] BHARDIK:
Awesome Master Shifu, THanks Once again

Thanks

Hardy Ahir
[Miscellaneous Android Development] yuweng:
Based on your error log, i believe you must've manually deleted the ~/cm10.1/device/ZTE/V967S thats why you get all these error... Use Menu 7 first then delete ZTE/V967S & you won't get these error... :o

When encounter this problem, use below command to fix it then delete whole ~/cm10.1/bootable/recovery folder (it'll sync faster when deleted)

cd ~/cm10.1 && sudo make clean && sudo make installclean && sudo make clobber

Now use the 6036 script Menu 3 & it'll auto sync latest CM source & Master Shifu carliv's latest 6040 bootable/recovery repo...

And i'm sure you should have seen the below info too...

... A new repo command ( 1.20) is available.
... You should upgrade soon:

[B][COLOR="blue"]cp /home/indra/cm10.1/.repo/repo/repo /home/indra/bin/repo[/COLOR][/B]

After you have use the above command, you won't get the upgrade soon prompt anymore... :cowboy:

Now that you've successfully compiled out a fully working 6040 its time for you to build your own device tree & compile a new one for it... :cool:

1) cd ~/cm10.1 && build/tools/device/mkvendor.sh (your device manufacturer) (your model name) ~/boot.img

e.g for your device : build/tools/device/mkvendor.sh Tinji Tinji_i9300 ~/boot.img

2) Unpack your MTK stock recovery.img & cross-reference it with Master Shifu carliv's ZTE/V967S particularly the BoardConfig.mk & recovery folder

3) lunch cm_Tinji_i9300-eng && . build/tools/device/makerecoveries.sh cm_Tinji_i9300-eng OR make -j4 recoveryimage

4) After completion, go to ~/cm10.1/out/target/product/Tinji_i9300 & your recovery.img should be there...

Cheers, you have compiled your own recovery with your own device tree... :D
[Miscellaneous Android Development] FaIzaL3040:
Cwm for BM Mobile

HI guys...i need some help n sory if i aksing same question twice..

so i have A7000 BM Mobile with mediatek MT6577 .. my problem is this phone stuck at bootloop and wanna try format it with cwm recovery.

my phone is 100 % factory setting.. i know op already give a link for MT6577 cwm but i not sure if i can use it with my phone..

my device info is :

BB chip: MT6577

Modem Ver: MAUI.11AMD.W12.22.SP.V8.P2

Kernel Ver: 3.0.13 (root@abcde-desktop) gcc version 4.4.3

Android Ver: 4.0.3

tq..
[Miscellaneous Android Development] yuweng:
Bro, it might be too late already, you should have backup your Factory ROM with MTK Droid Tools first... :fingers-crossed:

Try the stock 3e recovery -> take out & put back battery -> Hold Volume UP( if it doesn't work then try Volume Down ) don't let go, now press power until it boots into 3e -> navigate using the Menu, Home, Escape, Volume Up/ Down button -> Wipe Data/ Factory Reset

If still it doesn't boot then refer to here... :laugh:
[Miscellaneous Android Development] BHARDIK:
i successfully ported COT recovery for my device but after install it in my MT6589 based device UMI X2 its want show cot recovery screen its just show umi logo then nothing stuck there., but in cmd its show cot-recovery recovery mode

when i type "adb devices" what the problem with my recovery any idea dear master shifu Yuweng ?
[Miscellaneous Android Development] yuweng:
i realize the bugs when i make CTR porting tool... :o 1080x1920 & all tablets res doesn't work... Use CTR instead, lazy to fix old mod... :D
[Miscellaneous Android Development] BHARDIK:
hummm thanks master yuweng !

Hardy
[Miscellaneous Android Development] bilalz400:
It says CTR Recovery does not support you device res my device res is 320x480
[Miscellaneous Android Development] yuweng:
Foresee only two possibility why it fail to detect your device res... :cowboy:

1) Your device res is not exactly 320 x 480

2) The porting tool uses screencap or screenshot from your ROM, if it doesn't exist then it cannot detect your device res...

Use this one here with this one here & follow on-screen for porting instructions... :cool:
[Miscellaneous Android Development] bilalz400:
My device res is 320x480 even the porting tool says that and I can comfirm it as well I tried it with auto and manual with factory and cwm recovery all giving same error
[Miscellaneous Android Development] yuweng:
Bro, i have mentioned this many times on this thread & also on my other thread, help me to help you by providing as many info as possible... :o

i don't even know which or where my program went wrong when you said all giving same error...

The least you could do is attach your stock recovery.img here so that i can check on it... :cool:
[Miscellaneous Android Development] bilalz400:
My phone is an mt6575 (MT6628) running gingerbread its screen size is 3.5" and its res is 320X480

I was trying to port CTR recovery by your automatic porting tool but i was getting error that your device res isnt supported even though there is 320x480 sources in it and my device is COMFIRMED 320x480 device its is still giving error

Right now i am running CWM Recovery ported by [MENTION=5119815]rua1[/MENTION] MTk Droid Root And Tools

Files which may help

Boot.img

https://www.dropbox.com/s/xct0xmf4pe1v5do/boot.img

Recovery :

https://www.dropbox.com/s/usslkvcwgj2uw3x/recovery (2).img?m
[Miscellaneous Android Development] FaIzaL3040:
thanks for ur help by the way ..

i already do a full reset about 10 times before but still stuck at bootloop..

any help please..
[Miscellaneous Android Development] Neodragon12:
Hello folks, does the scripts for CWM or TWRP are running with a new MT6582 chipset device ?

I've extracted succesfully a full ROM with MTKdroidTools, try to convert the recovery. It seems that it worked but impossible to update the recovery.img with MobileUncle Tools (the old recovery remains each time), nore with SP Flash Tool (error 8038) and nore with Fastboot (no recovery partition). All tools i'm using are the latest ones.

Thanks if u can help ;)

The phone: Haipai S4 A9500, proc MT6582 4x1.3Ghz 1Gb/4Gb, Mali400-MP2
[Miscellaneous Android Development] yao85930101:
Brothers updated look Carliv Touch Recovery v1.1:good:
[Miscellaneous Android Development] yuweng:
Busy with site work, fyi, i do android modding during office hour when business is bad + i got nothing else better to do...

Recently, a fellow xda member pm me & i found out there are 2 variance for MT6572 one uses ext4 & the other one uses ubifs & he brick his ubifs MT6572.... :eek:

Upload your stock recovery.img here & i'll check it out for you first... :cool: If you insist on DIY then you can try CTR it'll auto-install the recovery when ported successfully... :cowboy:

i'll update it later meanwhile you can use this to port it over to your MTK if you can't wait... :cowboy:
[Miscellaneous Android Development] Neodragon12:
Ok thanks :fingers-crossed:

Here is the recovery: https://hotfile.com/dl/252865941/0f6a938/Stock_recovery_A9500.zip.html
[Miscellaneous Android Development] yao85930101:
Oh thank you pay, the transplant has been used now, and look forward to your new version
[Miscellaneous Android Development] Neodragon12:
CTR method worked like a charm with my MT6582 device, thanks a lot Yuweng
[Miscellaneous Android Development] tarkin88:
Hi i'm have motorola Razr D3 with CPU Model MTK6577 is a 2 cores cpu, i want to know if someone can make a recovery for my device? i want to make a Customs ROM's but no CWM or TWR for my device... please someone help!

Sorry for my bad english :3
[Miscellaneous Android Development] yuweng:
i have wasted enough time on Razr refer to post #254 onwards, i get zero feedback & only farenheith has the experience, finally make some progress then his Razr got stolen...

RAZR D3 MT6577 FACTS SUMMARY

1) Even my Master Shifu Michfood refuse to help unless i get a Razr myself... :cowboy:

He says his Repack Utils is Open-Source so you guys have to figure out how to mod his tools for your Razr.

It unpack Razr correctly but you have to mod it to repack it back to Razr format... :cowboy:

2) Unpack MZF via RSD Lite has the standard MT65xx layout but its system-sign.img can't be unpack with any existing tools...

No one ever feedback if using adb command to backup system.img can be unpack. If it can't be unpack then most probably you can't cook any ROM at all... :cowboy:

adb shell
> su
> mount -o remount,rw /dev/block/mmcblk0p4 /system
> dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img

Credits to Master Shifu dsixda for above command. Use Android Kitchen & see if it can unpack system.img... :fingers-crossed:

3) farenheith has made some progress before he lost his Razr. Everytime he flash my modded TWRP/ CWM then his Razr won't boot. He then use SP Flash Tool to download stock recovery-sign.img & it'll boot, no need to use RSD Lite. Refer to here for details. Refer to here for firmware & RSD Lite...
[Miscellaneous Android Development] derkvol:
Use my Auto-Port to port it to your 320x480 MT6573.. Sorry, but it don't work in my Fly IQ260 MTK6573
[Miscellaneous Android Development] yao85930101:
Glad to see updated CTR v1.1, but how only MT6573, MT6589 how not updated automatically update hope hurry transplant.

Thank you very much to pay:good:
[Miscellaneous Android Development] yuweng:
Never realize the old auto-mod prompt error when detected MT6573 SoC... Updated info at the OP... :o

All my recent mods are shared without proper testing & it's full of bugs... :o So this time, i'm gonna fully test it before sharing, as said, my old Auto-Port tool is still fully functional to port CTR v1.1 to any MT65xx & you didn't try it... :cowboy:

Just download your screen size from here & use the Auto-Port, if it doesn't work then double-click again & it'll work (again, its a bug)... :o
[Miscellaneous Android Development] superdragonpt:
[MENTION=4478781]yuweng[/MENTION] nice tool ;)

Usually i do it manually, but The tool should be usefull for people with less experience.

Since we are talking about different MTK SoC's it would be hard to make an 100% bug free port tool.

im sure this (great) tool will work for The majority, if it doesn't work, just manually port it, it's not that hard.

If you guys need some help, just ask, here or on The CTR thread.

B.Regards
[Miscellaneous Android Development] derkvol:
Sorry, it's don't work:confused:
[Miscellaneous Android Development] yuweng:
Then just install it directly, AFAIK, mine is a clone of your IQ260 so it should work... :cowboy:
[Miscellaneous Android Development] yao85930101:
No use has been absolutely no way to install the driver prompts you to install or suggested have tried 20-30 times
[Miscellaneous Android Development] yuweng:
it means you didn't read this... if still cannot then attach your stock recovery.img here... :cool:
[Miscellaneous Android Development] yao85930101:
I do not know where the problem is why the Auto-Port-MTK-CWM will not connect to the

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

ro.secure=0

ro.allow.mock.location=1

persist.mtk.aee.aed=off

ro.debuggable=1

persist.sys.usb.config=mass_storage,adb

persist.service.acm.enable=0

persist.service.adb.enable=1

ro.build.id=JOP40D

ro.product.model=AMOI N828

ro.product.brand=AMOI

ro.product.name=amoi89_wet_jb2

ro.product.device=amoi89_wet_jb2

ro.product.board=amoi89_wet_jb2

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=AMOI

Use CTR for MTK.exe already do a good job
[Miscellaneous Android Development] derkvol:
Yes, i did it: i install it directly with mobileuncle :fingers-crossed:
[Miscellaneous Android Development] rnovino:
How about mt6572 but I think it will work also on MTK droid root and tools :)
[Miscellaneous Android Development] yuweng:
As said here currently there are no official CWM or TWRP that support ubifs... :fingers-crossed:

AFAIK, only Christian Troy has built TWRP/ CWM with ubifs & he has also shared ROM upgrade ubifs to ext4 as there are ZeRo ROM on ubifs & tons of ROMs on ext4 format... :laugh:

MTK Droid Tools has a beta version that support ubifs here... :cool:
[Miscellaneous Android Development] manikkumar20:
aey i used auto port for TWRP2.5 for MTK 6589 but when i flahsed recovery img using mobile uncle tools the phone goes blank...what is wroing can anyone help??
[Miscellaneous Android Development] yuweng:
Did you try the Auto-Port feature... :confused: it'll auto-check if ported TWRP is over-sized BUT it will still let you install it if you want & after that you will loose you IMEI (refer to here)... :D

As said before, most MT6589 kernel is larger & lately even the latest compiled CWM doesn't fit to most MT6589 6Mb recovery size anymore... :cowboy:

My 7Mb mod has mix response, some says it works while other says it doesn't even boot after mod... :eek:

While for some latest MT6589 devices, it comes from Factory with 7Mb recovery partition (refer to here) so mod at your own risk... :cool:

Always backup your Factory ROM with MTK Droid Tools first before modding this & that or you'll end up here... :laugh:
[Miscellaneous Android Development] OraXdaDevelopers:
Hi all,

I have successfully generated a 5.5.0.4 version of CWMR with droid tool.

But I like a newer version of CWMR for my MT6572. All what I need is a sample of the newest version of recovery.IMG from a MT6572.

How can help me? Thx
[Miscellaneous Android Development] manikkumar20:
you r right i flashed that TWRP 2 ON MY MTK 6589 AND THEN it didnt boot only blank screen and my IMEI was lost...:( any solution for this?
[Miscellaneous Android Development] yuweng:
Guys, if you don't read then nobody can help you...

Many has pm me too, read everything in this thread, many great feedbacks & tips from fellow xda members, all already mentioned with solutions & answers... :good:
[Miscellaneous Android Development] rashidkn:
are you used first page porting tools???

this tools contain latest recovery with aroma file manager... and fully automatic...

http://d-h.st/ewo

---------- Post added at 02:17 PM ---------- Previous post was at 02:12 PM ----------

---------- Post added at 02:20 PM ---------- Previous post was at 02:17 PM ----------

one question ...

whats different between this two type of mounting partitions :

# mount point fstype device [device2]

/boot emmc /dev/bootimg
/misc emmc /dev/misc
/recovery emmc /dev/recovery
[B][COLOR=Red]/system ext4 /dev/block/mmcblk0p4
/cache ext4 /dev/block/mmcblk0p5
/data ext4 /dev/block/mmcblk0p6
/emmc vfat /dev/block/mmcblk0p7[/COLOR][/B]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2

with this :

# mount point fstype device [device2]

/boot emmc /dev/bootimg
/misc emmc /dev/misc
/recovery emmc /dev/recovery
[B][COLOR=Red]/system ext4 /emmc@android
/cache ext4 /emmc@cache
/data ext4 /emmc@usrdata
/emmc vfat /emmc@fat[/COLOR][/B]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
[Miscellaneous Android Development] dyulay:
[MENTION=4478781]yuweng[/MENTION]

I used porting tool in OP but i have a problem, recovery menu is upside down.. I can't fully utilize its touch function. Are there any solutions to this?

I also used aroma file manager, it's working fine but it is also upside down. I have an mt6572 device, an oem of Spice Mi-436 Stellar Glamour. I have an 1-otm8018b_dsi_vdo lcd driver IC..
[Miscellaneous Android Development] estape11:
Hi, if i have CWM 5 compile by MTdroid tools, i can use this porting tools or i need do someting?
[Miscellaneous Android Development] superdragonpt:
Let me answer those last replys...

use the search please,

it has been answered several times...

@rashidkn

Those mount points, should work in the same way.

If you don't know what your doing, you should call the direct mount points names (mmcblk XXXX)
[Miscellaneous Android Development] betamax08:
I tried the CWMR and TWRP method but it doesnt work for my phone. can somebody assist me on this one.

I will attach my scatter txt, boot and recovery which i got from MTK droid tools.

SKK Mobile Impulse mtk6575

PRELOADER 0x0

{

}

DSP_BL 0x40000

{

}

__NODL_NVRAM 0x100000

{

}

__NODL_SECCFG 0x400000

{

}

UBOOT 0x420000

{

}

BOOTIMG 0x480000

{

}

RECOVERY 0x980000

{

}

SEC_RO 0xe80000

{

}

__NODL_MISC 0xfa0000

{

}

LOGO 0x1000000

{

}

__NODL_EXPDB 0x1300000

{

}

__NODL_FAT 0x13a0000

{

}

ANDROID 0x27a0000

{

}

CACHE 0x14ea0000

{

}

USRDATA 0x18aa0000

{

}

__NODL_BMTPOOL 0xFFFF0050

{

}
[Miscellaneous Android Development] yuweng:
As superdragonpt says, they are the same... :cowboy:

The first one with adb -> cat /proc/dumchar_info & you'll get the physical block, the 2nd one credits to Master Shifu bgcngm it doesn't care if your android system partition is at mmcblk0p3, 4, 5, 6 or 7 it will mount system to emmc@android

Take a look at init.rc & you'll know what i mean, it actually saves me a few lines of codes so i don't have to use adb to detect the mmcblk0pX number... :laugh:

in fact, i've tried compiling CTR with BOARD_HAS_FLIPPED_SCREEN := true but still it doesn't flip... :o

i'm not good at modding source code so you gotta report this to my Master Shifu carliv so that he can compile a flip CTR for you when he is free... :laugh:

Hmm, i've been getting a few reports that the porting tool doesn't work while CWM 5504 from MTK Droid Tools works... :o

They are just too many variance of MT65xx out there so you guys have to figure it out yourself with this tool... :cowboy:

Unpack both, use the init from 5504 or your stock recovery & see if it boots... :fingers-crossed:

Added on 18 Nov 2013

Hmm, based on your scatter.txt layout, its a MT6575 with mtd & your recovery partition is only 5Mb, ported CWM/ TWRP is way over 5Mb in size thats why it doesn't boot... :cool:

You gotta increase your SEC_RO 0xF80000 & do Factory ROM download, for cross-reference refer to the 7Mb mod at OP for emmc partition... :cool:

WARNING : Might brick your MTK device if you donno what you're doing...
[Miscellaneous Android Development] rashidkn:
yes true... but in default configs... i cannot format my system partition to ext4 " emmc@android"

but when i changed emmc@android to dirrect adress "dev/block/mmcbl0p4" now i can easily format and mount system partition...
[Miscellaneous Android Development] topaza:
Hi,

I am not able to create a CTR Image as my device is for some reason not recognized by the tool. Why is a connection to the phone needed in "manual mode"?

I have a recovery.img of my stock recovery. Is it somehow possible to generate an CTR recovery.img out of my stock img without any connection to my phone?
[Miscellaneous Android Development] yuweng:
if you have read 5 pages from the back then you would've know the whole story here thats why now i've included the adb checking in it even on manual porting... :cool:

if you know what you're doing, the old mod doesn't do any checking then refer to this one here... :cowboy:
[Miscellaneous Android Development] Lokifish Marz:
Any chance of adding 240x240 to one of the touch based porting tools. I ask because there are multiple MTK65xx smartwatches that lack Vol buttons and the current porting tools don't support 240x240.
[Miscellaneous Android Development] topaza:
Thanks for the links. What exactly do you refer to when talking about your old mod? When I download the auto-port tool from the thread you linked to, it still complains that it has no adb connection. So you probably mean something else with the "old mod" and I just don´t get it... ;) would you mind to post the download link?
[Miscellaneous Android Development] yuweng:
Whoops, beside being bad with source code modding, i'm also bad at modding graphics thingy...

My Master Shifu carliv is kinda busy right now & he once share with me that his CTR can work on any res only you have to resize the images to 240x240 & compile a new one for the recovery binary to support that res... :cowboy:

WoW, never realize so many MTK SmartWatch BTW what is your SmartWatch SoC -> MT657?

Whoops sorry bro, totally forgotten that i have updated that old porting tool too, link is here & use at your own risk... :o
[Miscellaneous Android Development] Lokifish Marz:
I'll play with it but I'm more ROM side and have only been able to mount/extract the system image but not recovery. This is also my first time playing with MTK based devices so I'm having to get used to no fastboot and with a smartwatch that lacks volume buttons.

Which one? ;)

Right now I have an EC309 (MT6577) from Vapirius which they resell as the AX-2 Comet which the gave me for development. I am being shipped the TrueSmart Engineering Prototype (MT6572) as well as backing the TrueSmart Oct Dev Edition which will ship in December.