[GUIDE] How To Root Micromax Canvas Xpress 4G Q413-CWM/TWRP

[aravazhi_mdr]

How to root Micromax Canvas Xpress 4G?​

Micromax Canvas Xpress 4G Q413 is running on Android LOLLIPOP and using Mediatek chipset MT6735P

How to ROOT Micromax Canvas Xpress 4G (Q413)?

1.One-Click-Root apps - FAILED
2.Porting ClockWorkMod using MTK droid tools - FAILED
(Because that does not support MT6735P chipset)

So What is NeXt?
Porting ClockWorkMod(CWM) recovery to this mobile i.e Compiling recovery from source
So we can flash superSU flashable zip through CWM to get ROOT access.

What I did exactly is ported ClockWorkMod(CWM) recovery to Micromax Canvas Xpress 4G

Now focus on What should you do to ROOT

1.Flash CWM using SP flash tool (Also TWRP is available)
2.Flash "UPDATE-SuperSU-v2.46.zip" ZIP package through ClockWorkMod (CWM).

Very EASY...

What do you need?

1.A PC/Laptop with windows 7/8/8.1/10
2.Drivers for Micromax Canvas Xpress 4G (Use link in STEP 6)
3.SP Flash Tool
4.UPDATE-SuperSU-v2.46.zip
5.Micromax Canvas Xpress 4G mobile
6.All Files From This Link
7.ADB and FASTBOOT drivers (Use link in STEP 6)
8.USB VCOM drivers (open READ_ME.txt from the link in STEP 6)

Preparation...

1.Goto Settings >> About phone and tap continuously Build Number until you see "You are now a developer" message.
2.Now get back to settings and click Developer Options
3.Now turn on "Allow OEM Unlocking" and "USB Debugging"

1.Flashing CWM

i).Open SP flash tool and load scatter file (from the link)
ii).Locate recovery-cwm.IMG(from link) in recovery,uncheck all and check only recovery
iii).Pull out your battery and insert it,DON'T TURN ON YOUR PHONE
iv).Click "Download" in SP Flash Tool and connect your phone to PC using USB cable
v).You will promoted with a big green tick.Done

2.Flash "UPDATE-SuperSU-v2.46.zip" ZIP package

i).Place "UPDATE-SuperSU-v2.46.zip" in your sd card
ii).Turn off your device

You may also use the following code while your phone is turned on

 adb reboot recovery

and skip to STEP (v)

iii).Press "Power" & "Volume Down" until you see some options
(Here "Volume Down" = DOWN and "Volume Up" = OK )
iv).Choose Recovery by pressing "Volume Up"
v).In ClockWorkMod recovery choose "Install ZIP from sdcard"
(Here "Volume Down" = DOWN "Volume Up" = UP and "Power" = OK )

You may also choose Install From Sideload

 adb sideload path/to/UPDATE-SuperSU-v2.46.zip

vi).Now locate "UPDATE-SuperSU-v2.46.zip" in your sd card and press POWER KEY
vii).After installition choose REBOOT.........Done!

All done..,you have rooted your device.:highfive::good:
If u have any problem post here.

EDIT: TWRP Added.
It is RECOMMENDED To Use it...
Check link #3 below"

Credits

[+]Mr.ChainFire for SuperSU
[+]Mr.Koushik Dutta for original ClockWorkMod
[+]TWRP Team
[+]All developers on XDA for wonderful guides and support
Thanks and salute to them

Download Links
1.SP Flash Tool
2.UPDATE-SuperSU-v2.46.zip
3.All Files From This Link

 

[aravazhi_mdr]

Take a note....

Don't use scatter file from the stock rom posted on androidmtk.com
This ClockWorkMod can be easily ported to other devices running on MT6735P/M chipset by replacing kernel.

 

[pbababab]

Awesome JOB...Love it

Don't use scatter file from the stock rom posted on androidmtk.com
This ClockWorkMod can be easily ported to other devices running on MT6735P/M chipset by replacing kernel.

Awesome job...didn't know someone would get a recovery for this phone...actually most of mtk built phones are neglected as mtk doesn't release Sources or some other issue...But Thank You....any hopes of having cyanogenmod ROM for this device?

 

[aravazhi_mdr]

Awesome job...didn't know someone would get a recovery for this phone...actually most of mtk built phones are neglected as mtk doesn't release Sources or some other issue...But Thank You....any hopes of having cyanogenmod ROM for this device?

