[RECOVERY] Various recoveries for THL T100S and THL T11

[RECOVERY] Various recoveries for THL T100S and THL T11 - Miscellaneous Android Development

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
Here are several recoveries compiled from source by me, for THL T100S, octacore mt6592. All are fully functional.
and here are several recoveries compiled from source by me, for THL T11, octacore mt6592. Need to be tested.
I know that there are already compiled TWRP recoveries, same versions, for this phone, but my versions are a little bit different. For example in my versions, both sdcards are mounted at the same time in USB Mass Storage mounting, not one at a time as in existent twrp recoveries. And there are some other small changes.
All can be installed by MobileUncleTools or SPFlashTools.

Could you please help me, how to port your recoveries to T11?
I've tried the manual and automatic modes, on the desktop W8.1x64, no errors but the recovery not showed up.

Indiant said:
Could you please help me, how to port your recoveries to T11?
I've tried the manual and automatic modes, on the desktop W8.1x64, no errors but the recovery not showed up.
Click to expand...
Click to collapse
Hm, I see there are some similarities between THL T100S and T11, but the device resolution is different, and so for recoveries between point 2 to 5 that might be a problem, but number 1 should work... If you can give me a stock recovery I will try to build again for your device, when I will have time. Nevermind. I found it.

carliv said:
Hm, I see there are some similarities between THL T100S and T11, but the device resolution is different, and so for recoveries between point 2 to 5 that might be a problem, but number 1 should work... If you can give me a stock recovery I will try to build again for your device, when I will have time. Nevermind. I found it.
Click to expand...
Click to collapse
It is the same phone except resolution (720x1280), the camera, but it is not matter, and the 16Gb space.
Yes, the 1st works great! The second is working too, but the touch is misaligned.
Thank you for the great recoveries and your work!

Indiant said:
It is the same phone except resolution (720x1280), the camera, but it is not matter, and the 16Gb space.
Yes, the 1st works great! The second is working too, but the touch is misaligned.
Thank you for the great recoveries and your work!
Click to expand...
Click to collapse
Have you tested number 2 from my new list, for T11? Can you make a photo about the problem (touch misaligned) or to provide more details, because version 2 is not full touch, and the actions are taken by swipe (up/down/left/right). If you touch a menu row the highlight will move up or down, depends how it will be interpreted as swipe up or down.

carliv said:
Have you tested number 2 from my new list, for T11? Can you make a photo about the problem (touch misaligned) or to provide more details, because version 2 is not full touch, and the actions are taken by swipe (up/down/left/right). If you touch a menu row the highlight will move up or down, depends how it will be interpreted as swipe up or down.
Click to expand...
Click to collapse
Yes, I did. I mean the four buttons on the screen are not working. The swipe up and down are working ok. (up is up and down is down)

T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
TWRP-s are not booting.

Indiant said:
T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
TWRP-s are not booting.
Click to expand...
Click to collapse
For Carliv Touch Recovery v-2.5, check to see if the backup format is same as before, if it was tar then set to tar and restore, if it was tar gz set to tar gz.
For twrp I'm affraid I can't help you more without the phone.

carliv said:
For Carliv Touch Recovery v-2.5, check to see if the backup format is same as before, if it was tar then set to tar and restore, if it was tar gz set to tar gz.
For twrp I'm affraid I can't help you more without the phone.
Click to expand...
Click to collapse
Hi!
I tried all mode (tar, tar+ gzip, and the third mode ) without success. "Error while flashing uboot image"
It can restore only own backup. :silly:

I have instaled this one with uncle tools
https://www.dropbox.com/s/u2ixf78a2krl8fd/recovery.img
Sent from my thl T100S using XDA Premium 4 mobile app

Indiant said:
T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
Click to expand...
Click to collapse
kamillo said:
Hi!
I tried all mode (tar, tar+ gzip, and the third mode ) without success. "Error while flashing uboot image"
It can restore only own backup. :silly:
Click to expand...
Click to collapse
Of course it does, because probably those old backups don't contain uboot.img. Not every recovery for mtk do backup also uboot. Even I introduced that since version 2.2 I guess, because I saw it will perform better if uboot is refreshed during restore. That's the reason I put lk.bin(uboot) in my custom ROMs too.
The solution is to restore those backups with advanced restore one by one: boot, system, data.
underboy2008 said:
I have instaled this one with uncle tools
https://www.dropbox.com/s/u2ixf78a2krl8fd/recovery.img
Sent from my thl T100S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't understand. Why are you telling me this? If it's one of mine, someone tooked from here and uploaded there, if it's not (there are other versions on the internet) I don't see the point.

