yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] yuweng:
i don't own an Alcatel & i have completely no idea what is happening in your phone, always attach log when reporting error . . . :cool:

Test all functions -> BackUp/ Restore -> Mount USB -> etc meaning go thru ALL PhilZ Touch menu & try every menu

Repeat procedure to wipe cache then reboot to PhilZ Touch -> Advanced Functions -> Report Error -> attach /sdcard/clockworkmod/philz_recovery.log

At MTK-PhilZ -> attach log.txt. Attach the ported PhilZ Touch recovery.img too so that i can check where it went wrong . . . Try the Manual mode too
[Android Software/Hacking General [Developers Only]] NFound:
In manual mode, the same thing. Prior to wipe all partitions are mounted and working, after a wipe cache partition is not mounted. Log and recovery here http://d-h.st/HNf
[Android Software/Hacking General [Developers Only]] yuweng:
In the past, many has experience upon booting a newly flashed recovery to their MTK, there is E: failed to mount /cache, a simple format cache would have solve this problem . . .

At PhilZ Touch -> do a Wipe and Format Options -> Wipe Cache first then reboot & after reboot do a fresh Backup/ Restore & it shall work properly . . . Check the log again & see if there is any more . . .

mount: mounting /emmc@cache on /cache failed: Invalid argument
W:failed to mount /emmc@cache /cache ext4 (File exists)
[Android Software/Hacking General [Developers Only]] NFound:
Sorry for my bad English, maybe you did not understand correctly. Explain the points that I made:

1 Philz established and went into recovery, while section cache normally mounted.

2 Clicked Wipe and Format Options -> Wipe cache and this process stops! (at the bottom of the strip turns endlessly, only helps hard reset)

3 When re-entering at the bottom there is an error Philz failed to mount /emmc@cache

Section cache disappears and it can only be vosstanovt through SP FlashTool. In the TWRP of such problems there.

There is a suspicion that the srorke recovery not properly prescribed cache partition size, so it overwrites something else.
[Android Software/Hacking General [Developers Only]] johnnybra:
Finally, I could build recovery with your tool using a virtual machine. Very thank you!

But I have a noob and silly question: your tool flash the recovery to device but, in order to share with other P8 users, in which folder is the correct built recovery? /Philz or /mtk-philz?????

