yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] entons:
hi

I have a phone type newman champion k1b

. Android 4.2.2. mtk 6582.

I've ROOTed the phone and I installed an app called root uninstaller - ru, I removed unneeded applications and accidentally deleted the CONTACTS. Now I miss the icon

of the PHONE DIALER and the CONTACT and pop-up message "Unfortunately process android.process.acore STOPED"

Factory Restore did not resolve the problem.

After the problem has been created I am backup the ROM by SP-Flash-Tool.

and i try to install stok rom of neman k1b mt6589 . bat the phone not work.

now i am restore by SP-Flash-Tool my rom from backup . the pone work bat in the same problem.

I am looking for a suitable ROM for NEWMAN K1B 4.2.2 to MTK 6582.

Or in any way to restore the CONTACTS and dialer, and solve the problem.

With CPU-Z saw that the manufacturer is ALPS.

The MODEL - CHAMPION K1B

kernel- 3.4.5 (eng.liya.1389839432)

IN THE Back of the device under the battery says:

NEWMAN CHAMPION MOBILE

MODEL K1B. MADE IN CHINA

Thanks in advance for any help.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] cvaria:
has anyone got the mutli-user profiles up and running on an edge or note 4?
[Miscellaneous Android Development] :
Unpack the resources.

In windows just drag them over unpack_MTK_img.bat or MTK_unpack.bat, one by one and that's it, you will see three new folders with every image name. You have to rename the porting recovery to a short name (ex. carliv-recovery, no spaces please) before dragging to unpack.

In linux, open a terminal in CarlivImageKitchen or mtk-tools folder where you have also the three images, and then type:

./unpack_MTK_img boot.img

or

./unpack-MTK.pl boot.img

to unpack the stock boot.img

When the boot image is unpacked, delete

boot.img

and

boot.img-kernel.img

if you are using bgcngm's tools.

After that type:

./unpack_MTK_img recovery.img

or

./unpack-MTK.pl recovery.img

to unpack the stock recovery.img

When the recovery image is unpacked, if you use bgcngm's tools, append "-stock" to

recovery.img-kernel.img

to name it recovery.img-kernel.img-stock and to

recovery.img-ramdisk

to name it recovery.img-ramdisk-stock, then delete

recovery.img

.

Next, rename "port_CarlivTouch-recovery-..." or the recovery you want to port, as

recovery.img

for bgcngm's tools or

carliv-recovery

for CarlivImageKitchen.

Then type again:

./unpack_MTK_img carliv-recovery.img

or

./unpack-MTK.pl recovery.img

to unpack the carliv recovery for port.

When it's finished, if you use bgcngm's tools, rename

recovery.img-ramdisk

as recovery.img-ramdisk-carliv or something to make the difference from stock ramdisk, and delete

recovery.img

and

recovery.img-kernel.img

from carliv recovery.

By doing this you already replaced the kernel with your stock one in bgcngm's tools.

Replace the kernel

If you use CarlivImageKitchen, both in linux or windows, just copy and replace all files except ramdisk folder from stock recovery folder to carliv recovery folder.

----------------------

In linux, when you use bgcngm's tools, that is already done as I said (only need to delete "-stock" from

recovery.img-kernel.img-stock

).

----------------------

In windows with michfood's tools open in two side by side windows the

boot stock folder

and

carliv-recovery folder

, then select kernel and kernel_header from boot and drag them over the carliv's kernel and kernel_header replacing both.

All the above are the same for jellybean or kitkat.
[Miscellaneous Android Development] Jamil69:
Another usefull guide sir,,,

Thanx [emoji4]
[Miscellaneous Android Development] avi3230:
Great guide as always sir,

I am not getting this last line before repacking:(

Do we need to include in the port recovery (from stock boot folder).

Or just needed the data inside the files to get vendorid and product id.

Thank you.
[Miscellaneous Android Development] :
As I said, you only need the data from stock files - those marked by me in red in example.
[Miscellaneous Android Development] Tech N You:
Here we go one more awesome guide! :D :good:

Thanks Master Carliv :) :cool:

EDIT : Figured out myself! Thanks works perfectly as a charm. :)
[Miscellaneous Android Development] ramex:
master carliv

Carliv Touch Recovery v3.0 for Kitkat has been successfully running on Evercross A66A_09_MT6582M_V 2.11

Thank you for providing Instructions

:good::good::good:

br,

ramex
[Miscellaneous Android Development] :
That's good, but looking at that image it seems that you used a wrong version to port. If I have to guess, I think you used 1280x720 instead of 720x1280, or something like that. The pictures from first post are made on a screen with 720x1280. There is a difference between yours and those, isn't it? If you use the right resolution it will look even better.

Cheers!
[Miscellaneous Android Development] ramex:
You right,

Better to use 720x1280 rather than resolution of 1280 x 720 and I already apply to latest ROM EVERCOSS A66A V12 MT6582M

Thank You.

:good::good::good:

br,

ramex
[Miscellaneous Android Development] Sagar_Patel:
syntax of the command is incorrect

while unpacking disc images, i am getting error at the end of the command window saying syntax of the command is incorrect.

Also, while unpacking stock boot image and recovery image, i am getting error saying "end offset is lower than start offset"

can you please help me?

im using windows 7 home premium, boot/recovery unpack/repack tool was used on desktop...

my device is panasonic p81, mt6592, resolution 720*1280

i have attached screenshots and also a zip file that includes same screenshots in good resolution.

Thanks in advance...
[Miscellaneous Android Development] hanuma:
Try this option STD_unpack.bat
[Miscellaneous Android Development] :
That was already discussed on this page starting with post #22, and there is a repacked tool in one of my posts from that page which seems to work better.
[Miscellaneous Android Development] Filipus:
[MENTION=5186178]carliv[/MENTION]: using your excellent tutorials, I successfully installed Carliv Touch Recovery v2.2 - Ubifs on my Samsung S5 Mini clone (MT6572-based). Except for the fact that the display is upside down, it works perfectly. Thanks!
[Miscellaneous Android Development] :
Thanks! But is it 2.2 or 2.7? :)

I know about the flipped screen issue, I'm still trying to find a solution for that.
[Miscellaneous Android Development] Filipus:
It's 2.2. I only realized later that a more recent version exists and I was too lazy (or not brave enough!) to attempt flashing the device again.

Should I?

Oh, and by the way, the flipped screen issue really isn't much of one, especially since the touch feature works so well. Don't lose any sleep over it... :)
[Miscellaneous Android Development] Maximus1a:
Hi Carliv,

i tried to make a v3.0 CTR for my phone (Elephone G6) but it does not work at all.

English is not natural language so some parts appeared confusing to me.

i think i did everything like shown in you tutorial but i got many errors while unpacking and packing. i got these errors managed but i´m not sure if something went wrong while packing, or maybe i made an error.

can you make a CTR3.0 for me please?

it would be nice when you help me out. :)
[Miscellaneous Android Development] anis_mulla:
I just tried for my MT6572

Worked successfully..

but i am getting out of screen .. Options are looking bigger..

i have 480*800 and i have downloaded for same resolution..

any way to change resolution ?:confused:
[Miscellaneous Android Development] :
It will be better for you to post here the ported recovery, to see what is wrong.

That is built with 15x24 font, which looks nice in 540x960... Maybe I should use a smaller font... but the next one is too small. Try to use 320x480 source and replace the images from res/images/ folder with those from 480x800. Tell me if that's better.
[Miscellaneous Android Development] anis_mulla:
Should i need to follow whole step again or is it ok to just copy all modified files ?:confused:
[Miscellaneous Android Development] Maximus1a:
here it is :)
[Miscellaneous Android Development] :
Check these suggestions and do it again! :)