I'm glad to have CTR2.5 for T11. :good:
But why smallers the buttons? (I know it is new design, but there are a lot of unused space left...)

Indiant said:
I'm glad to have CTR2.5 for T11. :good:
But why smallers the buttons? (I know it is new design, but there are a lot of unused space left...)
Click to expand...
Click to collapse
Well, you are the first, and thl t100s users too. I didn't release yet that version.
The new UI is focused on better space management. I know in your big screen it is much space left but in a 240 or 480px screen this is better, and I have to think an unified solution for everyone. This new UI will make menus accessible even in devices with only 2 points of touch, in which swipe wont work.

The new Backup is awesome. So detailed. I like it!

Carliv Touch Recovery v-2.5 and old Backups (uboot.img missing solution)
1. create a new backup and from that copy uboot.img file to old backup folder
2. from nandroid.md5 file copy the uboot.img row to old nandroid.md5 file with notepad++
Problem solved.

hello guys i hope you can help me.
i tryed to installed xposed installer and my phone wont boot up anymore.
i get the splash screen but nothing after it.
i can get to recovrey but it doesnt do anything when i press wipe data or catch.
when using SP flash tool i try to load scatter file and i get this error "error initializing scatter file failed"
anyone can help me? =/
EDIT
i meanaged to run sp tool in a diffrent version one. but it wont reconzie phone. i click download and then connect phone but i keep seeing at bottom of sp tools "seraching" and nothing happens (exept of noise of a connecting usb from computer...)

itzikd1 said:
when i press wipe data or catch..
Click to expand...
Click to collapse
..press Factory reset instead (Carliv sry for off) itzikd1,pls do not answer to this

