This is only for phones with MTK processor.
Master Carliv wrote
http://xdaforums.com/showpost.php?p=57584654&postcount=729
Master Carliv wrote
http://xdaforums.com/showpost.php?p=57584654&postcount=729
its so obvious & still you don't get it . . .
Step 1 - Download compatible CTRv2.5 according to your MTK filesystems
Step 2 - Unpack Step 1 & copy out the res folder & recovery binary
Step 3 - Unpack the working CTRv2.4 that you ported earlier & follow below Step 3
Hardware : MT6572
Model : LG-X135
Build number : LGX135-00-V10b-CIS-XXX-OCT-23-2014+0
Build date UTC : 20141023-033229
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V36.P7, 2014/08/13 19:04
Kernel v : 3.4.67 (u@u-desktop) (gcc version 4.7 (GCC) ) #1 SMP Thu Oct 23 11:30:07 CST 2014
Mt6572.....i think it has locked bootloader.....did u check whether ur device has locked bootloader or unlocked?hi guys and thread owner..
i tried to add custom recovery (with ur software) to lgx-135, everything went good but not power on device and not entering to recovery mode..
Code:Hardware : MT6572 Model : LG-X135 Build number : LGX135-00-V10b-CIS-XXX-OCT-23-2014+0 Build date UTC : 20141023-033229 Android v : 4.4.2 Baseband v: MOLY.WR8.W1315.MD.WG.MP.V36.P7, 2014/08/13 19:04 Kernel v : 3.4.67 (u@u-desktop) (gcc version 4.7 (GCC) ) #1 SMP Thu Oct 23 11:30:07 CST 2014
anyone has any custom recovery for this device..? i have org recovery.img file.. if anyone create for me i can add it..
tia..
Alex2ap
When said "CTR 2.7 is out" do you emna "Carliv recovery 2. & 3.0" is out?
Please take care that with device with Android 4.2.x you can use MTKDroid to generate on the fly the recovery for tour device startingfrom Carliv Recovery 2.7 base with the resolution of your device.
Old ToolAdded 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....
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...
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 . . .
Any bugs report here . . .
----------------------------------------------------------
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 . . .
Any bugs report here . . .
Updates
Thanks to surfturtle for reporting . . .
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 . . .
----------------------------------------------------------
Added on June 17, 2014
Users using XP & 720x1280 MTK devices use this fix . . .
----------------------------------------------------------
Added on July 01, 2014
CTRv2.5 refer to here . . .
----------------------------------------------------------
Notice to annoying n00bs & newbies
Most of your questions are already answered on this thread so pls read it...
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...
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...
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...
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
@MiLToS_666Thank you for the reply!
I have already tried to use the recovery.img I extracted from my device (the modified one with CWM 5.x, the size is 6MB) and use it with michfood-Port-CWM-6.0.3.0-BM.
The whole procedure completes successfully but the resulting recovery.img is 6.04MB and I can't use it with SP Flash Tool because it's too large and will overlap.
What am I doing wrong here?
/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