Edit: it was in Philz folder ;(

The compilation date is from a month ago, is there any way decompiling the recovery.img to insert the correct date manually???
[Android Software/Hacking General [Developers Only]] avi3230:
[MENTION=4478781]yuweng[/MENTION] sir,

waiting for PhilZ Touch 6.58.7 tool by u:good::good:
[Android Software/Hacking General [Developers Only]] Santhosh M:
Tool updates can't be bought out regularly. Instead you can check out master yuweng tutorial on compiling recovery from source with. You can keep updated yourselves any time if u compile :)
[Android Software/Hacking General [Developers Only]] yuweng:
Most importantly, is the existing version not working properly, don't only look at the version increment BUT look at the commits history, it is in plain simple English, it has absolutely nothing beneficially whatsoever to MTK except it fix compilation error so that you can still build PhilZ Touch from source with cm-11.0 repo . . .

However, i do need feedbacks from MTK Alcatel users BUT again the WARNINGS : Make sure you know how to unbrick MTK or don't even try it, read carefully post #1 to post #4 for more info, you have been fore-warned . . . :cool:
[Android Software/Hacking General [Developers Only]] mi-425:
Hello yuweng,

I have a problem with my device iBall andi 4.5K6+ having MT6572 and Kitkat 4.4.2. I tried all recoveries(cwm, carliv, Twrp)except yours philz Touch because I can't found easy recovery installer for philz or don't know how to make philz recovery for my device my device's resolution is 480x856. Please help to port custom recovery to my device.....:confused:
[Android Software/Hacking General [Developers Only]] Papdya:
Hey i have a mt6577 device .. I.e micromax canvas music.. But when i run the exe and connect my phone it says recovery partition only 62xxxxxx sumthing.. U said u had compiled twrp for mt6577 plz help me... Should i continue the installation?
[Android Software/Hacking General [Developers Only]] iZLeeP:
The size of your recovery partition is only 6mb and the tool already warned you about it. You'll brick your recovery partition if you proceed with flashing ported philz using the tool since it will exceed 6mb.
[Android Software/Hacking General [Developers Only]] Papdya:
Yes i realised that.. But yuweng said he had made one for his mt6577 so was asking... Cause i dont want to set up linux an all and was searching for alternatives and found this awesome tool.. But alas it didnt work out for me.:(
[Android Software/Hacking General [Developers Only]] iZLeeP:
It's because yuweng's MT6577 kernel is small that's why the ported philz recovery fits.
[Android Software/Hacking General [Developers Only]] Papdya:
K thanks for helping.
[Android Software/Hacking General [Developers Only]] zania:
Installed in a fake lenovo s960s with mtk 6982 with an awful rom. Thanks for your efforts.
[Android Software/Hacking General [Developers Only]] rjt.rockx:
Can I feature this tool in an article on my friend's blog ? This is really a great tool and I felt I should feature it there.
[Android Software/Hacking General [Developers Only]] IsolatedKM:
Thanks for share. I'll try
[Android Software/Hacking General [Developers Only]] papatzis:
Hi I have a Chinese 10.1 tablet with MT8389 Soc, I had managed to rooted with root genius and I have a Kinguser

I had installed the recovery, hardware buttons are working, scrolling is working, but I cannot select touching the screen, I touch somewhere it is selected only once, after that the touch doen't do anything,

If for example I press the down button only the first time it goes down after nothing, if I select repeat on and press the down button the cursor goes down very fast without stopping and it stops only if I press the hardware button

Since hardware buttons are working it is not importand, but is there any fix I had checked Touch accuracy all the settings but nothing

Thank you in advance
[Android Software/Hacking General [Developers Only]] Prometheus:
is there any way to get the recovery.img only and not to install it? adb doesnt work on my pc so i aborts at adb not working step..i just want the ported recovery in my pc so that i can install it manually
[Android Software/Hacking General [Developers Only]] yuweng:
This thread originates from Miscellaneous Android Development & move to Android Software and Hacking General [Developers Only] thanks to MOD justmpm, requested by me & the reason is very simple as stated at post #2, however even some RDs still do that . . .

Since you can't even get adb to work then i'm sorry to say that this tool is not for you to use, refer to your device forum DEVs & ask them to have a look on this porting tool then . . . :cool:

Refer to post #2 then . . . :cowboy:

Updates

Has been working on Easy Magic PhilZ Touch Installer to support latest MTK big.LITTLE & Cortex-A53 so unfortunate that my only beta-tester NiksSkersts breaks his USB port & those that downloads from here, guess what ZERO feedback . . . :rolleyes:

Fyi, i'm still using my MTK Cortex-A9 so pls pm me & let me know if there is any bug on big.LITTLE & Cortex-A53 MTK devices before i officially release it . . . :cool:
[Android Software/Hacking General [Developers Only]] Grimm97:
For all mtk devices?
[Android Software/Hacking General [Developers Only]] EnerJon:
[MENTION=4478781]yuweng[/MENTION] brother, i am unable to download latest beta v7, chrome browser shows nothing but my downloader keeps showing this error message
[Android Software/Hacking General [Developers Only]] yuweng:
Fyi, d-h.st has updated their server even the porting tool couldn't download required files so i use copy.com & i've attach it to post #137 . . . :cool:
[Android Software/Hacking General [Developers Only]] EnerJon:
Thanks, going to download it (y)
[Android Software/Hacking General [Developers Only]] EnerJon:
My Device: Qmobile-A900 (GiONEE-Elife-E3 - 4GB) (MT6589) Running KK-4.4.2

Tested: PhilZ Recovery 6.59.0 - Beta v7 | Manual installation Mode

All Basic Functions Are Working Fine (Making Backup, Restoring Backup, Flashing ZIPs)

Suggestions:

1:

When We Are Making Recovery Using Manual Mode, installer Should Wait For User To Press "OK" Button instead Of Automatically Rebooting To Recovery...

2:

You Should Use 0BB4 as a Vendor-ID & 0C03 as a Product-ID in Your Recovery Making Tools Because These Are The Most Common IDs Used in MTK Devices For ADB+MassStorage Mode
[Android Software/Hacking General [Developers Only]] yuweng:
Thanks for the feedback & suggestions, as for the adb, my motto has been If it ain't broken, don't fix it, you only need to install the adb driver once & it'll work after that . . . :laugh:

Once upon a time . . . :o
[Android Software/Hacking General [Developers Only]] nghiepduclub:
i have a zopo 980, not zopo 980+, i can up recovery CWM 6x on zopo 980 (mtk6589 ARM Cortex A7 1.5GHZ) ? can you help me ?
[Android Software/Hacking General [Developers Only]] xpeca1:
works on Lenovo A936 (Note 8)!

Hi, Mr. yuweng!

I'd like also to report smooth and easy recovery installation on my Lenovo A936 Note 8 (golden warrior).

Used Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY v7.

Device : Lenovo A936 Kitkat 4.4.4 MTK6752

TKS a lot !
[Android Software/Hacking General [Developers Only]] hanuma:
Make full screenshot PhilZ Recovery
[Android Software/Hacking General [Developers Only]] xpeca1:
Screenshot or img?

The UI looks exactly as on PhilZ' CWM thread > xdaforums.com/showthread.php?t=2201860 I don't see any added value to take another screenshots.

My dd .img's are here: fastshare.cz/4378933/lenovoa936-cwmrecovery.zip

Again, kudoz goes to yuweng.

Fix the links with http prefix above - I cannot paste links yet as I'm new to the forum.
[Android Software/Hacking General [Developers Only]] hanuma:
I want to see what the font size?
[Android Software/Hacking General [Developers Only]] xpeca1:
OK didn't found quick & easy way to make a capture, so sending a photo to give a flavour. I used the default font values during installation process and for my usage I found it very convenient - considering it's 6" screen on a936..

*updated > <http://> s7.postimg.org/63053m5bf/a936.jpg

regards xPeca
[Android Software/Hacking General [Developers Only]] hanuma:
I do not see the image
[Android Software/Hacking General [Developers Only]] xpeca1:
Fixing the link, updated in the previous post :(. Sorry for inconvenience! Downside of the limited capabilities for newbies prior to 10 posts :).

Cheers xPeca
[Android Software/Hacking General [Developers Only]] jbliz:
MT6572

Why MT6572 have such a big kernel, are there's way to reduce it?

Even compress PNG file, still no luck. I have 6.144 KB with PhilZ Recovery 6.786 KB.
[Android Software/Hacking General [Developers Only]] muckelmaus:
That's The problem here. How to get to this page to get this final release. I tryed the beta version the day before this release.

I wonder if both version are the same. I tested the v7 successfully on my lenovo note8 a936, but I can't (find) backup and restore nvram. I thought, this is quite important for our devices!?!

Maybee it's my fault, but I can't find the link, even after I switched from classik view to 2015.

PS.: Our device is definively supported, as we are more than three using your revovery, Thanx!

OKAy, Finally I got it!! My fault! Only visible/reachable in 2013/15 view!
[Android Software/Hacking General [Developers Only]] muckelmaus:
That sounds easier thanit is!

First: Which recovery to take to unpack? The stock or the PhilZ?

Editing default.prop by inserting, no problem. (Just pasting the 3 lines at the end?)

Finding the recovery.fstab file wasn't that difficult, but after I inserted the nvram line I tried to repack the image.

Do I have to connect the device with the stock recovery or any other?

Is it a problem, that the PhilZ recovery was build by v7?

Now I try to use the new build.
[Android Software/Hacking General [Developers Only]] adhamamar:
when i downloaded 6.59.0 r1 and run it it give a massage in logo file " PhilZ.7z source file not found" can you sir put whole installer program Please.
[Android Software/Hacking General [Developers Only]] yuweng:
Notes to all armv8 owners

Please carry out below tests & feedback, if it works then i will incorporate Factory ROM backup into this porting tool . . . :cool:

Requirement : ro.secure=0. Use the command adb shell cat /proc/partinfo & adb shell ls -al /dev/block/platform/mtk-msdc.0/by-name to find out the exact partition on your armv8.

You can also use MTK Droid Tools -> Click at ROOT -> Click at ADB terminal

adb pull /dev/block/platform/mtk-msdc.0/by-name/boot boot.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/recovery recovery.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/custom custom.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/expdb expdb
adb pull /dev/block/platform/mtk-msdc.0/by-name/flashinfo flashinfo
adb pull /dev/block/platform/mtk-msdc.0/by-name/lk lk.bin
adb pull /dev/block/platform/mtk-msdc.0/by-name/logo logo.bin
adb pull /dev/block/platform/mtk-msdc.0/by-name/metadata metadata.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/nvram nvram
adb pull /dev/block/platform/mtk-msdc.0/by-name/para para
adb pull /dev/block/platform/mtk-msdc.0/by-name/proinfo proinfo
adb pull /dev/block/platform/mtk-msdc.0/by-name/protect1 protect_f
adb pull /dev/block/platform/mtk-msdc.0/by-name/protect2 protect_s
adb pull /dev/block/platform/mtk-msdc.0/by-name/seccfg seccfg
adb pull /dev/block/platform/mtk-msdc.0/by-name/secro secro.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/system system.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/tee1 [COLOR="Blue"]trustzone1.bin[/COLOR]
adb pull /dev/block/platform/mtk-msdc.0/by-name/tee2 [COLOR="blue"]trustzone2.bin[/COLOR]
adb pull /dev/block/platform/mtk-msdc.0/by-name/userdata userdata.img
adb pull /dev/block/platform/mtk-msdc.0/by-name/cache cache.img

Please send me trustzone1.bin & trustzone2.bin i think the backups are identical according to P6000 Lollipop scatter.txt

Since you don't even know what to do then let others try it out, refer to the title of this thread . . . :cowboy:

Thats the new feature of this porting tool, auto-download source accordingly to your MTK device, Condition : Working adb & your PC needs to be connected to the internet . . . :cool:

Fyi, if i were to pack everything into the installer, the exe would be close to 40MB !; no one owns all five MTK SoC, it will be a waste of bandwidth !
[Android Software/Hacking General [Developers Only]] muckelmaus:
Developers only!

Thank you, sir!

I'm not stupid! I'm playing around with my expensive every day device!

I was porting WM long before you ever thought of xda-dev!

Making a Faktory Rom backup isn't at all, what i want to do!

I got nearly a dozen roms for it, stock and custom!

I wanted to have the possibility to backup the imei, as it is possible in carliv touch recovery v3 for our device!

I think, that's the problem: Requirement : ro.secure=0

I found it in the old log of v7.
[Android Software/Hacking General [Developers Only]] adhamamar:
"Thats the new feature of this porting tool, auto-download source accordingly to your MTK device, Condition : Working adb & your PC needs to be connected to the internet" Does this mean that i should Connect the phone to the computer during the download ?. (sorry)
[Android Software/Hacking General [Developers Only]] TechDad378:
Great tool!

Verified Easy Magic Philz Touch Installer works for MT6582. Great tool!
[Android Software/Hacking General [Developers Only]] muckelmaus:
Yes, so the software can download the device specific parts. It recognizes the mtk version of your devices cpu.
[Android Software/Hacking General [Developers Only]] yuweng:
You don't have to tell me all that, obviously you still donno what to do & the importance of Factory ROM backup & i'm making this tool not just for you but all users . . . :cool:

Its already explained at page 1 & many times at my other threads & since you wanna brick your armv8 then follow below simple procedure . . .:cowboy:

UnPack the PhilZ Touch that you just ported, UnPack/ RePack recovery.img -> UnPack recovery.img -> Yes

Open MTK-PhilZ\UnPackRePack\rmdisk\default.prop with Notepad++ & add the below to the last line . . .

ro.kernel.android.checkjni=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[COLOR="blue"]ro.cwm.backup_partitions=/nvram
ro.cwm.forbid_format=/nvram
ro.cwm.forbid_mount=/nvram[/COLOR]

Using Notepad++ add nvram to MTK-PhilZ\UnPackRePack\rmdisk\etc\recovery.fstab

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#<src> <mnt_point> <type><mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
[COLOR="Blue"]/dev/block/platform/mtk-msdc.0/by-name/nvram /nvram emmc defaults defaults[/COLOR]
/dev/block/platform/mtk-msdc.0/by-name/lk /lk emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,noatime wait
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata

/devices/mtk-msdc.0/11240000.MSDC1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto

UnPack/ RePack -> RePack -> Yes

What OS you're using ? Once started, it will look for PhilZ.7z source file & if its not there it will auto-download it. If its there, you will see the main menu, What you wanna do. Again, as mentioned at page 1, play with it then you'll know how it works, its already so user friendly & still people find it hard to use . . .

Notes to all

Pls indicate what OS when reporting error, this will narrow down the trouble-shooting procedure & pls read page 1 all over again before error reporting, its has been explained so many times already . . .
[Android Software/Hacking General [Developers Only]] muckelmaus:
-obviously you still donno what to do-

Of cause I do! First I stopped working with your tool!

I took michfoods unpack/repack.bat files to edit my boot.img and the Philz recovery I got, without even connecting the device! Job done!

Drag and drop wasn't such a thing.

EDIT PS: I can read post#2:

Requirement

- Requires Root

- Install adb driver

- Enable USB debugging

- Disable UAC

- Disable driver signature

- Works from Gingerbread to Lollipop but NOT on encrypted data partition on Lollipop but why you enable it back ?

- No need ro.secure=0 to run <<<<<<=========

Post#157:

Requirement : ro.secure=0. <<<<<<=========

Thanks, for THAT!
[Android Software/Hacking General [Developers Only]] yuweng:
You come to my thread asking for help & i guided you but you continue boasting about how smart you are then go figure that out yourself, you won't be getting further help from me & Thanks for being such a noob you're not welcome here anymore . . . :mad:
[Android Software/Hacking General [Developers Only]] muckelmaus:
Well, I think, I can easily live with THAT!!

Make up your mind first, wether your tool needs ro-secure=0, or not.

Then, you can call anyone else a noob.

There are no silly questions, just answers, wich noone is helped with.

Sorry, for wasting everyones time.
[Android Software/Hacking General [Developers Only]] adhamamar:
Mr. yuweng Thank you very much for this tool, it has worked efficiently, the problem that I used Windows XP, but it did not work, but it worked on Windows 7, thanks again

---------- Post added at 03:37 PM ---------- Previous post was at 03:15 PM ----------

how can i backup nvram , i add it to recovery.fstab and fstab.mt8382 like that

recovery.fstab

/dev/bootimg /bootimg emmc defaults defaults

/dev/recovery /recovery emmc defaults defaults

/dev/uboot /uboot emmc defaults defaults

/emmc@android /system ext4 ro,noatime wait

/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait

/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

/dev/misc-sd /preloader ext4 ro,noatime wait

/dev/nvram /nvram emmc defaults defaults

/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto

/devices/platform/mt_usb/musb-hdrc.0/usb1 auto vfat defaults voldmanaged=usbotg:auto

fstab.mt8382

/dev/bootimg /bootimg emmc defaults defaults

/dev/recovery /recovery emmc defaults defaults

/dev/uboot /uboot emmc defaults defaults

/emmc@android /system ext4 ro,noatime wait

/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait

/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

/dev/misc-sd /preloader ext4 ro,noatime wait

/dev/nvram /nvram emmc defaults defaults

/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto

/devices/platform/mt_usb/musb-hdrc.0/usb1 auto vfat defaults voldmanaged=usbotg:auto

but it did not work.
[Android Software/Hacking General [Developers Only]] DaddyCapone:
Mt6752

Please support Mt6752 64bit cpu.

I have a THL 2015 with 1,7ghz octacore cpu 64bit. Android 4.4.4

I try your tool,but it says not compatible.

Thank you for this amazing tool!!!!!

It worket many times for me on my old mediatek phones (6582,6592....)

And again.....Thank you cor this tool!

and bro......let them talk....... ;) You are Dev master!!!!

and sorry for my baaaaaaaaaad english....:rolleyes:
[Android Software/Hacking General [Developers Only]] yuweng:
Guys, please, i need infos/ feedbacks, lots of them or i won't be able to help out . . . The porting tool will started off with adb shell cat /proc/cpuinfo & if it doesn't start with MT then it'll say for MediaTek devices only . . . Then if the porting tool detects modem partition(MTK clone) then it'll say not compatible for your device & Please read whole page 1 all over again

YOUR TOOL DOESN'T WORK . . .

i've seen this at many threads & also mentioned this many times at my other threads, most frequent reply is it doesn't work, you have given nothing at all to figure out what went wrong . . .

Please list out as many info as possible then it'll be easier to trouble-shoot & read EVERYTHING before hands-on, fyi, tested working on XP to Win10 Technical Preview . . .

What OS you are using on the PC & your MTK...

Did you disable UAC & Anti-Virus

Did you execute the porting tool at C: drive if you're using XP else then at your Desktop

Did you try Run as Administrator

Could it be some other software that you installed that interfere with the porting tool then uninstall it

Did you try it on other PC with other version OS or even different USB port

Try uninstall all previous adb driver -> Device Manager -> View -> Show hidden devices -> uninstall all ADB Interface/ Android device -> reboot -> re-install. Refer to screenshot -> View attachment 3018860

Did you try latest google ADB driver while for XP try this one
[Android Software/Hacking General [Developers Only]] DaddyCapone:
ok.....

My System.......

-Windows 7 Home Premium 64bit

-AntiVir is disablet

-UAC is also Disablet

-The newest ADB Driver are installed and working

but youre port tool says "The Recovery is too big,aborting!"

what does that mean? whant the tool mess up with me? :D

I hobe you understand Master Yuweng.:)
[Android Software/Hacking General [Developers Only]] yuweng:
Most MT6752 has a recovery partition of 16MB, there is something wrong with your device or a bug at the porting tool, attach the log.txt for further analysis . . .
[Android Software/Hacking General [Developers Only]] kirito9:
did anybody try this? i would like to to flash twrp, but i don't wanna mess up my phone