@carliv
Could you update the TWRP to the latest 2.7.1.1/2.7.1.2 (bugfixes)?
Which version (6.0.4.4?) is CWM?
Why on TWRP website (http://teamw.in/project/twrp2) there is no reference about yoour TWP recovery?

HI Carliv.
Could you update TWRP for T100S at 2.8.4.0?

bovirus said:
HI Carliv.
Could you update TWRP for T100S at 2.8.4.0?
Click to expand...
Click to collapse
I don't have the phone. When I built these recoveries I had one from a friend who wanted me to build a recovery for him, but now he doesn't have it either (sold). I can't do it without the phone to test the result first.

Related

[CWM] CWM-based Recovery for RK3188/RK3066/RK2928/RK2926/RK2918/RK2906

Mod Edit: Link removed
all credit goes to original CWM author koush and all its contributors. but they have no responsibility for this CWM-based Recovery. use this CWM-based Recovery at your own risk.
this CWM-based Recovery can write raw MTD partition such as kernel, boot, and recovery on RK3188, RK3066, RK2928, RK2926, RK2918, and RK2906 devices without any problem. this can be installed without Windows.
if you want to install zip with edify script which writes something to raw MTD partition, you have to use update-binary and/or flash_image included in this CWM-based Recovery image.
please see my site for detail.

* Known issues (2013/2/11)
- timestamp
backup may be named as 1970-01-01.xx.xx.xx. it's just a directory name on SD card. please rename it.
- dump_image
it says "mtd: read error (No such file or directory)" at the end. please ignore it, it should not be a problem.
* How to controll
- mouse
move up/down: up/down
left click: select
right click: back
- keyboard
cursor up/down: up/down
cursor left/enter: select
cursor right: back
- touch screen
swipe up/down: up/down
swipe left: select
swipe right: back
- button
volume up/down: up/down
power: select
back: back
- remote controller
up/down: up/down
left/ok: select
back: back

* about tools to make device specific image
you can use any tools which can be used to make custom rom for Rockchip devices. I'm using rkunpack, rkcrc, unpackbootimg, and mkbootimg.
if you don't know how to make custom rom for Rockchip devices, please ask google. many developers are already making custom rom for Rockchip devices, many information is already floating around.

where to download rkflash, rkflashtool, or RKAndroidTool.exe
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:

magnemann said:
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:
Click to expand...
Click to collapse
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,

fun_ said:
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,
Click to expand...
Click to collapse
Thanks alot for info! I'll try 'from root shell' method. Seems like the easiest way. :laugh:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.

magnemann said:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.
Click to expand...
Click to collapse
I only have a MK806. it has a button to boot recovery and bootloader. but sorry I don't know about other device...
if you are sure there is no button, then you need to flash some misc.img with USB flash tool.
sorry, I'm busy a little. please search about RKAndroidTool for RK3066 on google.

I got a report on another forum, this CWM works fine on MK808B.

backup will be named as "1970-01-01.xx.xx.xx" on (at least) MK806 and MK808B.
I'll investigate it. for now please rename it from PC or any explorer app. it's just a directory name on SD card.

Ah, a new cwm for my rk2918 device.
Thanks to fun_ stuff.
JDfense

http://androtab.info/clockworkmod/rockchip/
2013/1/19
update updater-script
add images for MK802III and UG007
latest stock rom for MK802III and UG007 has /system/etc/install-recovery.sh. it restores stock recovery on every boot. then, you need to disable it e.g.
Code:
chmod 644 /system/etc/install-recovery.sh
otherwise, installed CWM is erased and stock recovery is restored after reboot.
I added above code into updater-script in all my CWM.zip. if you install CWM.zip from CWM or adb sideload, it will be done automatically.
if you flash recovery.img from shell or rk tools, you need to do it manually.
if you update your device, install-recovery.sh may be re-enabled. then, you need to disable it again.
----
at this time all images are updated, but only updater-script in zip is changed. if you already installed CWM, no need to install this version.

hi fun!
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device? thanks man!!

onelovekir said:
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device?
Click to expand...
Click to collapse
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side

http://androtab.info/clockworkmod/rockchip/
2013/01/20
CWM.zip can be installed from stock recovery (it may not work on some device)
if you already installed CWM, no need to install it.

fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
there is some take apart pics somewhere...let me see if I can find them. thanks for your help and I will test the new build today.
and oh yeah btw...X5 is very nice

for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.

fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.

Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.
Click to expand...
Click to collapse
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
HTC EVO LTE with Tapatalk

onelovekir said:
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.
Click to expand...
Click to collapse
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
onelovekir said:
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
Click to expand...
Click to collapse
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!

Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!
Click to expand...
Click to collapse
Yes the up/down/left arrows work but not the right (i think cuz we don't need a fourth function), but ONLY (so far) on the stock remote that comes with the X5. Yes changing to update.zip works and I will get you the key test results in a little bit.
Thanks again for your work!
HTC EVO LTE with Tapatalk

Telsda A198

I bought a chinese phone Telsda/TSD A198 . The firmware reports it as an MT6589 CPU but the computer reports it as a spreadtrum phone. I need to root the phone to get rid of some apps on this to make space. Also without rooting is there anyway to backup the stock rom on my phone before I mess up to root? I have seen a method on XDA but that requires root. Now I am trying to backup to get to rooot !!!! Also I have also researched researchdownload but without a ROM backup and not knowing which CPU model to flash its impossible to it right. I also looked into mtkdroidtools and it tells me "unstructured rom backup not possible" , so I am guessing its a fake MTK CPU that is being reported by tweaking the firmware.
This is the link to the phone
http://www.aliexpress.com/item/New-...3-MTK6589-4-0-INCH-smart-phone/879312434.html
Any help is appreciated.
Thanks

I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.

Villis1251 said:
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Click to expand...
Click to collapse
Ok, first my honest suggestion dont buy this phone it has pathetic performance. For the same price go for a real MTK6577 dual core. ANyways below are the answers to your question
> Real CPU frequence seems to be 1GHZ
>Mali 300 GPU
>no 3G
>no GPS
>256MB RAM and 256 MB ROM
>I am not sure if its real JB and I cant figure it out but it says JB 4.2.1 and the kernel is 2.6.35.7 and hence I guess its a fake JB. The funny part is under baseband version it says "MT6589 1.5GHZ quad cores" !!!! offcourse it means the firmware/build.prop has been tweaked and is reporting false values. Also when I ran Antutu it gives a score of about 3500 which is useless when compared to what is required to run games ..etc. I hope I have helped.

Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.

custom recovery
Villis1251 said:
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
Click to expand...
Click to collapse
Finally I was able to stitch a ROM, using bits and pieces from different sources and its perfectly working. I only need to build a CWM recovery image based on the recovery image I have attached. Can someone help me do that? so that I can do a nandroid and ump my rom in case someone needs to recover their telsda A198

I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?

aspirus said:
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
Click to expand...
Click to collapse
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.

hel me please!!!
braindia said:
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
Click to expand...
Click to collapse
braindia hello ... I bought the same phone and I have problems with the sims do not have to call or receive coverage ..... could you explain you did and how you did it?
there say that you put android 4.0 not work quite right? ... greetings from chile

Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:

aspirus said:
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
Click to expand...
Click to collapse
ok looks like lot of people have issues with this phone. Its a junk phone, all fake stuff on it. ANyways I will upload the firmware images and then you guys can use those to flash on your phones. Below is what I have done
1> Patched a 4.0.4 ROM which works perfectly
2>Removed useless preinstalled apps
3>rooted
4>Perfectly working dual sim,GPRS,WIFI,Camera,Camcorder .,..etc etc
4>The issue is with the IMEI, because of the way its stored you guys will need to use your own NV files.
The only thing I havent been able to do is get a working CWM, but you dont need it as you can flash the firmware images using researchdownload.

Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.

working firmware files
aspirus said:
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
Click to expand...
Click to collapse
Here you go, you flash at your own risk. If there are bricks/issues you are responsible for your own device.(Standard disclaimer) . I have uploaded all the files except system and NV, system image is kind of big and I am trying to figure it out where to upload it.. You dont need to worry about NV unless you completely erased the flash(never erase the complete flash or format it). If you havent done so then you are good to go.
Please google to find researchdownload and use it to flash the attached files. I wont be able to write the tutorial on using researchdownload so google is your friend.
I have also uploaded the gapps zip which will get you up and running with google play store. You need root to copy these files directly into system/apps folder.
I will be able to upload a system file which works, not the patched one with google play store, root ...etc etc . You do that on your own, I will help you do it.
Thanks !

Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.

aspirus said:
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
Click to expand...
Click to collapse
your phone is probably not detected due to 2 reasons
1> windows disabling non signed driver.. if thats the issue while you start the PC keep hitting F8 you will be shown various options
Select disable windows driver signature enforcement
2> Second reason is you need to add an entry in adb_usb.ini file I think its 0x1782 which is for SPRD enumerator. There are tons of links for this one of which is
http://forum.xda-developers.com/showthread.php?p=37271476

Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?

aspirus said:
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
Click to expand...
Click to collapse
getting root is simple, flash a CWM I have attached one, please note this does not work but it works enough to get you root. follow the below steps
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
4> perform mount /system and then exit shell
5> push su binary & busybox directly to /system/bin (from the command prompt using adb push)
6>change permissions for su & busybox to make them runnable
7> exit from the shell and reboot
8> do adb install superuser.apk(optional this can be done later)
thats it you have su, and then you can sideload the superuser apk or you can do step 8 as above. Once you have rebooted and verified that you indeed have superuser you can flash the stock recovery back on the phone.
Note note note : The CWM recovery image is only for you to get root and it doesnt work and doesnt show the normal CWM options... you have been warned. You should flash your old recovery/stock recovery after you have achieved root.
Also can you give me the stock recovery image so that I can build a working CWM out of it. I overwrote mine and now stuck with another recovery which works but is not for this phone.
Thanks

:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.

aspirus said:
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
Click to expand...
Click to collapse
Hmm... I am not sure what is the issue please try attached drivers and pray that they work . use either 64bit or 32bit depending on your OS.
Also you said you have the firmware can you upload it ? I can do something more with the stock/original firmware, so please upload it

I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4

aspirus said:
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
Click to expand...
Click to collapse
Thanks ... I know this phone is a waste of time and money both. I am just using this phone as an experiment platform knowing fully well that this piece of junk will die anytime.

[xxxrom][14-08-2013] micromax canvas 4 - a210-stock based custom rom (jb)

Hallo,
I was trying to find custom ROMS for the Canvas 4 -A210 Micromax mobile in this forum and my search yielded one custom Rom which I experimented and met with the difficulties.
I thought I can try some other custom ROM of the same type or equivalent type mobiles. Luckily I came across the "Thread By: bgcngm" which normally read regularly.
I picked up the V3.0MOD Rom and edited and and experimented with the A210 canvas4. Luckily it gave me a good performance except that of the "Video call" facility did not show up. My IMEI was also vanished. This happended to me on previous experiments also.
Hence who ever is going to use this Custom Rom has to back up there IMEI and restore it using Mobileuncle Tool or what ever they feel easier.
I submit and reiterate here all the credit for this ROM to "bgcngm" and also request him further help us to some more modification to ease the application. I am only a learner and new entrant. Based on my use below I provided the details: You should have a Rooted Phone..
1. Find here the CWM recovery that was obtained using the MTKDroid Tool 2.4.8.
2. Use SPFT above 119. I have used 139.
3. Download the stock ROM and click on the Scatter file. This will load up all the files required for the stock rom. Un-**** all the items. Now click preloader and take your curser to the recovery. Click it and point it to the extracted CWM recovery you have downloaded from this.
4. This will install the CWM recovery 5.5.0.4 to your mobile. Also you can try with Mobileuncle tool to install the cwm recovery.
5.Download and copy the Custom Rom to your external or internal sdcard. The url is here:
MMX-XXX-JB_210_ROM => https://docs.google.com/file/d/0B6mi3aQy8tz9TVlJWWJ5SnJMRDA/edit?usp=sharing
6. Before installing please back up every thing using the CWM recovery.
7. Using CWM recovery you select the custom ROM form the location you have copied and install from the AROMA installer.
8. Please back up your IMEI, some time it may be required if you loose yours, this can be restored using Mobileuncle Tool.
9. It is advisable to use custom installation and select what ever application you like.
10. Install and enjoy.
If you like my efforts, please hit thanks.
with best wishes
Please wait Camera is not seen/ working I am recasting it. I am trying. An port it tonight. Please wait

puduraja said:
Hallo,
I was trying to find custom ROMS for the Canvas 4 -A210 Micromax mobile in this forum and my search yielded one custom Rom which I experimented and met with the difficulties.
I thought I can try some other custom ROM of the same type or equivalent type mobiles. Luckily I came across the "Thread By: bgcngm" which normally read regularly.
I picked up the V3.0MOD Rom and edited and and experimented with the A210 canvas4. Luckily it gave me a good performance except that of the "Video call" facility did not show up. My IMEI was also vanished. This happended to me on previous experiments also.
Hence who ever is going to use this Custom Rom has to back up there IMEI and restore it using Mobileuncle Tool or what ever they feel easier.
I submit and reiterate here all the credit for this ROM to "bgcngm" and also request him further help us to some more modification to ease the application. I am only a learner and new entrant. Based on my use below I provided the details: You should have a Rooted Phone..
1. Find here the CWM recovery that was obtained using the MTKDroid Tool 2.4.8.
2. Use SPFT above 119. I have used 139.
3. Download the stock ROM and click on the Scatter file. This will load up all the files required for the stock rom. Un-**** all the items. Now click preloader and take your curser to the recovery. Click it and point it to the extracted CWM recovery you have downloaded from this.
4. This will install the CWM recovery 5.5.0.4 to your mobile. Also you can try with Mobileuncle tool to install the cwm recovery.
5.Download and copy the Custom Rom to your external or internal sdcard. The url is here:
MMX-XXX-JB_210_ROM => https://docs.google.com/file/d/0B6mi3aQy8tz9TVlJWWJ5SnJMRDA/edit?usp=sharing
6. Before installing please back up every thing using the CWM recovery.
7. Using CWM recovery you select the custom ROM form the location you have copied and install from the AROMA installer.
8. Please back up your IMEI, some time it may be required if you loose yours, this can be restored using Mobileuncle Tool.
9. It is advisable to use custom installation and select what ever application you like.
10. Install and enjoy.
If you like my efforts, please hit thanks.
with best wishes
Please wait Camera is not seen/ working I am recasting it. I am trying. An port it tonight. Please wait
Click to expand...
Click to collapse
Man, does the recovery works perfectly in your canvas4 ? have you tried it?
Reply soon

sexydjb said:
Man, does the recovery works perfectly in your canvas4 ? have you tried it?
Reply soon
Click to expand...
Click to collapse
Many time i used the the recovery obtained through Mtk Droid tool and it is working fine. I used the patched recovery provided by MTK Droid Tool.
This worked fine. But the recovery saved inside the mobile in the clockworkbackup created some problem.
Patched recovery provided in the recovery file in the MTK DROID Tool is functioning good and I am using that currently. Whether it is perfect or not I do not know. In what contact you are asking i could not guess.
It suffice the need and operation is normal and good like many other which I have used in the past.
If you meet with any difficulties. You write in this forum. I or any one
will reply.
Sent from my A210 using xda app-developers app

CAN U MAKE a video for INSTALLING CMW i am new to canvas PHONES

Shane said:
CAN U MAKE a video for INSTALLING CMW i am new to canvas PHONES
Click to expand...
Click to collapse
I can narrate step by steps. To make a video I may have to borrow my son's mobile.
Could you please wait for a day or two. Now I am out of Chennai. And after 2 days only I will return.
Sent from my A210 using xda app-developers app

I will try to give you the screen shots from laptop first if you could not be able to follow I shall try the video.
Screen copy is also possible only after I reach Chennai, may be day after.
Kindly bear with till then
Sent from my A210 using xda app-developers app

NO PROB I will give U THE SS just upload here OOK

screen pictures how to install CWM Recovery to Canvas 4
Shane said:
NO PROB I will give U THE SS just upload here OOK
Click to expand...
Click to collapse
Gentle man,
Please find the screen shots for installing the CWM recovery on Canvas 4
1. Download keep ready the SP_Flash_Tool_exe_v3.1312.0.139.zip extract it to a separate folder on your desk top.
2. Double click the blue coloured .exe file as shown below
http://forum.xda-developers.com/attachment.php?attachmentid=2201502&stc=1&d=1376999658
3.Immediately the Smart Phone Flash Tool will pop up. You click on the scatter loading row by taking the courser there, AS SHOWN IN THE SCREEN SHOT BELOW.
http://forum.xda-developers.com/attachment.php?attachmentid=2201517&stc=1&d=1377000012
4. Once you clkick the scatter file your window will ask for the location of the scatter file from the ROM. Hence you should have the SPFT flashable rom file reaqdy in hand. Hope you will be having one or you google it in this from search and down load and keep ready.
5. Take your curser to the MT6589-Android_scatter_emmc.txt file as shown in the picture below and click it.
http://forum.xda-developers.com/attachment.php?attachmentid=2201539&stc=1&d=1377000609
6. Immediately after clicking, the tool will download all the required files from the folder and a tick mark will be seen against the files name as seen here
http://forum.xda-developers.com/attachment.php?attachmentid=2201546&stc=1&d=1377000844
7. Now un-tick all the boxes except the preloader file. Then go to Recovery file and tick it. Now do a sigle click of the recovery file. A window eill pop up and ask for the location of the file in your stock Rom folder. Now take your courser to the location where you have saved your CWM recovery file and click/ open or do a double click. The stock recvery file will be replaced by the CWM Recovery file as seen in the shot below.
http://forum.xda-developers.com/attachment.php?attachmentid=2201559&stc=1&d=1377001277
8. Similarly if you want you can upload the patched Boot.img file also. It has been recommended by the senior developer of the MTK Tools to flash the patched boot.img also for a better shell performance of the phone. It can be done on a trial and error basis. I have upload this .img also into my phone during the flash. You can do a separate flash or single flash of both the files together. No other files are required.
9. After ticking stay awake and usb debugging in your phone your put off your phone. Remove the batter. Connect the phone to your PC/ Lap top using the USB cable provided along with the phone. After connecting your phone now put your batter into the phone again. For some PC or Lap top you may have to put after clicking the download button. It depends on how you have installed the drivers or framwork of driver loading. Normally I connect the batter before clicking download section.
9.After downloading the required file, just look above the 5 white rows of the SPFT tool you can notice, four different components, vice ----Format----, firmware upgrade-----, download------- and DA DL all with check sum. Just click on the Download section there as shown in the pictures below
http://forum.xda-developers.com/attachment.php?attachmentid=2201573&stc=1&d=1377001862
a window will pop up asking you yes or now withe warning as seen in the above shot. Ignore the warning and click yes.
10. Depending up on the RAM and other features of your PC/Laptop first yellow flash across the bottom most row will glowing through as shown in the shot below and followed by a Purple/indigo micture glowing flash and finally a yellow beam that ends with a green circle as you seen in the shots below.
Though the CWM and Boot.img file file has already been uploaded by me in this portal for making it holistic I am up loading the files here.
https://docs.google.com/file/d/0B6mi3aQy8tz9XzhyZmFmQUtqWVk/edit?usp=sharing .... Patched boot.img file.
https://docs.google.com/file/d/0B6mi3aQy8tz9MldBYUlCdkxIRW8/edit?usp=sharing ----- CWM Recovery file
https://docs.google.com/file/d/0B6mi3aQy8tz9bHdXUWtYMUZPZTQ/edit?usp=sharing ---- SPFT 139 file
Extractthese files and keep it separatedly and use it
With bewst of my wishes.

u r patched bootIMAGE is not working PLZ DO IF U CAN MAKE SIZE LARGER OF FONT or if u can provide me kernel files SO MY FRND CAN ADD FEATURES IN IT not img file

Canvas 4 A210 boot.img
Shane said:
u r patched bootIMAGE is not working PLZ DO IF U CAN MAKE SIZE LARGER OF FONT or if u can provide me kernel files SO MY FRND CAN ADD FEATURES IN IT not img file
Click to expand...
Click to collapse
Dear Sir,
I am porting the stock Boot.img and also stock recovery.img. If further improvements takes place. I will be very happy. I do not know how to extract the kernel. The files are in 7z format and kindly extract them.
I am unable to upload directly due to the reasons as below
"Your submission could not be processed because a security token was missing.
If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error"
Please use this google drive url.
https://docs.google.com/file/d/0B6mi3aQy8tz9ZGxjbXJGVG1hUm8/edit?usp=sharing ;;;;; boot.img file
https://docs.google.com/file/d/0B6mi3aQy8tz9NFpra3hWUmJmSzQ/edit?usp=sharing .... recovery file
Regards,

puduraja said:
Hallo,
I was trying to find custom ROMS for the Canvas 4 -A210 Micromax mobile in this forum and my search yielded one custom Rom which I experimented and met with the difficulties.
I thought I can try some other custom ROM of the same type or equivalent type mobiles. Luckily I came across the "Thread By: bgcngm" which normally read regularly.
I picked up the V3.0MOD Rom and edited and and experimented with the A210 canvas4. Luckily it gave me a good performance except that of the "Video call" facility did not show up. My IMEI was also vanished. This happended to me on previous experiments also.
Hence who ever is going to use this Custom Rom has to back up there IMEI and restore it using Mobileuncle Tool or what ever they feel easier.
I submit and reiterate here all the credit for this ROM to "bgcngm" and also request him further help us to some more modification to ease the application. I am only a learner and new entrant. Based on my use below I provided the details: You should have a Rooted Phone..
1. Find here the CWM recovery that was obtained using the MTKDroid Tool 2.4.8.
2. Use SPFT above 119. I have used 139.
3. Download the stock ROM and click on the Scatter file. This will load up all the files required for the stock rom. Un-**** all the items. Now click preloader and take your curser to the recovery. Click it and point it to the extracted CWM recovery you have downloaded from this.
4. This will install the CWM recovery 5.5.0.4 to your mobile. Also you can try with Mobileuncle tool to install the cwm recovery.
5.Download and copy the Custom Rom to your external or internal sdcard. The url is here:
MMX-XXX-JB_210_ROM => https://docs.google.com/file/d/0B6mi3aQy8tz9TVlJWWJ5SnJMRDA/edit?usp=sharing
6. Before installing please back up every thing using the CWM recovery.
7. Using CWM recovery you select the custom ROM form the location you have copied and install from the AROMA installer.
8. Please back up your IMEI, some time it may be required if you loose yours, this can be restored using Mobileuncle Tool.
9. It is advisable to use custom installation and select what ever application you like.
10. Install and enjoy.
If you like my efforts, please hit thanks.
with best wishes
Please wait Camera is not seen/ working I am recasting it. I am trying. An port it tonight. Please wait
Click to expand...
Click to collapse
I installed it but then there was nothing inside the rom.. Even the touch in the aroma installer was not working,somehow managed to install it.
You said you ll port again, when can we expect the new upload from your side which we can actually use not on experimental basis.
Thank you

sexydjb said:
I installed it but then there was nothing inside the rom.. Even the touch in the aroma installer was not working,somehow managed to install it.
You said you ll port again, when can we expect the new upload from your side which we can actually use not on experimental basis.
Thank you
Click to expand...
Click to collapse
The is 547 MB and why nothing inside.
AROMA installer problems is also felt by me. But using volume up and down key and power on switch we have to install the Rom Colour scheme in the touch is not working for volume up and down buttons.
Since I was busy with local works I could not improve it. Developers who are free can attempt it.. For another one week I have busy schedule and afterwards I will try to improve it.
Thanks for your attempts

Not yet.
I have some other urgent work on duty and could not concentrate on this.
Please if some one could help it is good.
I can attend to the fix only after 10th September due to duty work.
I am sorry.
Sent from my A210 using xda app-developers app

Screens??
Any screensots of the rom?

What are the screen shots required If you list I shall port it immediately.
It is stock based one.
I can load this custom ROM, which is in the sd card and take shots and post it immediately.
Thanks
Sent from my A210 using xda app-developers app

NeroD said:
Any screensots of the rom?
Click to expand...
Click to collapse
Sent from my A210 using xda app-developers app

[RECOVERY] Cannibal Open Touch Recovery for ZTE V967S

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
UPDATE:
I updated the recovery to a new version, more stable, with CWM 6.0.4.4 basic structure (updated by me).
After a hard work with many failed builds, I succeded to compile from source a fully working recovery with touch support for ZTE V967S. I used for this the Project Open Cannibal source, named Cannibal Open Touch Recovery. It's a well done recovery, compatible with CWM, with usefull functions: for example advanced backup - you can backup only that partition you want, posibility to use themes, etc.
Here you can see more images of the recovery, from a device with smaller screen, but you can check the options.
Touch navigation is made by touching bottom buttons menu, just like in Philz recovery or similar. First button is for exit or go back, second is key down, third key up and last is select or enter. Now you can save your phone buttons.
You should read this:
First time you boot in recovery will be a touchscreen calibration set up: you have to touch three times the red square. Also, first time you do a backup, it will take a little longer time, because it will be create directory structure and free up the space. After that it will be a joy, is fast, is powerfull, is full of options and is funny.
CREDITS:
Project Open Cannibal who release and mantains this wonderful recovery.
Sblood86 for his help.
C3C076 for his help on tweaking recovery source.
bgcngm for his unpacking tool.Download from attachment.

Deleted.

Need your Help Master
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.

BOND1987 said:
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.
Click to expand...
Click to collapse
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.

carliv said:
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.
Click to expand...
Click to collapse
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.

BOND1987 said:
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.
Click to expand...
Click to collapse
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.

carliv said:
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.
Click to expand...
Click to collapse
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
I am using recovery of Master Yuweng that you suggested few post back.
EDIT:-
Got the Images back after installing the default theme. Actually I selected the theme RED but it was not there so it was saying like that. Now will create a theme and share to you also. BTW how can I adjust size and something to do with touch also...
Master You are awesome and your creations also.

BOND1987 said:
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
Click to expand...
Click to collapse
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.

carliv said:
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.
Click to expand...
Click to collapse
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????

BOND1987 said:
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????
Click to expand...
Click to collapse
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.

carliv said:
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.
Click to expand...
Click to collapse
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....

BOND1987 said:
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....
Click to expand...
Click to collapse
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.

carliv said:
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.
Click to expand...
Click to collapse
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.

BOND1987 said:
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.
Click to expand...
Click to collapse
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.

carliv said:
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.
Click to expand...
Click to collapse
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery

BOND1987 said:
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery
Click to expand...
Click to collapse
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.

carliv said:
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.
Click to expand...
Click to collapse
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.

BOND1987 said:
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.
Click to expand...
Click to collapse
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.

carliv said:
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.
Click to expand...
Click to collapse
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.

BOND1987 said:
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.
Click to expand...
Click to collapse
I need your device official boot.img and recovery.img
There is something wrong in your init.rc, but I need to look in those two files to be sure.

A buggy twrp for A60, but not sure for M40.

I have made and got a buggy twrp for A6060, which is the Chinese version of M40, based on android-11. It can startup but lacking mtp and usb. It can't decrypt the /data too so you should do some preparations before can use it. I am not sure whether it can be used on M40.
Usage in shorts:
① Magisk and root. You can find the guide in this forum so I will pass it.
② Using a file manager to access /system/vender/etc/fstab.qcom, in the part of /userdata delete the field of "fileencryption=ice" (usually sth. like this, not includes the quotation marks), same and quit.
③ Enter recovery and wipe data. Then use odin flash this recovery: Just zip it to .tar file then flash in the AP slot.
④ When startup, press VOLUMN UP ＆ POWER. If everything goes well, you will see the logo of twrp and enter it and can successfully access the files in /data. Then you can copy some gsi and have a try.
Click to expand...
Click to collapse
Hope it will be helpful and I really hope somebody can make it a ture and full device tree. That will definetely benefit both A60 and M40 users.
The twrp for A60: https://github.com/Jason-summer/Action-Recovery-builder
The source of the twrp: https://github.com/Jason-summer/device_samsung_a60q/tree/android-11
Sorry for my poor English if causing someone confused.

good job! Is it possible to flash a phone using this? (i have a60)

blankkk123 said:
good job! Is it possible to flash a phone using this? (i have a60)
Click to expand...
Click to collapse
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.

SummerElement said:
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.
Click to expand...
Click to collapse
If it's not difficult, can you please write instructions? I think this will help many who want to flash

Database Info

welcome