Cheers!
[Miscellaneous Android Development] Maximus1a:
thanks for your tips. :)

i´ll try later this day. :good:

EDITH says: it worked. :laugh::laugh::laugh:

very cool. :good:

many thanks to you.

after testing some days i´ll make it public on needrom and here
[Miscellaneous Android Development] SmiLeToLife:
Thanks Carliv, i need some help

i need to find correct path for voldmanaged but i dont know how to. is there any adb command for that? Also i dont know how to find them via root explorer.

my phone is mmc too. my fstab:

/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:emmc@fat,noemulatedsd

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

as you said those are not working. But in carliv 3.0 720x1280 recovery :

/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard1:8,

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

also didnt work for me ...

i have ported recovery but can't see my storages. cant mount them. so can't install rom :D

thanks in advance :)
[Miscellaneous Android Development] :
No, you need to copy only the "recovery" module from ramdisk/sbin folder from 320x480 recovery to your ported in same folder replacing the one from there.

Everything else remain the same. And repack.

Did you checked my Guide in images, linked in OP. In those 90something images you can find more info about that. Usually is the number from fat partition block. If you don't have a fat partition check my Guide in images to understand what that means.
[Miscellaneous Android Development] Maximus1a:
when i try to sideload a zip i get status 1.

is this CWM or device related?

when i open Show Recovery log i get informations.

"I:Can´t partition non mmcblk device: /devices/platform/mtk-msdc.1/mmc_host/mmc1"

"I:Can´t partition non mmcblk device: /devices/platform/mtk-msdc.0/mmc_host/mmc0"

Is this a problem for me?
[Miscellaneous Android Development] :
For sideload it's something that you are doing wrong or your ported recovery has something not set right.

Here is my test made just now:

Those info messages in recovery log are normal - your sdcards are not defined as mmcblk devices because they are voldmanaged. I know something is redundant here since if you define sdcards as mmcblk they won't work, but I kept it from CWM, they did it this way.
[Miscellaneous Android Development] Maximus1a:
your CTR is driving me crazy.....

now i get without changing anything status 6 and 7 with roms who worked on monday.

i go to bed.

edit: now it is unable to restore backups. ??? realy intresting...
[Miscellaneous Android Development] :
I don't understand what's happening in your device, but I never heard of any recovery to "go crazy" like that without a reason. If it worked untill some point, start thinking what you did at that moment and after. Maybe you can isolate the problem and correct it.
[Miscellaneous Android Development] kirito9:
[MENTION=5186178]carliv[/MENTION] add to list of working ported recoveries. :D http://xdaforums.com/android/development/recovery-carliv-touch-recovery-2-7-t3019163/post58575866#post58575866
[Miscellaneous Android Development] DerTeufel1980:
anyone already worked on mt6752 device?
[Miscellaneous Android Development] :
Yes, but not much. SevenMaxs built my recovery and a twrp for a Lenovo with mt6752. I helped him to fix sdcards for my recovery and he said both are working very well. He used my device tree for mt6595 to create his device tree (the custom graphics files are the same as I did them - unchanged - and they are working). He said everything works really well, but I don't have any device to test, and I don't know if he pushed to github his device folder.
[Miscellaneous Android Development] DerTeufel1980:
Thanks. I've got jiayu s3, going to try it on Saturday. I'll let you know how it goes
[Miscellaneous Android Development] FSadino:
Hello,

First all very thanks [MENTION=5186178]carliv[/MENTION] for this great tutorial, i successful ported your recovery to Wiko Darkfull (Thread) and add all credits to you.

I just want to ask if theres any way to make Touch working on Jelly Bean.

Thanks again :good:
[Miscellaneous Android Development] :
The touch is related to kernel and touchscreen drivers. If other touch recovery works, this one should work too. If the touch isn't working at all in any recovery, it will be very hard to fix that.
[Miscellaneous Android Development] SmiLeToLife:
thank you for your help Carliv. Now everything works good but in recovery when i mount my storages and copy / paste some zip files to sdcards it's really slow. probably i made some mistake?
[Miscellaneous Android Development] m_slon:
There is an error in MTK_Unpack.bat near the end of file. Just remove 'echo.' in the end of marked line:

md %~N1\rmdisk
cd %~N1
cd rmdisk
%~dp0bin\cpio.exe -i <../ram_disk
cd ..
cd ..

[COLOR="Blue"][B]copy %1 %~N1[/B][/COLOR]
echo.
pause
echo - Done^!
:end

I need an advice. My phone (Galaxy S5 clone MT6571) is UBIFS-based. I've made a port of recovery v.2.7 (from this post) using your guide but with flipped screen i got an errors:

E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't find /dev/mtd/mtd9
I: ensure_path_mounted ubifs: /cache ubifs /dev/mtd/mtd14 (null)
E: bad mtd index for /dev/mtd/mtd14
I: Can't format unknown volume: /external_sd

etc........

My dumpchar_info.txt

Part_Name	Size	StartAddr	Type	MapTo
preloader 0x00080000 0x00000000 1 /dev/mtd/mtd0
pro_info 0x00100000 0x00000001 1 /dev/mtd/mtd1
nvram 0x00180000 0x00000002 1 /dev/mtd/mtd2
protect_f 0x00180000 0x00000003 1 /dev/mtd/mtd3
seccfg 0x00020000 0x00000004 1 /dev/mtd/mtd4
uboot 0x00080000 0x00000005 1 /dev/mtd/mtd5
bootimg 0x00600000 0x00000006 1 /dev/mtd/mtd6
recovery 0x00600000 0x00000007 1 /dev/mtd/mtd7
sec_ro 0x00040000 0x00000008 1 /dev/mtd/mtd8
misc 0x00060000 0x00000009 1 /dev/mtd/mtd9
logo 0x00100000 0x0000000a 1 /dev/mtd/mtd10
expdb 0x00200000 0x0000000b 1 /dev/mtd/mtd11
fat 0x01400000 0x0000000c 1 /dev/mtd/mtd12
android 0x13600000 0x0000000d 1 /dev/mtd/mtd13
cache 0x00180000 0x0000000e 1 /dev/mtd/mtd14
usrdata 0x09580000 0x0000000f 1 /dev/mtd/mtd15
bmtpool 0x00000000 0x00000000 1
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate

Edited /etc/recovery.fstab in carliv-port

# mount point	fstype	device	[device2]

/boot	mtd	/dev/mtd/mtd6
/misc	mtd	/dev/mtd/mtd9
/nvram	mtd	/dev/mtd/mtd2
/recovery	mtd	/dev/mtd/mtd7
/uboot	mtd	/dev/mtd/mtd5
/system	ubifs	/dev/mtd/mtd13
/cache	ubifs	/dev/mtd/mtd14
/data	ubifs	/dev/mtd/mtd15
/emmc vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/sdcard	vfat	/dev/block/mmcblk1p1 /dev/block/mmcblk1

/etc/recovery.fstab from stock recovery

# mount point	fstype	device	[device2]

/boot	mtd	boot
/cache	ubifs	cache
/data	ubifs	userdata
/misc	mtd	misc
/recovery	mtd	recovery
/sdcard	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/system	ubifs	system

Do i need to use stock-like mounting points?
[Miscellaneous Android Development] :
For flipped screen I can't help you now. I'm still working for a solution.

For the other issues I don't know the exact problem because I never had a device with ubifs, but try to reboot recovery (in recovery from power menu "reboot recovery") or reboot to system and go back to recovery. Also try to mount manually the /cache in mount/storage.

Anyway, as I said, for ubifs I can't offer much support because I couldn't test this recovery version in a device. I made it for advanced developers to try to port or build it for their devices.

Many reported successful ports (check the thread), so there has to be a way for you too.
[Miscellaneous Android Development] m_slon:
Hi, it's me again ;)