I don't hope anyone will post cyanogenmod ROM for this device (As of now)

We have to port it ourself.
I think Xposed installer will help our phone to rock...

 

[Nangshi]

Will the device have otg support after the root?????

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

Will the device have otg support after the root???

 

[aravazhi_mdr]

May be

Will the device have otg support after the root?????

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

Will the device have otg support after the root???

if the kernel supports OTG,there is a way HERE


But I don't know if the kernel supports OTG

If u have a otg cable,

U can root and try this

don't fear to root your device

because I have posted a untouched stock recovery here....

So don't worry u are safe...

 

[glasseffects]

Im glad, I found this post! Please help me with CWM for Q412. Can I use the recovery posted here? Or can I use the Scatter file to grab recovery from the phone?

Thanks!

 

[aravazhi_mdr]

Im glad, I found this post! Please help me with CWM for Q412. Can I use the recovery posted here? Or can I use the Scatter file to grab recovery from the phone?

Thanks!

You should not use this scatter and recovery

1.Create scatter based on my scatter....


Connect your phone with pc Your device
Make sure you have configured adb (Android Debugging Bridge)

Now use following command

adb shell cat /proc/partinfo

you will get "start address" and "size" of every partitions
compare these results with my scatter and replace the values.
Try to grab recovery using MTK Droid Tools or use 2nd step


2.Unpack my "recovery.img" using "Carlive image kitchen"

now repack it with your own kernel
flash it using sp-flash tool

 

[glasseffects]

aravazhi_mdr,

Thank you for the little tutorial! I followed it but ended up with the same error whereby SP Flash Tool tells me that the flashing has failed, perhaps I missed something crucial. So I tried to revert to the stock firmware again but even that ends with error. But this isn't the real problem. This phone has a non-removable battery. Once something has been flashed, the phone remains in some mode and can not be rebooted. I wish the battery could be removed. I have to wait for the battery to drain untill the phone becomes operable.

This is the error I recieve if I flash anything with SPFT in any mode but 'Format All + Download':

Please suggest a solution.

PS: I have stock firmware which inclides recovery.img and boot.img. If I flash this firmware, the phone boots fine, but if I unpack and repack any of these with CarlivImageKitchen, results in the same error as above!

 

[aravazhi_mdr]

aravazhi_mdr,

Thank you for the little tutorial! I followed it but ended up with the same error whereby SP Flash Tool tells me that the flashing has failed, perhaps I missed something crucial. So I tried to revert to the stock firmware again but even that ends with error. But this isn't the real problem. This phone has a non-removable battery. Once something has been flashed, the phone remains in some mode and can not be rebooted. I wish the battery could be removed. I have to wait for the battery to drain untill the phone becomes operable.

This is the error I recieve if I flash anything with SPFT in any mode but 'Format All + Download':

Please suggest a solution.

while flashing maintain your charge below 15%....
so you don't need to wait 4 long to drain battery

I think you are using an old version of SPFT.
Grab the new one from androidmtk.com

don't touch boot loader...
coz many people stuck here...

gud luck
next time attach log file...

 

[aravazhi_mdr]

unpacking with carliv image kitchen

use normal android unpack option

if u have error choose mtk unpack option

 

[glasseffects]

while flashing maintain your charge below 15%....
so you don't need to wait 4 long to drain battery

I think you are using an old version of SPFT.
Grab the new one from androidmtk.com

don't touch boot loader...
coz many people stuck here...

gud luck
next time attach log file...

Thanks aravazhi_mdr,

I downloaded the recent version of SPFT but consistently reporduced the same error . CarlivImageKitchen, on the other hand does not unpack the recovery citing that "it has been packed with an unknown compression menthod". While the same can be unpacked through the regular Android option. Repacking is possible but reproduces the same error upon flashing.

I have attached the log with this post. Error 4008 suggests that SPFT wasn't able to download the flash file but I can't say beyond that.

For now, I have been flashing with almost no battery backup so I won't have to wait. Do you think this is also a design flaw when they overlooked the obvious?

Please guide me further.

Thanks.

 

[aravazhi_mdr]

OK.
You don't have problem with stock ROM.
But the repacked recovery failed to flash..
am I right?

Unpack your stock recovery (from stock ROM) and my recovery-CWM.IMG (link on 1st post) using regular android unpack.....

copy the following files from your stock recovery to recovery-cwm

