Q&A for [Guide]How To Port & Modify Roms For Mediatek[Everything]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
thanks for great guide
i have ported the rom it have bug. screen is black but sound is coming
I ported Lenovo P780 ROM for Xolo Q900 and after that when installing this rom it gives error "(Status 0) installation aborted". What is solution for that. Please help me.
i want to port a kitkat rom to my device
actually xolo have released kk for A500 club mtk 6572 its specs are exactly same as my phone a500s somehow can i get kk for my phone pls help m
Help- Port a ROM for Micromax Bolt A61.
All developers are requested to Port a ROM for Micromax Bolt A61. & Also plz tell me how to port Recoveries & ROM via android & Computer both... plz..
thanks .
help with update script
hi bros please give a hand with my updater script. i donto know how to chanhe the #mounts.
update-script
hello!
Can anybody help me with the Android kitchen to Register my device and to make a updater-script for my device, want to port a Rom!!
Thank you!
Greetz,
Nick
Maybe you should join me so that we build mediatek frame buffer console for debugging,it could really helpout.
Sent from my ALCATEL ONE TOUCH 918D using xda app-developers app
I got an error
I use step 1. and while install the ported rom it shows an error "format() expects 5 args, got 4 " status 7
please help,
MTK 6582 ROM port: I've tried everything
Hi, I've been working on replacing the OS on my MTK6582 for many days over the last 3 weeks. I've followed several very helpful guides but I simply cannot get an alternative ROM to successfully boot. The original stock ROM is buggy and won't even connect my SIM to the network!
I've found this guide [Guide]How To Port & Modify Roms For Mediatek[Everything] by @digyvijaykumar123 to be the most helpful but I don't think the OP is active any more and I don't have the authority required to reply on that thread. I've tried posting in the Noob Friendly thread with no response.
Honestly, at this stage I'll try anything! So please give me the benefit of your experience and knowledge!
The phone is an unbranded clone. It's called "Lenovo A808T" but this seems to be completely misleading, and not even connected to the usual clone of that name.
Here's the MTK Droid Tool info:
Hardware : MT6582 (MT6595 is Fake!)
Model : LENOVO
Build number : ALPS.KK1.MP1.V2.11
Build date UTC : 20140914-111625
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V35, 2014/07/17 10:42
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Oct 20 17:21:08 CST 2014
Uboot build v : -----
LCD Driver IC : 0-sh1282_dsi
I've tried porting 7 ROMs but the most successful (i.e. have installed in CWM) have been the following:
Inew V3 Huawei Emui 3 port KK,
Lenovo S860 VibeUI 2.0,
Honor 3C Hol-T00/U10 MIUI,
Lenovo S850 VibeUI 2.0.
All ROMS have been based on the 4.4.2 Android version, the MTK6582 chip and most on the same resolution. However they either boot loop or hang on the "welcome" logo.
Some questions I have are:
MTK Droid Tools detects the phone as a MTK 6582, is this detection 100% unmistakably correct?
MTK Droid Tools says the OS is 4.4.2, is this also 100% correct (or is this easily changeable in the build.prop or some other file)? If so, how can I determine the real Android version?
Will using a ROM with the same build number "ALPS.KK1.MP1.V2.11" make a boot more likely?[/B] Other ROMs using this same build number seem to be for the MTK6592.
In relation to @digyvijaykumar123's guide that I've been following I have these questions:
I don't have a file called "modem.img" in my stock ROM System/etc/firmware folder. I do have a file "modem_1_wg_n.img" but copying or not doesn't seem to make any difference.
The stock ROM does not have a System/lib/modules folder, so should I delete the Port ROM modules folder?
The only step I have not followed in the guide is this:
"Lastly drag and drop a launcher like nova,apex or any to system/app/ of port zip in case port launcher did not worked."
Is this a necessary step?
I'll find another ROM and keep trying but at this stage it's like banging my head against the wall. I've invested literally days of time on this so I'd hate to give up now. Any advice will be gratefully followed.
Eclectica said:
Hi, I've been working on replacing the OS on my MTK6582 for many days over the last 3 weeks. I've followed several very helpful guides but I simply cannot get an alternative ROM to successfully boot. The original stock ROM is buggy and won't even connect my SIM to the network!
I've found this guide [Guide]How To Port & Modify Roms For Mediatek[Everything] by @digyvijaykumar123 to be the most helpful but I don't think the OP is active any more and I don't have the authority required to reply on that thread. I've tried posting in the Noob Friendly thread with no response.
Honestly, at this stage I'll try anything! So please give me the benefit of your experience and knowledge!
The phone is an unbranded clone. It's called "Lenovo A808T" but this seems to be completely misleading, and not even connected to the usual clone of that name.
Here's the MTK Droid Tool info:
Hardware : MT6582 (MT6595 is Fake!)
Model : LENOVO
Build number : ALPS.KK1.MP1.V2.11
Build date UTC : 20140914-111625
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V35, 2014/07/17 10:42
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Oct 20 17:21:08 CST 2014
Uboot build v : -----
LCD Driver IC : 0-sh1282_dsi
I've tried porting 7 ROMs but the most successful (i.e. have installed in CWM) have been the following:
Inew V3 Huawei Emui 3 port KK,
Lenovo S860 VibeUI 2.0,
Honor 3C Hol-T00/U10 MIUI,
Lenovo S850 VibeUI 2.0.
All ROMS have been based on the 4.4.2 Android version, the MTK6582 chip and most on the same resolution. However they either boot loop or hang on the "welcome" logo.
Some questions I have are:
MTK Droid Tools detects the phone as a MTK 6582, is this detection 100% unmistakably correct?
MTK Droid Tools says the OS is 4.4.2, is this also 100% correct (or is this easily changeable in the build.prop or some other file)? If so, how can I determine the real Android version?
Will using a ROM with the same build number "ALPS.KK1.MP1.V2.11" make a boot more likely?[/B] Other ROMs using this same build number seem to be for the MTK6592.
In relation to @digyvijaykumar123's guide that I've been following I have these questions:
I don't have a file called "modem.img" in my stock ROM System/etc/firmware folder. I do have a file "modem_1_wg_n.img" but copying or not doesn't seem to make any difference.
The stock ROM does not have a System/lib/modules folder, so should I delete the Port ROM modules folder?
The only step I have not followed in the guide is this:
"Lastly drag and drop a launcher like nova,apex or any to system/app/ of port zip in case port launcher did not worked."
Is this a necessary step?
I'll find another ROM and keep trying but at this stage it's like banging my head against the wall. I've invested literally days of time on this so I'd hate to give up now. Any advice will be gratefully followed.
Click to expand...
Click to collapse
Hi,
Firstly please post your build.prop here.That will help to clear some confusions.
And dont worry,all issues will be fixed.
Cheers..
digyvijaykumar123 said:
Hi,
Firstly please post your build.prop here.That will help to clear some confusions.
And dont worry,all issues will be fixed.
Cheers..
Click to expand...
Click to collapse
Hi, so good to get a reply from you!
This is from the latest ROM I've adapted and tried to flash.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=VIBEUI_V2.0_1451_7.8.1_ST_S850
ro.build.version.incremental=VIBEUI_V2.0_1451_7.8.1_ST_S850
ro.custom.build.version=VIBEUI_V2.0_1451_7.8.1_ST_S850
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Wed Dec 10 17:13:08 CST 2014
ro.build.date.utc=1418202788
ro.build.type=user
ro.build.user=buildslave
ro.build.host=shws22
ro.build.tags=release-keys
ro.product.brand=Lenovo
ro.product.board=scofield
ro.product.cpu.abi=armeabi-v7a
ro.product.device=MTK
ro.product.model=Lenovo MTK
ro.product.name=scofield
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LENOVO
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=MTK
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=scofield-user 4.4.2 KOT49H VIBEUI_V2.0_1451_7.8.1_ST_S850 dev-keys
ro.build.fingerprint=Lenovo/scofield/S850:4.4.2/KOT49H/VIBEUI_V2.0_1451_7.8.1_ST_S850.:user/release-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP1.V2.10
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/scofield/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# switch bluetooth stack solution
#
ro.btstack=blueangel
#lenovo-sw chenglong1 add for camera exif info
#
# camera related exif info
#
ro.camera.main.hwinfo=3.85
ro.camera.sub.hwinfo=3.38
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=CrispBell.ogg
ro.config.alarm_alert=Dreamland.ogg
ro.config.ringtone=SaltWater.ogg
ro.config.ringtone_2=SaltWater.ogg
ro.config.sms_notifi_sound=HeavenNearby.ogg
ro.config.sms_notifi_sound_2=HeavenNearby.ogg
ro.com.lenovo.smart.config=7
persist.systembgdata.enable=true
persist.backgrounddata.enable=false
ro.lenovo.adb=apkctl
ro.sf.lcd_density=320
ro.ctaversion.enable=false
ro.lenovo.bqb=no
ro.lenovo.wificert=no
ro.lenovo.platform=mtk
persist.sys.timezone=America/New_York
ro.com.google.clientbase=android-lenovo
ro.config.max_starting_bg=10
persist.ipo.shutdown.process.wl=com.vlife.lenovo.wallpaper/com.vlife.lenovo.wallpaper:main
ro.lenovo.core.version=master(PRE_V1.0.8)
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6582
mediatek.wlan.module.postfix=_consys_mt6582
ril.radiooff.poweroffMD=0
sys.lenovo.romui.version.sdk=2
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.lenovo.operator=open
ro.lenovo.videocall=true
ro.lenovo.sim=dsds
ro.product.sw.internal.version=S850_USR_ST1451_7.8.1_1412101706_MP1V2_rom_mt65X2_v2.0_ST_CN
ro.product.hw.version=H201
ro.product.particular.version=LENOVO_FUJIAN
ro.product.ota.model=LenovoS850_ROM_ST_KK
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
I called the kitchen/tools/edify_defs file "MTK".
Not sure if this helps, but here is an unmodified build.prop file extracted from a CWM backup of the stock ROM:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP1.V2.11
ro.build.version.incremental=eng.ysm.1410693248
ro.custom.build.version=LENOVO_20140914
ro.custom.build.versiondisplay=LENOVO_20140914
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2014年 09月 14日 星期日 19:16:25 CST
ro.build.date.utc=1410693385
ro.build.type=user
ro.build.user=ysm
ro.build.host=tastech2-desktop
ro.build.tags=test-keys
ro.product.model=LENOVO
ro.product.modeldisplay=LENOVO
ro.product.brand=LENOVO
ro.product.name=LENOVO
ro.product.device=LENOVO
ro.product.board=LENOVO
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LENOVO
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/New_York
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=LENOVO
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=v820_kk-user 4.4.2 KOT49H eng.ysm.1410693248 test-keys
ro.build.fingerprint=alps/v820_kk/v820_kk:4.4.2/KOT49H/1410693248:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties
ro.custom.lcm.id=sh1282_boe_c3_lianxin
ro.custom.camera.version=ov5648_mipi_raw s5k5eayx_yuv s5k5e2ya_mipi_raw siv121du_yuv
ro.custom.camera.pixel=main_500w_and_200w__sub_200w_and_30w
ro.custom.fm.id=6628
ro.custom.modem=hexing82_hspa
ro.custom.alsp=APDS9930 ltr558
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP1.V2.11
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/v820_kk/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# switch bluetooth stack solution
#
ro.btstack=blueangel
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6582
mediatek.wlan.module.postfix=_consys_mt6582
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Eclectica said:
Not sure if this helps, but here is an unmodified build.prop file extracted from a CWM backup of the stock ROM:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP1.V2.11
ro.build.version.incremental=eng.ysm.1410693248
ro.custom.build.version=LENOVO_20140914
ro.custom.build.versiondisplay=LENOVO_20140914
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2014年 09月 14日 星期日 19:16:25 CST
ro.build.date.utc=1410693385
ro.build.type=user
ro.build.user=ysm
ro.build.host=tastech2-desktop
ro.build.tags=test-keys
ro.product.model=LENOVO
ro.product.modeldisplay=LENOVO
ro.product.brand=LENOVO
ro.product.name=LENOVO
ro.product.device=LENOVO
ro.product.board=LENOVO
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LENOVO
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/New_York
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=LENOVO
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=v820_kk-user 4.4.2 KOT49H eng.ysm.1410693248 test-keys
ro.build.fingerprint=alps/v820_kk/v820_kk:4.4.2/KOT49H/1410693248:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties
ro.custom.lcm.id=sh1282_boe_c3_lianxin
ro.custom.camera.version=ov5648_mipi_raw s5k5eayx_yuv s5k5e2ya_mipi_raw siv121du_yuv
ro.custom.camera.pixel=main_500w_and_200w__sub_200w_and_30w
ro.custom.fm.id=6628
ro.custom.modem=hexing82_hspa
ro.custom.alsp=APDS9930 ltr558
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP1.V2.11
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/v820_kk/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# switch bluetooth stack solution
#
ro.btstack=blueangel
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6582
mediatek.wlan.module.postfix=_consys_mt6582
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Firstly your device model is not clear.But according to your build.prop and MTk droid tools we can assume that your device is Lenovo s850 or close to it.
Your device have-
Chipset- MT6582 (confirmed as detected MTK droid tool)
Ram- 1GB
Network- 2G/3G
Android Version- Kitkat (4.4.2) Confirmed as"" ro.build.version.sdk=19 ""
Answers to some of your questions:
I don't have a file called "modem.img" in my stock ROM System/etc/firmware folder. I do have a file "modem_1_wg_n.img" but copying or not doesn't seem to make any difference.
The stock ROM does not have a System/lib/modules folder, so should I delete the Port ROM modules folder?
Click to expand...
Click to collapse
->Modem.img is renamed to "modem_1_wg_n.img" in kitkat roms.Earlier it was named as only modem.img.So both are same just name is different.
->Same situation is with "modules" folder.Older roms had "modules folder but Kitkat rom modules are built in kernel i.e under boot.img.So you should skip that step.Leave that untouched.
The only step I have not followed in the guide is this:
"Lastly drag and drop a launcher like nova,apex or any to system/app/ of port zip in case port launcher did not worked."
Is this a necessary step?
Click to expand...
Click to collapse
->No it is not necessary unless you facing a force close error after booting your rom.
Now tell me steps in breif your are following for porting.I will help you.Also attach your recovery.fstab file here and updater script of stock rom and the rom which your ported.
One more question - You said that you were facing no network issue on your stock rom too.So you never received mobile network since you bought this device?
And for quicker contact you can contact me on facebook(digyvijaykumar123),wahtsapp(8409108997) too.
Good luck.
digyvijaykumar123 said:
attach your recovery.fstab file here and updater script of stock rom and the rom which your ported.
Click to expand...
Click to collapse
Attached:
recovery.fstab from stock ROM (MTK Droid Tool backup)
This is identical to recovery.fstab from latest 'cooked' ROM that I've tried to port (hanging on boot).
update-script from stock ROM
update-script from ROM I'm trying to port (this is from after it's been cooked - prior to kitchen there is no META-INF folder)
digyvijaykumar123 said:
You said that you were facing no network issue on your stock rom too.So you never received mobile network since you bought this device?
Click to expand...
Click to collapse
Kind of, it's not properly connected to the network since I bought the phone: it connects for a split second, enough to download txt messages, but not long enough to make a call. It repeatedly gives a pop up that says “Unfortunately the Process.com.android.phone Has Stopped” until I disable SIM 1 in the Android settings. I've googled and tried the usual solutions to fix this but nothing has worked. The SIM works on other phones. I'll get a micro SIM and try that in the second SIM reader slot.
I’m working on a thorough, step-by-step response to your guide which I’ll post when I can finish it.
I just flashed the ROM ported from the s850 ROM, modified with the MTK DT backup alterations. On phone reboot it showed the "welcome" logo then the screen went black. This is the first ROM I've flashed that has produced a black screen.
Eclectica said:
Attached:
recovery.fstab from stock ROM (MTK Droid Tool backup)
This is identical to recovery.fstab from latest 'cooked' ROM that I've tried to port (hanging on boot).
Click to expand...
Click to collapse
Just checked this and it's very different from the recovery.fstab extracted from the CWM backup. I'm not sure why, perhaps MTK DT encodes it differently? Perhaps because of the way I extracted it? Anyway, I suspect that this is the problem with this ROM port.
The recovery.fstab content from the CWM backup is the following:
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
#################################################
###############################################################
###############################################################
###############################################################
I'm going to try port the same s850 ROM again using the CWM backup for stock ROM.
I've tried another three ports but none of them have loaded.
I'll post the entire process here from the backups I'm using a 'Stock ROM' to the final OUTPUT_ZIP Porting ROM.
I have backups of the stock ROM from CWM, shown here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and also from MTK Droid Tools:
I think that MTK DT does not produce a reliable recovery.fstb (as attached 2 posts above) but maybe I'm missing something.
Registering with Kitchen
I extracted recovery.img from the CWM backup in kitchen. recovery.fstab was in boot.img-ramdisk/etc.
Code:
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
#################################################
###############################################################
###############################################################
###############################################################
I replaced the mount locations in your Micromas A110Q template file “A110Q” to produce this:
Code:
# MTK
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p5
cache_mnt=\/dev\/block\/mmcblk0p6
boot_mnt=\/dev\/bootimg
data_mnt=\/dev\/block\/mmcblk0p7
sdcard_mnt=\/dev\/block\/mmcblk1p1 \/dev\/block\/mmcblk1
I renamed this file MTK and copied it to: C:\cygwin\home\username\kitchen\tools\edify_defs
Getting “system” folder.
I can get the system folder from the CWM backup or the MTK Droid Tool backup but in different ways:
Extracting the system folder from CWM is easy: I found that I could just extract the system folder from the system.ext4.tar :
This system folder is 671 MB
Extracting the system folder from MTK Droid Tools backup was more tricky. I found I could rename the file “system.ext4.img” to system.img and kitchen would extract it and then open Ext2Explore. (It gives the warnings “Qt: Untested Windows version 6.2 detected!” and the pop up "Unable to read disk. Please make sure you are running application as an Administrator." as you predict in your guide.) When Ext2Explore loads I could open the “WORKING_XXXXXX_XXXXXX” folder, open the “system” folder and find a file called “system.img” 921.600KB (not system.ex4.img) and successfully extract that the the same folder. Kitchen then advises “A valid boot.img is not found. You have the option to add a 'fake' boot.img so that the features of the kitchen can still function normally.” and I selected the default “Add boot.img” y. Resulting in the following:
Code:
Copying null boot.img ...
Looking for symbolic links under /system/bin ...
None detected
Adding a default set of toolbox symlinks to update-script ......................................................................................................................................................................
Adding dumpcrash symlink ...
Looking for symbolic links under system/xbin of working folder ...
None detected
Found ./system/xbin/su
Updating update-script with su entry and symbolic link
Remove install-recovery.sh from update-script (y/n)? (default: n): n
Not removing
Remove system/etc/install-recovery.sh (y/n)? (default: n):
Not removing
Listing of WORKING_010515_120816:
total 12
-rwxrwxr-x 1 Rob None 6144 Jan 5 12:09 boot.img
drwxrwxr-x+ 1 Rob None 0 Jan 5 12:08 META-INF
drwxrwxr-x+ 1 Rob None 0 Jan 5 12:09 system
Finished setting up working folder!
The Working folder ROM info:
Code:
Working folder information (v0.224)
Android OS version : 4.4.2
Device : LENOVO
Model : LENOVO
ROM Name : ALPS.KK1.MP1.V2.11
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : UNKNOWN
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
Here is a screen shot of the system folder via the MTK DT backup:
This system folder is altogether 662MB.
The system folders from MTK DT and from DWM are different. Here is a comparison:
bin: 12,323,955 (from the MTK DT backup extraction) vs 12,324,456 (from the CWM system folder. )
fonts: 19,000,960 (MTK DT) vs 19,000,993 (CWM)
lib: 139,120,006 (MTK DT) vs 139,120,039 (CWM)
media: 59,754,472 (MTK DT) vs 59,898,584 (CWM)
Everything else is the same size. The MTK DT backup and the CWM backup were made on the same day but not immediately consecutively. I’m not sure if the MTK DT backup was made prior to CWM being installed or not.
Stock boot.img
I followed your instructions ‘to a t’. Again, the MTK DT backup boot.img and the CWM backup boot.img files produce slightly difference results.
CWM: boot.img-ramdisk 1.49MB vs MTK DT: boot.img 1.55MB
The only file that differs is adbd which is 203 KB in MTK DT backup and 144 KB in the CWM backup.
Both “zImage” files are the same size: 4750 KB
PORTING
This time I used what seems to be the most plain, official LENOVO S850 ROM that I can find on needrom. It was listed by [email protected] and is intended to be SP Flashed. For some reason it’s a bit of a monster ROM. It has three folders:
The folder “apdb” (178 KB) has the files: “APDB_MT6582_S01_KK1.MP1_” and “APDB_MT6582_S01_KK1.MP1__ENUM”
“modemdb" (21.8 MB)has the following:
and target_bin (1.74 GB!) has the following files:
So because the system folder is a .img I followed your guide step “IF YOUR ROM IS SP_TOOLS FLASHABLE THEN DO THESE TO EXTRACT SYSTEM FOLDER FROM IT:” again. This is the kitchen terminal output:
Code:
Android Kitchen 0.224 - by dsixda (xda-developers.com)
============================================================
> MAIN MENU
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Zipalign all *.apk files to optimize RAM usage
6 - Change wipe status of ROM
7 - Change name of ROM
8 - Show working folder information
0 - ADVANCED OPTIONS
00 - LEGACY OPTIONS (old and rarely used)
99 - Build ROM from working folder
u - Kitchen Info/Update/Donate
x - Exit
Enter option: 1
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
Please wait ...
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0, r=refresh): 1
Found original_update/system.img
The new working folder will be named WORKING_010615_121157
Change the name (y/n)? (default: n):
Creating working folder WORKING_010615_121157 ...
Copying system.img ...
Adding an update-script ...
‘system.img’ -> ‘../system.img.ext4’
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img.exe successfully compiled
Converting system.img.ext4 into a format for unpacking ...
#####################################################################
READ INSTRUCTIONS BELOW TO EXTRACT FILES FROM ext4_system.img:
1) Ignore the 'Cannot Read Disk' warning dialog (press 'OK') if it
appears!
2) When Ext2Explore appears, use 'File->Open Image' to open:
C:\cygwin64\home\Rob\kitchen\WORKING_010615_121157\system\ext4_system.img
3) After it loads, right-click on the new icon displayed in the left
frame, and select Save
4) Select C:\cygwin64\home\Rob\kitchen\WORKING_010615_121157\system
5) Wait for extraction to finish and then close Ext2Explore
#####################################################################
>>>> PERFORM THE STEPS ABOVE BEFORE PRESSING ENTER! <<<<
Press Enter to continue
Qt: Untested Windows version 6.2 detected!
The Ext2Explore warning pops up: “Unable to read disk. Make sure you are running as an Administrator”
Code:
The file ext4_system.img has been fully unpacked into:
/home/Rob/kitchen/WORKING_010615_121539/system
Warning: A valid boot.img is not found. You have the option to add a
'fake' boot.img so that the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM's
ZIP file when it is built.
Add boot.img (y/n)? (default: y):
Copying null boot.img ...
Looking for symbolic links under /system/bin ...
None detected
Adding a default set of toolbox symlinks to update-script ................................................................................................................................................................................
Adding dumpcrash symlink ...
Looking for symbolic links under system/xbin of working folder ...
None detected
Listing of WORKING_010615_121539:
total 12
-rwxrwxr-x 1 Rob None 6144 Jan 6 12:17 boot.img
drwxrwxrwx+ 1 Rob None 0 Jan 6 12:15 META-INF
drwxrwxrwx+ 1 Rob None 0 Jan 6 12:17 system
Finished setting up working folder!
Would you like to view this ROM's info (y/n)? (default: y):
PORT ROM info:
Code:
Working folder information (v0.224)
Android OS version : 4.4.2
Device : S850
Model : Lenovo S850
ROM Name : S850_ROW_S119_140627
Rooted (Superuser app + su) : NO
Rooted (unsecured boot.img) : UNKNOWN
(the rest are : NO)
The Kitchen Working folder is 1.11 GB. It contains META-INF, system and boot.img.
PATCHING BOOT.IMG:
After extracting the boot image I replaced the zlmage file (1 KB) with the ‘Stock ROM’ zlmage file (4750 KB).
Editing Build Prop:
In build.prop of Port ROM I changed “ro.product.device=S850” to “ro.product.device=MTK” and saved the file.
I copied modem_1_wg_n.img across.
I copied libcameraservice.so across.
The stock ROM does not have a System/lib/modules folder so I didn’t touch that.
The stock ROM’s keyboard was actually buggy so I didn’t touch this either hoping it will improve things.
Then built the ROM.
It flashed fine but just hangs on the boot "welcome" logo, as most of the previous port attempts have also done.
I've done my best to be systematic and clear about this process - like your excellent guide - but please let me know where things are ambiguous.
Does any of this process suggest I'm making a mistake anywhere? What do you suggest I try next. I'll try pinging you on facebook. Thanks for the help!
So my SIM card did not work with the original stock ROM, giving “Unfortunately the Process.com.android.phone Has Stopped” errors. That was in slot 1.
I have now tried a second 'micro' SIM in slot 2. It doesn't give any pop up errors but it can't connect to the network either.
Interestingly, now that the 2nd 'micro' SIM card is inserted into the phone, when I insert the 1st SIM as well the phone doesn't give pop up errors update - the phone does still pop up with the same errors. Neither will connect.
New Zealand has the following phone frequencies for the companies my SIMs are for:
SIM 1: 2G 900Mhz and 1800Mhz
SIM 2: 3G 850mhz & 2100mhz
According to the phone seller's description (which could be completely false) the phone should support the following:
2G: GSM 850/900/1800/1900MHz
3G: WCDMA 850/2100MHz
Therefore I'm hoping the connection problems are down to the ROM and not the phone capability!
MT6592
I want to port Huawei Honor 3X PRO's firmware to my Philips Xenium i908. Both MT6592. The only difference in specs is the display inch. 5.5 vs 5.0, aaand different partition scheme. If it fails, and i can reformat and put my rom back, then no problem. (I can fix NVRAM too with backup! I do this after format), but will reformat bring it back? I haven't tried with different scatter file.
Edit: Nevermind. I'm done fighting with scatter file.
Thanks man!
After two months of trying to get Huawei's Emotion UI on my phone. You're a life saver! And to think I did it in one hour. Just fixed audio. SIMs are working, wifi too. Now to find out why it does not wake the display when i press power buton. I have to reboot through adb, or keep the power button pressed.
Ported Huawei Honor 3x Pro G750-T20 KK EMUI2.3 ROM to Philips Xenium i908. Both MT6592.
Maaan! Thanks!
Related
Here is the latest "Verizon patch" OTA for your Nexus 7 (2013) LTE for anyone that wants it. The OTA doesn't seem to push unless you pop in a VZW SIM card. This is Android 4.4.2 Revision 2 and is 37MB in size. It applies only to Nexus 7 (2013) LTE devices on build KOT49H and will update you to build KVT49L. It was done at Verizon's request so I cannot confirm 100% this update doesn't kill puppies. It didn't break my ability to use my phone SIM in my Nexus 7 and tethering (I have a this on my phone data plan) still worked so not sure how evil it is.
Direct Download: Google
Unrooted, stock users can use the sideload instructions here.
Rooted stock users should not flash this OTA.
This patches a lot of things, including the radio, breaks root, and replaces the recovery. I wouldn't be surprised if it replaced your entire music library with Britney Spears tracks.
Instead, the factory recovery images are available now at Google's Developer website. If you want to flash to this version without losing data or replacing your recovery (you will lose root but reinstall Superuser with TWRP/CWN/Philz), then download the factory recovery image and modify it.
Use the install script below (removed -w from fastboot flash image) and remove recovery.img, userdata.img, and cache.img from image-razorg-kvt49l.zip. I attached the script as flash-all.bat.txt for convenience. Remove the .txt extension from it if you want to use it.
flash-all.bat
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-deb-flo-04.02.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-deb-deb-z00_2.42.0_1204.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-razorg-kvt49l.zip
echo Press any key to exit...
pause >nul
exit
build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KVT49L
ro.build.display.id=KVT49L
ro.build.version.incremental=979340
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue Jan 14 20:22:58 UTC 2014
ro.build.date.utc=1389730978
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfj11.cbf.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 7
ro.product.brand=google
ro.product.name=razorg
ro.product.device=deb
ro.product.board=deb
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=deb
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=razorg-user 4.4.2 KVT49L 979340 release-keys
ro.build.fingerprint=google/razorg/deb:4.4.2/KVT49L/979340:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
#
# from device/asus/deb/system.prop
#
#
#set prefer network type
#LTE, GSM, WCDMA(9)
#
ro.telephony.default_network=9
#Display Traditional Chinese/Simplified Chinese carriers name
persist.radio.use_cc_names=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.radio.apm_sim_not_pwdn=1
ro.opengles.version=196608
ro.sf.lcd_density=320
persist.audio.handset.mic=dmic
persist.audio.fluence.mode=endfire
persist.audio.lowlatency.rec=false
af.resampler.quality=4
camera.disable_zsl_mode=1
persist.hwc.mdpcomp.enable=true
ro.audio.monitorRotation=true
ro.qualcomm.bt.hci_transport=smd
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
media.aac_51_output_enabled=true
debug.egl.recordable.rgba8888=1
ro.qc.sensors.wl_dis=true
ro.qualcomm.sensors.smd=true
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.r_buffer_cache_size=4
ro.hwui.path_cache_size=24
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=5
ro.hwui.texture_cache_flushrate=0.5
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Tejat.ogg
ro.config.alarm_alert=Oxygen.ogg
fmas.spkr_6ch=35,20,110
fmas.spkr_2ch=35,25
fmas.spkr_angles=10
fmas.spkr_sgain=0
ro.carrier=unknown
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.gms
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
ro.facelock.black_timeout=1250
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=1000
ro.facelock.use_intro_anim=true
ro.media.effect.bgdropper.adj=0.2
camera.flash_off=0
ro.setupwizard.network_required=true
ro.com.widevine.cachesize=16777216
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
No need to do all that. Just be stock and have stock recovery installed. Take the ota and reroot. Being unlocked and rooted won't cause a problem but you will loose root because like I said reroot. If you have a custom recovery it will just not install causing no problems.
[Q] [Help] "Mann Zug A18" android version 4.3 boot welcome and black screen
I'm newbie and sorry for my English Language
Spec Model Mann zug3 android 4.3 quard core ram 1 gb screen 480x800
My model don't root
1.I try to change bootanimation.zip on my device by adb command , It all OK , when boot then welcome screen and then animation screen that I create and go to main display
2.I try to change Product Name by pull build.prop then edit and push to system and reboot , Problem! my device boot Welcome then go to black screen cannot touch active, so I go to recovery mode and wipe data and patition by hole power + volume down and reboot again , but still the same problem
I don't know how to do next step, please help me or suggest me please :crying:
this is file build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JLS36C
ro.build.display.id=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.version.incremental=W992.6.01.01
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Tue Jul 22 12:28:06 CST 2014
ro.build.date.utc=1406003286
ro.build.type=userdebug
ro.build.user=root
ro.build.host=redhat6.2
ro.build.tags=release-keys
ro.product.model=A18
ro.product.brand=A18
ro.product.name=A18
ro.product.device=A18
ro.product.board=MSM8610
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=A18
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8610
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A18PLUS_CR
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.fingerprint=MANN/A18PLUS_CR/A18PLUS_CR:4.3/JLS36C/W992.6.01.01:userdebug/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for msm8610
#
# Use reference RIL for initial bringup
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
persist.radio.msgtunnel.start=false
persist.radio.atfwd.start=false
# Start in wcdma+gsm mode
ro.telephony.default_network=0,1
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
persist.dsds.enabled=true
ro.multi.rild=true
#persist.env.spec=ChinaUnicom
#
# system props for the cne module
#
persist.cne.feature=0
# system prop for override memlimit to enable cne
persist.cne.override.memlimit=1
# Skip /sys/power/wait_for_fb_* nodes and
# force FB to be always on
debug.sf.fb_always_on=1
debug.composition.type=dyn
debug.gralloc.map_fb_memory=0
debug.hwc.dynThreshold=1.5
dev.pm.dyn_samplingrate=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=96m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=5m
ro.hdmi.enable=true
tunnel.decode=false
#8x10 does not support tunnel av playback
#this prop should be set to false all the time
tunnel.audiovideo.decode=false
lpa.decode=false
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
mm.enable.qcom_parser=130815
# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs
vidc.debug.level=1
#
# system props for widevine
#
persist.gralloc.cp.level3=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
#telephony.lteOnCdmaDevice=1
telephony.lteOnCdmaDevice=0
# simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hmct.sdcard.change=1
persist.sys.hmct.primary.st=internal
ro.hmct.TFcard.supported=true
ro.hmct.hasRealPhoneStorage=false
#
# System prop for enabling the cdrom feature
#
persist.service.cdrom.enable=1
#
# System prop for default USB configuration
#
persist.sys.usb.config=diag,serial_smd,serial_tty,rmnet_bam,mass_storage,adb
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=fluence
# Reduce Background apps limit
ro.sys.fw.bg_apps_limit=20
# System property for cabl
# zhaolinhu modified from 1 to 0
ro.qualcomm.cabl=0
# Enable Fast Dormancy 103
persist.env.fastdorm.enabled=true
#system props for restore modem_pref support
persist.radio.restore_mode_pref = 1
#
# dirty ratio value when enable UMS
#
ro.sys.umsdirtyratio=20
# Enable RST packet drop
persist.data.tcp_rst_drop=true
# system prop for NFC DT
# ro.nfc.port=I2C
#
#DASH video streaming
#Specify max allowed resolution/bandwidth for representations
#Set allowed avsync window during playback
#
persist.dash.max.rep.resolution=1280*720
persist.dash.max.rep.bandwidth=4000000
persist.dash.avsync.window.msec=100
tunnel.audio.encode = false
#PPPOE config enable
#
ro.config.pppoe_enable=1
# system prop for storage test
ro.external.sd.path=/storage/sdcard1
#modified by QKD 20131017 ro.hmct.sdcard.change
ro.hmct.sdcard.change=1
persist.sys.hmct.primary.st=internal
#
# Version of hardware and software.
#
ro.hardware.version=V1.00
ro.software.version=A18_plus_SW_A18_E_V01_140718
ro.hmct.sw.internal.version=A18_plus_SW_A18_E_V01_140718
#ro.hmct.ota.product=A18PLUS
#default not roaming
ro.com.android.dataroaming=0
ro.sms.8X10=1
ro.hmct.sms.max.capacity = 2000
ro.hmct.sms.nobox = true
#modem version
ro.hmct.modem.version=M8612AAAAANLYD193517BA
#add by huyan
ro.sf.lcd_density=240
# hisense style for shutdown dialog
ro.hmct.hisense.style=0
#tianhaiyan add for new card propt
persist.env.phone.newsim = true
#jingnannan add for active dualmode-card on dsds product.
persist.env.phone.autoprovision = true
ro.hmct.product.operator = export
ro.export = true
#timezone
persist.sys.timezone=Africa/Casablanca
#add by xiaoqian for UI2.0
persist.hmct.origin.style=1
#adb auth
ro.adb.secure=1
#add by huangzengzhi
# add by xiaoqian for bootanim
ro.product.unicom=1
#add by dingchao for usb
ro.hmct.bicr.yes=yes
#fm volume add by zouyanfei
persist.sys.hmct.fm.vol=2500
#add by zouyanfei for volumepannel
persist.sys.hmct.volpannel.vol=100
#add by libing for camera preview
camera.hmct.optm.prev=1
ro.hmct.mvno.mcc=208
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=World.ogg
ro.config.notification_sound=Pizzicato.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=1
ro.qc.sdk.izat.service_mask=0x5
ro.gps.agps_provider=1
Spec Model Mann zug3 android 4.3 quard core ram 1 gb screen 480x800
My model don't root
Click to expand...
Click to collapse
just try VROOT
additional - maybe interesting: corresponding branch @Russian board 4PDA (only Russian language! - that's why look at "911 - Quick help for English speaking users"
same problem
You're English is good, better than my Russian. I bought the same phone, Mann Zug 3 with snapdragon 200 msm8212, and bricked it the day I got it. Similar problem, boot loop thanks to a custom boot screen I installed after rooting it (thanks geohot for the towelroot). I got lucky the first time and it eventually rebooted with me inserting the USB and hitting the volume buttons randomly trying to get it into bootloader mode (I know think it can't be done with out an app). Because I'm a slow learner, I then went on to try and install cwm from a similar phone makeup and bricked it again. I still have stock recovery, for all the good it does me, and I couldn't get Odin to recognise it or flash tool. I cant even find a rom to flash from the sd recovery that works. There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot". Any help from all you brilliant devs would be so gracious.
Cheers
Patrick Futch said:
I bought the same phone, Mann Zug 3 with snapdragon 200 msm8212,
Click to expand...
Click to collapse
can provide the link (to the seller page) where did you obtain (buy) your phone?
Patrick Futch said:
There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot".
Click to expand...
Click to collapse
that is something like "Factory mode" -- for flashing with special type of ROM (NOT *.zip file, but "folder with files")
there are ROM for the similar device (MANN Zug3 A18 --- but only with 512MB RAM & GPU Adreno 203);
Mann Zug A18Plus (Falcon) - its device with 1GB RAM & GPU Adreno 305 (i.e. "302"))
// & acc. to build.prop at first post of this thread -- this thread is about Mann Zug A18Plus (Falcon)
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JLS36C
ro.build.display.id=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.version.incremental=W992.6.01.01
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Tue Jul 22 12:28:06 CST 2014
ro.build.date.utc=1406003286
...
ro.build.product=A18PLUS_CR
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=A18PLUS_CR-userdebug 4.3 JLS36C W992.6.01.01 release-keys
ro.build.fingerprint=MANN/A18PLUS_CR/A18PLUS_CR:4.3/JLS36C/W992.6.01.01:userdebug/release-keys
....
#
# Version of hardware and software.
#
ro.hardware.version=V1.00
ro.software.version=A18_plus_SW_A18_E_V01_140718
ro.hmct.sw.internal.version=A18_plus_SW_A18_E_V01_ 140718
#ro.hmct.ota.product=A18PLUS
...
#modem version
ro.hmct.modem.version=M8612AAAAANLYD193517BA
Click to expand...
Click to collapse
& that's why (because of inconsistent GPU) after flashing this ROM to Mann Zug A18Plus (Falcon) - there is "grey lines" only on the screen
so I DO NOT recommend you to flash this ROM;
&& maybe you can ask your seller to share the ROM for you phone (?)
DX.com
I got the phone from dealextreme.com (now dx.com). I found what I think is the producers' (Mann) website but it was more concerned with advertising graphics than support or even instructions. I keep hoping for a universal unbrick method, but none that i've found seem to work with a phone in bootloop and no fastboot/download/bootload mode. And yeah, that double volume and power button thing seems to be manufacturer input method.
---------- Post added at 07:18 PM ---------- Previous post was at 07:05 PM ----------
Cant read it for a while. Excited by the content. Thanks a ton.
Patrick Futch said:
... There's one more option of holding down the power and both volume buttons that leads to Chinese and English saying that the "Int SD card failed, hold the power button to reboot".
Click to expand...
Click to collapse
there is the firmware for flashing with this mode
I have the same problem - bootloop
I just got this phone (falcon edition) and it worked fine the first time I booted.
Then I put in a new sd card and sim and since then it won't boot. I always an image of the green andorid on its back with the middle open and a big red triangle.
After a while it will try to reboot itself only to get to the same image.
I've also tried pushing all the buttons to get into some kind of recovery but nothing works.
Anyone have any suggestions?
Thanks
that is recovery mode (locked)
spidersilver said:
an image of the green andorid on its back with the middle open and a big red triangle.
Click to expand...
Click to collapse
that is recovery mode (locked)
just try to press soft keys ( "home" or "back" or "menu")
--- than appear normal recovery items
then make wipe data / factory reset
MANN zug 3 Flacon
Hi , im new in the xda community , I'm french and i'm sincerly sorry for my so bad english ...
I've just bought my new phone MANN zug 3 A18+ , he got MSM8212 Qualcomm QuadCore 1.2Ghz , 1 GB ram , 4GB ROM (so the falcon one)
Yesterday i found a path to root him ( take rootGenius.exe , for Ascend G6 and it works) but i'm don't sure if it was completly rooted.
And like a andro-geek i tried so much possibilities with that !
But after flashed a boot.img , for install TWRP recovery via Flashify (the app) my phone bootloop with a white screen , i can go to "fastboot downloading" mode , original recovery and a mode which i don't know (vol + , vol - and power) with chinease letters and a message "no update on TF card" !
So , i need to restore my phone , unbrick him , install the stock rom or an other rom ?
I tried to read the topics in russian on "4PDA" but .. I didn't learn russian and google traduction is really ... approximatif , so , Vladimir i need you're help x) !
Thanks very much
Flash stock ROM Zug 3 Falcon (FTM(?) mode)
Papaya59 said:
But after flashed a boot.img , for install TWRP recovery via Flashify (the app) my phone bootloop with a white screen , i can go to "fastboot downloading" mode , original recovery and a mode which i don't know (vol + , vol - and power) with chinease letters and a message "no update on TF card" !
Click to expand...
Click to collapse
there is an archive on MEGA with many req. files for MANN Zug 3 Falcon
0. assure that your device is really MANN Zug 3 Falcon -- check if battery capacity is 2930 mAh (look above cover ))
1. download and unpack archive "a18plus.v1.zip" from MEGA::\\ROM\stock
2. copy unpacked folder "a18plus.v1" archive to 'root' of clean SD card
3. insert SD card into device
4. boot device into "mode which you don't know (vol + , vol - and power) with chinease letters"
... &the flashing is ROM have to start automatically
(/if something wrong - try to rename folder on SD-card into ""a18plus" (without ".v1")
//src of instr.
###############addit.
it looks like bootloader is 'locked from flashing' on MANN Zug 3 Falcon
that's why simple flash boot is impossible;
have try before:
Code:
d:\MANN_ZUG3\MEGA\recovery>fastboot flash recovery Philz_Touch6.57.9MANN_ZUG3Falcon_portedFROMc230w.img
target reported max download size of 515899392 bytes
sending 'recovery' (8316 KB)...
OKAY [ 0.327s]
writing 'recovery'...
[COLOR="Red"]FAILED (remote: partition table doesn't exist)[/COLOR]
finished. total time: 0.334s
but
Code:
d:\MANN_ZUG3\MEGA\recovery>fastboot boot Philz_Touch6.57.9MANN_ZUG3Falcon_portedFROMc230w.img
downloading 'boot.img'...
OKAY [ 0.314s]
booting...
OKAY [ 0.089s]
finished. total time: 0.404s
Flash stock ROM Zug 3 Falcon
Hey Wladimir ! Sorry for the time , i had internet problems !
I tried to do what you said but it doesn't worked , my phone already looks like this (picture)
I tried to put the rom on differents memory cards but , again it doesn't worked , i tried to delete ".v1" but it doesn't worked can you help me again ?
It looks like no update file in TF card :/
Thanks again , bye !
problem with my Mann Zug 3
I write from Italy (sorry for my bad English). In the last April I has buy on internet Mann smartphone model Zug 3. For the first month the zug 3 was perfect. But three week ago he began with the problem with the network connection. Now, I have tried to check the smartphone with android app for search the problem, I have tried to check imei code....but I don't have solved the problem. Do you have a solution?
Please wake up one phone to download the original file recovery
Please do help me the phone I'm looking for the original recovery
Hi, thank you for taking the time reading my post and any help or directions you could give to solving my problem.
I was given a phone (Samsung Galaxy Note 3) to replace my aging LG Optimus P509.
When I received the SGN3 I did a wipe of the user data so it was pristine through the recovery feature to put it back to 'stock'.
And that's when my issues began.
PROBLEM #1
First thing that happened after wiping is I 'lost' the internal 16Gb SD storage.
PC would only see the 2Gb's of application storage. Android system would see the 16Gb's, BUT it was reported as 'filled' with 15Gb's of data. If I just DID a wipe of the user data then where did all this 'data' come from???
So started looking around the system using different root explorers to see if I could manually delete the bloated data.
Couldn't find it.
I DID discover that the 'folder' that the 16Gb storage was under had no permissions. Just a series of dashes where the permissions would be listed. The OS's corrupted somehow...
Used a different Home loader and IT was reporting the 16Gb internal SD storage as there and pretty much empty. But still no access.
So I take it to a 'phone repair' place and explain to the guy what my issue was. Figured he was just going to look around and see what he could see. Nope, he starts pressing buttons and gets to the "recovery screen"...eventually. When I realized what he had did it was too late to stop him.
PROBLEM #2
The 'recovery screen' was not what I once saw, blue and orange screen with a droid on it, to a black screen with white characters with three options. Fast Boot, Recovery, Normal
AND the screen was now upside down in orientation and you could not use the 'enter' key (volume up). Refuses to select anything. So no more recovery option.
I learned through researching the issues here on XDA that a replacement ROM would be something I should do to address my issues, just reflash. Start anew.
I learned that the Device (Samsung Galaxy Note3) is NOT a SGN3! It's a KnockNote (my term). To my understanding you cant flash an OEM ROM on a non-OEM device. It's a Mediatek MT65xx device, made by China.
So I start looking around for a ROM to put on there. Not much that I can understand...
Here is the kernel information that 'could' help with identifing the device.
Code:
SM-N9006
Android version: 4.4
Baseband Ver.: N9006ZCUBMI3
Kernel Version: 3.4.0-1590669
[email protected] #1
Wed Sep 11 23:59:42 KST 2013
Build Number: JSS15J.N9006ZCUBMI5
Possible model (android tuner, build information) MT6620 (mt6582)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB5.MP.V1.5
ro.build.version.incremental=eng.rs.1390483692
ro.custom.build.version=.N9006V116En20140123
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.4
ro.build.date=2014年 01月 23日 星期四 21:29:52 CST
ro.build.date.utc=1390483792
ro.build.type=user
ro.build.user=rs
ro.build.host=rs-ThinkStation-D30
ro.build.tags=test-keys
ro.product.model=Samsung GALAXY Note 3
ro.product.brand=alps
ro.product.name=lcsh82_wet_jb5
ro.product.device=lcsh82_wet_jb5
ro.product.board=lcsh82_wet_jb5
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lcsh82_wet_jb5
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lcsh82_wet_jb5-user 4.4 JDQ39 eng.rs.1390483692 test-keys
ro.build.fingerprint=alps/lcsh82_wet_jb5/lcsh82_wet_jb5:4.4/JDQ39/1390483692:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.timezone=Asia/Shanghai
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB5.MP.V1.5
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB5.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=180
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MT6620
mediatek.wlan.module.postfix=_mt6620
ril.radiooff.poweroffMD=0
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.ringtone=Over_the_horizon.mp3
ter.service.enable=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So I began using it as basically a PDA until I could get things sorted out.
PROBLEM #3
I allowed my niece (9yrs) to play some games on it and...she set up a very nice and complicated pattern lock that was so pretty to her that she forgot the pattern. not a problem as long as wi-fi or cell service is on...which this device has neither.
(no SIM, I turned off wifi before I handed it to her)
My questions are these:
Q 1 : Can I install a recovery ROM, stock ROM to the device?
If so, can you direct me (link) to where I can find the one I should use, based on your knowledge?
Q2: I can not get into the phone (pattern lock), is there a way to establish a connection to the phone even though I don't have access to 'developer options'?
Q3: Could you describe the steps needed to complete this task, I KNOW there are tuts galore. That's part of the problem. So many different ways, options, etc.
Since I am residentially challenged at the moment due to a fire this device is pretty critical to me and I can't screw it up, no fails, no bricks.
If you can offer any advice on how to resolve my issues your help is very much appreciated.
If you need any more information about the device or require clarification please ask your questions.
Additional Information:
No WiFi (local/cell)
No Cellular Service
No 'developer/debug options' (because I am locked out of device with a pattern lock, see above) :crying:
No Adb
***BoM***
If this post is in the wrong place please direct me where to place it. XDA is a large place with a lot to sort through.
***EoM***
Hello
I have Cube U25GT-BN MTK8127 tablet with V1.2_20141107 firmware Android 4.4.2 + root
When I install from himarket or cube or zhi market
google play
and
google play services
and
google services framework
I get error "Unfortunately, Google Play services has stopped"
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=U25GT-BN_V1.2_20141107
ro.build.version.incremental=eng.zmchivin2.1415326784
ro.custom.build.version=1415326784
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Fri Nov 7 10:20:58 CST 2014
ro.build.date.utc=1415326858
ro.build.type=user
ro.build.user=zmchivin2
ro.build.host=chivin-All-Series
ro.build.tags=test-keys
ro.product.model=U25GT-BN
ro.product.brand=CUBE
ro.product.name=U25GT-BN
ro.product.device=U25GT-BN
ro.product.chivinproduct=U25GT-BN
ro.product.chivinversion=U25GT-BN_V1.2_20141107
ro.product.customversion=05050031A_20141107
ro.product.board=U25GT-BN
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CUBE
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=htt27_tb_t_mlc_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=htt27_tb_t_mlc_kk-user 4.4.2 KOT49H eng.zmchivin2.1415326784 test-keys
ro.build.fingerprint=HTT:4.4.2/KOT49H/1415326784:user/test-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP10.V1.16
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/htt27_tb_t_mlc_kk/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
ro.sf.lcd_density=160
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.config.pppoe_enable=1
#HTT liujihui {
ro.setupwizard.mode=DISABLED
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
persist.sys.timezone=Asia/Shanghai
ro.chivin.secure=9527
ro.product.facebook.dash=true
#HTT liujihui }
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=1
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
ril.current.share_modem=1
curlockscreen=1
ro.mediatek.gemini_support=false
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=mediatek.wlan.module.postfix=_
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Please help me.
Do you find any solution ? i have the same problem!!
cetra said:
Hello
I have Cube U25GT-BN MTK8127 tablet with V1.2_20141107 firmware Android 4.4.2 + root
When I install from himarket or cube or zhi market
google play
and
google play services
and
google services framework
I get error "Unfortunately, Google Play services has stopped"
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=U25GT-BN_V1.2_20141107
ro.build.version.incremental=eng.zmchivin2.1415326784
ro.custom.build.version=1415326784
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Fri Nov 7 10:20:58 CST 2014
ro.build.date.utc=1415326858
ro.build.type=user
ro.build.user=zmchivin2
ro.build.host=chivin-All-Series
ro.build.tags=test-keys
ro.product.model=U25GT-BN
ro.product.brand=CUBE
ro.product.name=U25GT-BN
ro.product.device=U25GT-BN
ro.product.chivinproduct=U25GT-BN
ro.product.chivinversion=U25GT-BN_V1.2_20141107
ro.product.customversion=05050031A_20141107
ro.product.board=U25GT-BN
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CUBE
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=htt27_tb_t_mlc_kk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=htt27_tb_t_mlc_kk-user 4.4.2 KOT49H eng.zmchivin2.1415326784 test-keys
ro.build.fingerprint=HTT:4.4.2/KOT49H/1415326784:user/test-keys
ro.build.flavor=
ro.build.characteristics=tablet
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP10.V1.16
ro.mediatek.platform=MT8127
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP10
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/htt27_tb_t_mlc_kk/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
ro.sf.lcd_density=160
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.config.pppoe_enable=1
#HTT liujihui {
ro.setupwizard.mode=DISABLED
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
persist.sys.timezone=Asia/Shanghai
ro.chivin.secure=9527
ro.product.facebook.dash=true
#HTT liujihui }
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=1
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
ril.current.share_modem=1
curlockscreen=1
ro.mediatek.gemini_support=false
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=mediatek.wlan.module.postfix=_
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Please help me.
Click to expand...
Click to collapse
Download es file explorer and place the gapps @ /system/priv-app, change the gapps permissions to rw-r....
freamz said:
Download es file explorer and place the gapps @ /system/priv-app, change the gapps permissions to rw-r....
Click to expand...
Click to collapse
When you said gapps you talk about a zip like this pa_gapps-modular-pico-4.4.4-20141214-signed.zip on this page http://forum.xda-developers.com/showthread.php?t=2397942
And i extract all .apk file in zip to put in /system/priv-app ??? They are other file in the zip i do nothing with?
Thx
Only the apks in priv-app. Remember to change permissions.
freamz said:
Only the apks in priv-app. Remember to change permissions.
Click to expand...
Click to collapse
ok thx a lots
bodyscape said:
ok thx a lots
Click to expand...
Click to collapse
Hi,
Could you please tell me how did you root the U25GT?
Didn't find it...
Thanks!
same problem. find no reasonable instructions for rooting of u25gt.
can anyone help?
greets
derthias said:
same problem. find no reasonable instructions for rooting of u25gt.
can anyone help?
greets
Click to expand...
Click to collapse
After a lot of trial and error - finally found the solution!
In order to root:
1. Install their "king user" app from the built in Chinese "Cube Market" (just search for the word "root" or "king user" and you'll find it).
2. I tried to root it from this app, but it didn't work, so I downloaded the PC app (kingroot #dot# net), connected the device to my PC (don't forget to enable USB debugging etc...), and it'll root it. (it's in Chinese, whenever you're not sure regarding to something, use "google translate" app with the option to take a photo of the text. there OCR is great).
3. Now the "King User" will function as "Super user" app for all the permission. I tried to change it to SU, but it didn't worked so I stayed with "king user".
That's it, your device is now rooted.
Next I installed the google apps, but again - I did it from that "Cube Market", just search for "Google" and you'll find a bundle of "Google services" including google play store. Add to this the "Google play services" (also in the Cube Market), and you're good to go.
Good Luck!
Hi and thx..
but this did not work for me somehow.
I have sent an email to the seller and he sent me after some back and forth a manual incl root program.
I've attached the files here. Accept no responsibility for problems.
root.rar is only an .doc file with pic's
worked at the first time and installed after rooting the google service automatically.
i hope i can help anyone who have the same problems
greets
Thanks for the info and files.
I did find however that the version of Root software in your post is different from the one in the instructions making it impossible to follow the instructions.
I clicked a few icons until it took me to their homepage... http://www.dashi.com/zhuodashi/shuaji.html
It seems if you download the latest version from there the version, layout and icons etc. match the instructions you provided.
Thanks
derthias said:
Hi and thx..
but this did not work for me somehow.
I have sent an email to the seller and he sent me after some back and forth a manual incl root program.
I've attached the files here. Accept no responsibility for problems.
root.rar is only an .doc file with pic's
worked at the first time and installed after rooting the google service automatically.
i hope i can help anyone who have the same problems
greets
Click to expand...
Click to collapse
The only one tuto for gapps and Google Play on Cube U25GT-BN
Hello. after one month of trials...
It's ok for me! :laugh: with my cube u25gt-bn but only with the root tool updated
Thanks a lot inspectaclueso !
You must follow instructions exactly like described on the .doc notice (into the file "root.rar") on the first page of this thread
Good luck.
derthias said:
Hi and thx..
but this did not work for me somehow.
I have sent an email to the seller and he sent me after some back and forth a manual incl root program.
I've attached the files here. Accept no responsibility for problems.
root.rar is only an .doc file with pic's
worked at the first time and installed after rooting the google service automatically.
i hope i can help anyone who have the same problems
greets
Click to expand...
Click to collapse
Can you elaborate on the steps you took? The tool is quite different from the one described in the doc. My U25GT-BN is already rooted, but I can't install google services. Thanks.
[EDIT] Never mind that, I followed the suggestion of @inspectaclueso for downloading the latest version and IT WORKED. This thread should be marked as solved!
Thx
thanks very much, but we need download lastest version in site that inspectaclueso informed
Latest update for your tablets by Cube http://yun.baidu.com/share/home?uk=288410357#category/type=0
Cube U25GT-BN root Done!
With KingRoot.apk >> http://www.apkmirror.com/apk/kingro...kingroot-5-0-6-android-apk-download/download/
Hey XDA forums, I have a Coolpad Catalyst that I'd like to be able to fix. The cause of my problem would be the firmware, I used KingRoot for a clean root and it was nice until I got the second lock screen overlay which was annoying. As well as a fast charge through KingRoot? Lol, what? Anyways I used SuperSU as a alternative and it suggested that I used SuperSU-me so I installed and ran that which would hide and "uninstall" KingRoot. I think because SuperSU was not yet supportive of my phone me uninstalling KingRoot bricked the firmware. I now can boot to the MetroPCS logo screen or recovery. I wiped the data/factory reset as well as wiped the cache partition. I have the option to reboot system now, reboot to bootloader, power down, apply update from sd card or adb.
Android System Recovery <3e>
5.1.167.10.p2.160504.LMY47V.MPCS .... <-- I believe this is the stock ROM name or firmware.
Volume up/down to move highlight; enter button to select.
-reboot system now
-apply update from ADB
-wipe data/factory reset
-wipe cache partition
-reboot to bootloader
-power down
-view recovery logs
-apply update from sd card
I'm going to MetroPCS shortly to see if they will be able to fix it or flash it. I could see a fresh flash fixing it but no one has yet to post a fix. If you need any information such as the signature for the ROM please let me know. I greatly appreciate any fix.
Extra Information: OS Build
KERNEL: Linux version 3.10.49-g3523c12-00131-gfd2b782 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed May 4 17:05:22 CST 2016
CODENAME: REL
Mainboard: cp3622a
BRAND: Coolpad
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: cp3622a
DISPLAY: 5.1.167.10.P2.160504.LMY47V.MPCS
FINGERPRINT: Coolpad/cp3622a_mpcs/cp3622a:5.1.1/LMY47V/1670845:user/release-keys
HARDWARE: qcom
ID: LMY47V
TAGS: release-keys
Extra Information: Build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47V
ro.build.display.id=5.1.167.10.P2.160504.LMY47V.MPCS
ro.build.version.incremental=1670845
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Wed May 4 16:53:40 CST 2016
ro.build.date.utc=1462352020
ro.build.type=user
ro.build.user=mine
ro.build.host=ubuntu
ro.build.tags=release-keys
ro.build.flavor=cp3622a-user
ro.product.model=Coolpad 3622A
ro.product.bluetooth.name=
ro.product.brand=Coolpad
ro.product.name=cp3622a_mpcs
ro.product.device=cp3622a
ro.product.board=cp3622a
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Coolpad
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8909
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cp3622a
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=cp3622a-user 5.1.1 LMY47V 1670845 release-keys
ro.build.fingerprint=Coolpad/cp3622a_mpcs/cp3622a:5.1.1/LMY47V/1670845:user/release-keys
ro.build.characteristics=default
# end build properties
#
# from device/yulong/cp3622a/system.prop
#
#
# system.prop for msm8909
#
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
# Start in cdma mode
ro.telephony.default_network=9
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
debug.hwc.dynThreshold=2.5
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dalvik.vm.zygotemaxfailedboots=5
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
#enable dirty rect
debug.sf.swaprect=1
#enable app buffer composition
debug.sf.hwc.canUseABC=1
#enable gpu perf hint
sys.hwc.gpu_perf_mode=1
#ro.hdmi.enable=true
#tunnel.decode=true
#tunnel.audiovideo.decode=true
#lpa.decode=false
#lpa.use-stagefright=true
#persist.speaker.prot.enable=false
#
# system props for the cne module
#
persist.cne.feature=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#codecsPARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC
mm.enable.qcom_parser=262143
# Default to AwesomePlayer
media.stagefright.use-awesome=false
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# System property for cabl
ro.qualcomm.cabl=2
# System property for QDCM
persist.tuning.qdcm=1
# System property for Screen Color
ro.qcom.screencolor=1
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System property for Camera
# System prop to allocate Reprocess buffer as "1"
# during Longshot usecase
persist.camera.longshot.stages=1
#
# dirty ratio value when enable ums
#
ro.sys.umsdirtyratio=20
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
#Set for msm8909
tunnel.audio.encode = false
ro.config.low_ram=false
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=64
#Minimum duration for offload playback in secs
audio.offload.min.duration.secs=30
#Enable offload audio video playback by default
av.offload.enable=true
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#enable dsp gapless mode by default
audio.offload.gapless.enabled=true
#Audio voice concurrency related flags
voice.playback.conc.disabled=true
voice.record.conc.disabled=true
voice.voip.conc.disabled=true
#Audio VoIP / playback record concurrency flags
rec.playback.conc.disabled=true
#Set composition for USB
# persist.sys.usb.config=diag,serial_smd,rmnet_qti_bam,adb
#Set read only default composition for USB
ro.sys.usb.default.config=none
# set max background services
ro.config.max_starting_bg=8
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
#propery to enable VDS WFD solution
persist.hwc.enable_vds=1
#property to enable image unload by audio HAL
sys.audio.init=false
#property to enable DS2 dap
audio.dolby.ds2.enabled=true
#property to change touch screen resolution
persist.sys.synaptics_dsx.qhd=false
#HWUI properties
ro.hwui.text_large_cache_height=2048
# enable sta proxy bydefault
persist.mm.sta.enable=1
#Trim properties
ro.sys.fw.use_trim_settings=true
ro.sys.fw.empty_app_percent=50
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.trim_enable_memory=1073741824
# set cutoff voltage to 3200mV
ro.cutoff_voltage_mv=3200
#min/max cpu in core control
ro.core_ctl_min_cpu=2
ro.core_ctl_max_cpu=4
#Enable B service adj transition by default
ro.sys.fw.bservice_enable=true
ro.sys.fw.bservice_limit=5
ro.sys.fw.bservice_age=5000
#set device emmc size
ro.emmc_size=8GB
#set the density
ro.sf.lcd_density=240
#enable Ycbcr WNR for camera
persist.denoise.process.plates=0
#enable fastdormancy
persist.env.fastdorm.enabled=true
persist.fd.scroff.timer=2500
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.yulong.version.hardware=P2
ro.yulong.version.btloader=1.01.001.10.P2.160504.LMY47V.MPCS
ro.yulong.version.kernel=3.10.49.10.P2.160504.LMY47V.MPCS
ro.yulong.version.software=5.1.167.10.P2.160504.3622A-MPCS
ro.yulong.version.release=5.1.167.P2.160504.3622A-MPCS10
ro.config.ringtone=Electronical.ogg
ro.config.alarm_alert=Nocturne.ogg
ro.com.google.clientidbase.ms=android-metropcs-us
ro.com.google.clientidbase.am=android-metropcs-us
ro.yulong.version.tag=LC
persist.sys.ssr.restart_level=adsp,venus,modem,wcnss
persist.sys.bugreport.enable=0
persist.sys.bugreport.senddata=0
ro.config.notification_sound=Proxima.ogg
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.google.clientidbase=android-coolpad
ro.com.google.clientidbase.yt=android-coolpad
ro.com.google.clientidbase.gmm=android-coolpad
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
persist.radio.sib16_support=1
persist.radio.custom_ecc=1
ro.frp.pst=/dev/block/bootdevice/by-name/config
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
ro.yulong.version.audiogsm=CP3622A_GSM_20160407
ro.yulong.version.audiowcdma=CP3622A_WCDMA_20160407
ro.yulong.version.audiolte=CP3622A_LTE_20160407
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=div
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.gps.agps_provider=1
ro.pip.gated=0
persist.radio.calls.on.ims=0
persist.radio.jbims=0
persist.radio.csvt.enabled=false
persist.radio.rat_on=combine
persist.radio.mt_sms_ack=20
import /system/vendor/default.prop
import /system/vendor/vendor.prop
import /system/vendor/power.prop
[UPDATE]
So I took my phone to MetroPCS and they tried to wipe the data/factory reset and cache partition which I had done numerous times prior with no success in unbricking the phone. Luckily because it was within 30 days of buying the phone they replaced it for free but will take 3-5 business days, so I would suggest doing that for now to others. As soon as I get my new phone I will be trying to copy the stock ROM and upload it here (if thats possible but I would believe so.)
For those who don't know if you come across a stock ROM for this device you may need to used ADB as a way to install the firmware package to the phone, or the best way to do it would be by downloading a .zip containing the package files and applying the update from a sdcard.
-Volume Down + Power = Recovery Mode;
-Volume Down + Volume Up + Power = Power On w/ [OFFICIAL] captioned at the bottom above "Android";
Thanks bro
I just bought the Coolpad catalyst and bricked it or bootlooped it.Im gonna take the phone back up there and see what they can do.If I can get another Coolpad please give me the firmware.And what flash tool do u use to flash the coolpad.
coolpad catalyst 3622a
Download YGDP Tool (all versions) - Android MTK
this is the tool ..i got it to connect and COM..still i need just the correctfirmware to try.
Coolpad catalyst recovery
Larry3 said:
I just bought the Coolpad catalyst and bricked it or bootlooped it.Im gonna take the phone back up there and see what they can do.If I can get another Coolpad please give me the firmware.
I have the same phone and rooted it and made a firmware copy and recovery copy my email is [email protected] contact for copy
Click to expand...
Click to collapse
Just gonna put this out there so noobs can stop ruining their phones. If you hate the kingroot lock screen then disable it in the settings. Lol it's that simple.
jestin1914 said:
Larry3 said:
I just bought the Coolpad catalyst and bricked it or bootlooped it.Im gonna take the phone back up there and see what they can do.If I can get another Coolpad please give me the firmware.
I have the same phone and rooted it and made a firmware copy and recovery copy my email is [email protected] contact for copy
Click to expand...
Click to collapse
Post a copy of it here on XDA.. PLEASE!
Click to expand...
Click to collapse
Anyone can provide drivers for this phone post here thanks..
Sent from my SM-N930T using Tapatalk
^.^7
If someone posts a link on how to copy the rom/firmware I'll get it posted. I'm getting a catalyst tomorrow. Sorry I'm a bit of a newb.
[email protected] said:
If someone posts a link on how to copy the rom/firmware I'll get it posted. I'm getting a catalyst tomorrow. Sorry I'm a bit of a newb.
Click to expand...
Click to collapse
I need the drivers please post here thanks
Sent from my SM-N930T using Tapatalk
help
anyone can shared the firmware for that coolpad 3622a, i have one stuck on logo after root, please i dont found it
Firmware would be appreciated. :'(
Help
Please, if you have the rom pass to this email: [email protected]
JT man said:
I need the drivers please post here thanks
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
same thing just happened to me ,,, how anyone found or shared a solution yet?
let me know what to do
i have this phoen adn its rooted with kingoroot. how do i get the rom off it so people can fix their phones that are stuck on teh logo screen? i actually have two of these phones and one of them is stuck on teh logo screen. i can get to the recovery screen where i assume i can put an update on a sdcard and fix it, i just need to know exactly how to get what i need off the working one to both post it to XDA and to put it on the that is stuck on the logo screen.
has anybody had any luck finding the firmware for this phone? i installed kingroot and inseterted supersu .. went good . rebooted and everything fine two days later rebooted my phone and it stuck on the boot screen . ive flashed hundreds of phones but i need the firmware. thankks in advance
looking for rom
I have a coolpad catalyst and I am wondering if anyone has a rom for this phone
unbrick 3622a
I have a zipped tutorial that contains everything needed to bring a 3622a back from the grave I am trying to figure out how to post it here. I will figure this out, and there is definitely a way to fix the 3622a. I have done completely restored mine.
lehmancurtis said:
I have a zipped tutorial that contains everything needed to bring a 3622a back from the grave I am trying to figure out how to post it here. I will figure this out, and there is definitely a way to fix the 3622a. I have done completely restored mine.
Click to expand...
Click to collapse
if you could send that file to me [email protected] thatd be greatly appreciated
lehmancurtis said:
I have a zipped tutorial that contains everything needed to bring a 3622a back from the grave I am trying to figure out how to post it here. I will figure this out, and there is definitely a way to fix the 3622a. I have done completely restored mine.
Click to expand...
Click to collapse
I'll trade you my first born if you could please pretty please send me a copy as well.... [email protected]