I still can't figure out how to flip the screen on recovery. Probably there's something in the pnone's stock firmware.

OK, let's get back to mounts.

When i make /etc/recovery.fstab yours-like

# mount point	fstype	device	[device2]

/boot	mtd	/dev/mtd/mtd6
/misc	mtd	/dev/mtd/mtd9
/nvram	mtd	/dev/mtd/mtd2
/recovery	mtd	/dev/mtd/mtd7
/uboot	mtd	/dev/mtd/mtd5
/system	ubifs	/dev/mtd/mtd13
/cache	ubifs	/dev/mtd/mtd14
/data	ubifs	/dev/mtd/mtd15
/emmc vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/sdcard	vfat	/dev/block/mmcblk1p1 /dev/block/mmcblk1

my errors are:

When i make /etc/recovery.fstab like stock recovery

# mount point	fstype	device	[device2]

/boot	mtd	boot
/cache	ubifs	cache
/data	ubifs	userdata
/misc	mtd	misc
/recovery	mtd	recovery
/sdcard	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/system	ubifs	system

my errors are:

I've searched through files and can't find any match of 'mtd14'

Any ideas?:confused:
[Miscellaneous Android Development] :
For flipped screen, you need to build from source a recovery that support it (mine doesn't yet) - ask other guys with same problem (I never had it).

And about those ubifs errors I can't help you because again, I never had a device with that file system. I worked a version of recovery for those phones, but I never test it and I can't tell you what is wrong with your files. Some time ago, there was a little interest in that version, but lately none (I couldn't even find someone to test version 3.0 for ubifs before release).

So, take my recovery as it is. If you can find someone with more experience in ubifs recoveries and a solution, please share it here for other users, because this is the biggest problem on xda: users search for an answer, and after they find it never come back to post a feedback to help others as well.
[Miscellaneous Android Development] raviindia:
CTR for Karbonn smart A11 Star (MTK6572) Little problem

Dear Carliv,

Hope you are good and working very well.

actually with the help of your tutorial, I managed to port CTR for the first time, for my device Karbonn Smart A11 Star, OS Android Kitkat 4.4.4, a low range Smartphone.

But i am having a little problem like when I am trying to "install from SDcard0" i am getting a error message like, "E:can't mount /system/sdcard0"

actually I follow all your steps, but I don't know why I am getting his error, so please help me.

I am just attaching some images from your tutorial, please explain these images to me, and please tell me why I am getting this error messages.

And in mine phone's stock boot file there was no "init.fuse.rc" file. there was a file named "init.fon.rc" so I did not complete the "step78" and "step79".

I will be very happy, if you reply and provide me the solution

and thanks for your contribution and for your tutorial.

Here is the attached file Explain this

And I did not complete these.
[Miscellaneous Android Development] Kyzrael:
Check init.rc and fstab files... It will pin point the correct sdcard path of yours... I experience that also when I first try to port but now it is now easy for me just give a time to look at the lines pertaining to storages.
[Miscellaneous Android Development] raviindia:
[MENTION=6168512]Kyzrael[/MENTION]

I will check and reply you.

if find any problem.

and could you please tell that the ported CTR is working fine, but can't mount the "SD card" from CTR for flashing the zip file or for backup of ROM
[Miscellaneous Android Development] Kyzrael:
Okay!

But if you still cannot pin point whats the problem... You can approach me and attach all the files (stock boot.img, recovery.img, and the ported ctr.img) so that if I have a time I will check it for you and correct/fix it (if I can).
[Miscellaneous Android Development] rictec:
Thanks yet again ;)

Thank you another of my devices with your recovery this time a alcatel pop C7 mt6582 one ;)
[Miscellaneous Android Development] kenzukie:
Can't mount misc any idea ?
[Miscellaneous Android Development] :
Probably wrong definition in fstab for it.
[Miscellaneous Android Development] sebcle38:
Thanks, i have tested your 2.7 for my Startrail 4 (A french Zte blade Q by SFR) on Android 4.2.2