1.recovery.img-base
2.recovery.img-board
3.recovery. img-cmdline
4.recovery.img-kernel
5.recovery.img-kernel_offset
6.recovery.img-pagesize
7.recovery.img-ramdisk_offset
8.recovery.img-ramdisk-compress
9.recovery.img-tags_offset


Now repack recovery-cwm using REGULAR ANDROID REPACK option and flash it....

 

[aravazhi_mdr]

Compare /proc/partinfo and your scatter from androidmtk.com

 

[glasseffects]

aravazhi_mdr

Glad, with your help the recovery now works, although I have to disconnect the phone before SPFT could give an error (it still does give the same 4008 error). I would be thankful if you could help me with the following two issues:

1. The recovery works but somehow it can't mount internal storage. I can flash zips like supersu.
2. The second issue relates to the Format + Download option in SPFT which I just came to know also wipes IMEI. So I'm without any network now . I tried the AT+ command method but it didn't work even if I deleted nvram. Elsewhere there's a tutorial about NV Tools but that requires me to have a file which isn't there in the Zip folder of the stock firmware.

Im trying to resolve these but I seek your help once again!

 

[aravazhi_mdr]

The command is "AT +" not "AT+"

unpack your stock recovery and goto ramdisk/etc/recovery.fstab

compare this with your modified recovery's recovery. fstab file......

this recovery.fstab file has details about where to Mount which block.....


AT + Command will work...

The command is "AT +" not "AT+"

AT +EGMR=1,7,”"

 

[glasseffects]

aravazhi_mdr,

Thank you for your continued support. I hope I'm not bothering you much here. As far as the progress is concerned. I tried to compare and replace certain parameters but the diversity of these two files has kept me thinking. So each time the results were the same, the internal SDCARD still remains inaccessible. I've attached the contents of these files here: Please take a look.

Q412 recovery.fstab

boot       				  /boot       emmc      defaults        defaults
/dev/block/mmcblk0p2      /cache      ext4      defaults        defaults
/dev/block/mmcblk0p3      /data       ext4      defaults        defaults
misc      				  /misc       emmc      defaults        defaults
recovery  				  /recovery   emmc      defaults        defaults
/dev/block/mmcblk0p4      /sdcard     vfat      defaults        defaults
/dev/block/mmcblk0p6      /system     ext4      defaults        defaults

Q413 recovery.fstab

# Android fstab file.
#<src>           <mnt_point>         <type>    <mnt_flags and options>                 <fs_mgr_flags>
# 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

/dev/block/platform/mtk-msdc.0/by-name/system     /system      ext4   ro						         wait
/dev/block/mmcblk0p3                              /data        ext4   noatime,nosuid,nodev,noauto_da_alloc,discard               wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache      /cache       ext4   noatime,nosuid,nodev,noauto_da_alloc,discard               wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1   /protect_f   ext4   noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc   wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2   /protect_s   ext4   noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc   wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/nvdata      /nvdata             ext4      noatime,nosuid,nodev,noauto_da_alloc,discard        wait,check,autoformat

#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist    /persist     ext4   noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc   wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom     /custom      ext4   ro                                                         wait
/storage/sdcard0                                    auto      vfat      defaults        voldmanaged=sdcard0:auto
/devices/mtk-msdc.0/11240000.MSDC1  auto      vfat      defaults        voldmanaged=sdcard1:auto
/devices/platform/mt_usb                auto      vfat      defaults        voldmanaged=usbotg:auto

Please help me wich code requires editing. This would complete the task of complete!

On the other hand I went ahead with SN Writer tool and successfully restored the IMEI codes.

Thanks again for your help!

 

[aravazhi_mdr]

Goto /dev/block and know something about your blocks,which is your internal storage.........

however you can use adb commands to push flashable zips.......

 

[aj38584]

Please also share for canvas xpress a99

Sent from my Moto G using Tapatalk

 

[aamir9191]

You should not use this scatter and recovery

1.Create scatter based on my scatter....


Connect your phone with pc Your device
Make sure you have configured adb (Android Debugging Bridge)

Now use following command



you will get "start address" and "size" of every partitions
compare these results with my scatter and replace the values.
Try to grab recovery using MTK Droid Tools or use 2nd step


2.Unpack my "recovery.img" using "Carlive image kitchen"

now repack it with your own kernel
flash it using sp-flash tool

Please create CWM recovery or any other recovery .img file for q412 users. pls provide us a simple link to download recovery file, so that we can flash it using sp tool or rashr, like u done for q413 users
pls do the needful,
thanks