[CWM For All MTK] Easy Magic CWM MT6575 MT6515 MT6577, MT6517 MT6589 MT6582 MT6592

[Zaiaku]

MT6572 on Jaike v11 worked wonderfully. didn't think it would but let it continue and bam success

[logon]

My 1st post here: Hi all of you!

The phone is HUAWEI Y330-U01 - MT6572 - 4.2.2 JELLY BEAN.

I found a custom CWM recovery and the phone is correctly rooted.

Now I'm trying to edit the resouces (PNG) inside the CWM recovery.img and all does seem to work flawlessly: CTRv2.4 is really a great app (thank you)!

However when I try to flash that edited "new-image" (renamed as "recovery.img", of course) running SP Flash Tool then an error (6045) does occur (please take a look at screenshot in attachment)...

So I compared the working CWM custom recovery and the just created one running a HEX editor: and the last is so different in the magic values...

I know that "ANDROID!" is the right value for the most ones out there, but now I think that Y330-U01 phone was a bit different...

Please note that I can flawlessly restore both the stock "recovery.img" and the CWM custom "recovery.img" running SP Flash Tool and also I tried "all" available versions with the same results.

Also I tried to edit the "new-image.img" running the HEX editor and replacing the first bunch of bytes with those from the working CWM until the "kernel" word, but then the SP Flash Tool error does change in 6048 one...

Any addressing is very appreciated!

So many thanks in advance!

[logon]

After further investigations now I can say that the device has a secure boot... and its stock "recovery.img" is signed, as matter of fact its original name is "recovery-sign.img".

Furtermore the boot magic (ANDROID!) is finding at offset 0x4040... I'm not an expert, but I guess that the values at the beginning was a kind of signature and I do not know how to sign an edited recovery.img or an existing one (created by MTKDT, as an example)...

So definively it is not a CTRv2.4 issue.

Please note that a custom CWM recovery for Y330-U01 is out there (and working flawlessly) and I wonder how its creator did in order to sign the recovery.img...

If compared running an HEX editor the stock recovery.img and the custom CWM recovery.img have the boot magic at the same offset (0x4040) although the values are slightly different...

So many thanks the same!

Greetings

[jahgogo]

I alrea
dy flash cwm to my phone but it is currupt saying cant mount cache recovry and all that can this magic cwm solve my problem ....??

[saintangel]

This is valid to MTK8312?

[indtram]

Hi....
Not Working......it says you have a secure boot image.....not compatible with your kitkat device....

Any info ???

Thanxxx

[Galacticos]

I wish d great ones can create a software that will forcefully turn usb debugging on any android phones that stuck in pattern lock..

[vkmr83]

I used it for Xolo Q1011 but it not works.

any solution???

[Sekypapa]

I want to use it for my new Inew V7A, but it not working.

[Trenzalore]

hi, please see these other links to creating your own CWM [Only registered and activated users can see links Click here to register]
good luck!