It work but i can't reboot or power off my phone, i have to remove the battery.

The tactile on the screen is not working, but it work well in Aroma.
[Miscellaneous Android Development] :
Well the touch screen module is different in recovery than aroma file manager and I can't say much about aroma file manager but for recovery you need e kernel that has the touch driver enabled. Being a 4.2.2 kernel should be, but we've seen other cases (elephone p6000) with more newer android version which didn't had touch enabled in recovery (well, they had but it was a flaw in source witch make it unusable).

About power options I can't help much without the device. As I stated in the OP my ported recovery works for most MTK phones but not for all. You need a developer with same phone to build the recovery from source and to make some adjustments in code to make it work (things that only having the phone can be found). Or you can start to learn and do it by yourself :)
[Miscellaneous Android Development] adilrenzu:
Hello Mate

Is there any comprehensive guide or tool to port your cmw touch recovery for jiayu s3 mtk6752 LOLIPOP We have twrp recovery but i like CMW more. Any help would be appreciated. Regards.
[Miscellaneous Android Development] :
The CWM development has stoped at kitkat. That is the reason you can't find a recovery based on cwm for lollipop kernels.
[Miscellaneous Android Development] Arittra:
CWM Needed For SAMSUNG GALAXY A5 SM-A500H

I have found a lot on this topic on Google but I didn't get it...I want to learn how to port Cwm recovery for galaxy A5 or give me the download link of ported Cwm for galaxy A5...Please help me.....Thank you....
[Miscellaneous Android Development] :
The "porting" method presented here is referring only to mediatek powered phones, as the title says. Your phone has a Qualcomm platform and for that you need to build it from source or find a developer with same phone who can do that. I can't, I don't have that phone.
[Miscellaneous Android Development] Adriano-A3:
Can somebody port it for me?

My device is an iNew V1 mt6582 Android 4.4.2.

It already has CWM, but non-touch.

If you know how to port and have time to help me, please...

I'll send my boot.img and recovery.img asap "you" confirm me that will do.
[Miscellaneous Android Development] MSalmanKhan17:
Recovery.img was unpacked fine but when I unpack boot.img I get this error:

Printing information for "boot.img"

Unpack mtk image utility by carliv@xda

Header:

Magic : ANDROID!

Magic offset : 0x00000000

Page size : 2048 (0x00000800)

Base address : 0x10000000

Kernel address : 0x10008000

Kernel size : 4053256 (0x003dd908)

Kernel offset : 0x00008000

>> kernel written to 'boot_stock/boot.img-kernel' (4052744 bytes)

Ramdisk address : 0x11000000

Ramdisk size : 636930 (0x0009b802)

Ramdisk offset : 0x01000000

>> ramdisk written to 'boot_stock/boot.img-ramdisk.gz' (636418 bytes)

Second address : 0x10f00000

Tags address : 0x10000100

Tags offset : 0x00000100

Compression used: gz

Unpacking the ramdisk....

../boot.img-ramdisk.gz:

gzip: ../boot.img-ramdisk.gz: invalid compressed data--length error

2239 blocks

Done. Your image is unpacked in boot_stock folder.

Press any key to continue . . .

---------- Post added at 10:30 PM ---------- Previous post was at 10:05 PM ----------

Dear [MENTION=5186178]carliv[/MENTION]

Can you make a video on this? It would be much easier for us to understand!
[Miscellaneous Android Development] :
Sorry I won't make a video for this. I think the written and the image guides are enough. If someone can't figure out how to do it from these two then maybe should stay away from these things.

That error seems to be related to gzip executable in your computer. Post here a link for that boot.img.
[Miscellaneous Android Development] BouyaPK:
This forum helped me a lot. now I can have my own Custom Recovery then.

Thanks [MENTION=5186178]carliv[/MENTION]