Related
[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
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!
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Bdazzled said:
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Click to expand...
Click to collapse
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you, I found it.
Bdazzled said:
Thank you, I found it.
Click to expand...
Click to collapse
Glad that it worked ?
Sent from my Pixel XL using Tapatalk
Same problem but with an Honor 9 (STL-AL09):crying:
---------- Post added at 06:02 PM ---------- Previous post was at 05:41 PM ----------
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I did it and it worked:good: but I can't find the build number. Can you help me ?
Please.
jacquesallet said:
Quote removed to prevent spam
Click to expand...
Click to collapse
That method only works on Samsung phones on stock ROMs or on non-stock ROMs with stock build fingerprint (aka ro.build.fingerprint property in build.prop)
So how can I find my build number? Please.
PS: when I do the manipulation, I can see:
"MacBook-Pro-de-Jacques:~ jacquesallet$ adb shell cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.version.incremental=eng.jslave.20170604.040710
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2017-05-05
ro.build.version.base_os=
ro.build.date=Sun Jun 4 04:07:10 CST 2017
ro.build.date.utc=1496520430
ro.build.type=user
ro.build.user=jslave
ro.build.host=LFG1000749994
ro.build.tags=test-keys
ro.build.flavor=generic_a15-user
ro.product.model=generic_a15
ro.product.brand=Huawei
ro.product.name=generic_a15
ro.product.device=generic_a15
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic_a15
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-user 7.0 NRD90M eng.jslave.20170604.040710 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys
ro.build.characteristics=default
# end build properties
# begin huawei emui properties
# autogenerated by build_emui_info.sh
ro.build.hw_emui_api_level=13
# end huawei emui properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=unknown
ro.setupwizard.require_network=any
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r5
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.display.id=System 5.1.0.78(055I)
ro.comp.sys_support_vndk=VA7.0-E5.0-B00005
ro.comp.sys_need_sndk=SA7.0-E5.0-B00005
MacBook-Pro-de-Jacques:~ jacquesallet$"
"ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys"
So it works isn't it?
ROOT(Magisk) + OEM Fix + Busybox + EFS Backup
Pie
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option
3.Download and copy Pie_G955F_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for S8 from official page https://twrp.me
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - Pie_G955F_Root_for_OEM_issue_devices_V*.zip, you have copied earlier
15.Once Magisk flash successfully, Reboot to System
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Oreo
PS : This guide is for Oreo and will be updated for Pie, when Pie will be out officially.
This is for Stock ROM/Kernel only If you have custom kernel, read below.
Here is guide and tool to Root S8/S8+ + Busybox + OEM Fix + Data mount fix
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy G955FD_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP latest TWRP (Edit : Latest TWRP is already fixed for data mount error, so you won't require to select data mount fix in aroma)
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14.Now select Install and navigate path to Ext SD card - G955FD_Root_for_OEM_issue_devices_V*.zip, you have copied earlier, select desired option (You must select Root option if you are on stock kernel/ROM else device won't boot) and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
For custom Kernel, you need to flash modified recovery that doesn't require data mount fix
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM
Credits : @Chainfire @topjohnwu @jesec @BlackMesa123 for OEM fix@osm0sis and some International forum discussion for original idea
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
It will be that this file, may help in the situation below:
https://forum.xda-developers.com/galaxy-s8/development/twrp-internal-storage-0mb-s8-t3769199
costafabiof said:
It will be that this file, may help in the situation below:
https://forum.xda-developers.com/galaxy-s8/development/twrp-internal-storage-0mb-s8-t3769199
Click to expand...
Click to collapse
Yes that will help in situation you have mentioned.
dr.ketan said:
Yes that will help in situation you have mentioned.
Click to expand...
Click to collapse
For the above procedure would I function before FORMAT DATE? Right?
Well just by trying to install the bug!
costafabiof said:
For the above procedure would I function before FORMAT DATE? Right?
Well just by trying to install the bug!
Click to expand...
Click to collapse
No need to format data, just flash from ext SD
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
very very much very very much very much very much very very much very very much THANK YOU.
It worked. I just had to learn to read
"- Reboot to system (Must)"
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download[/URL]
Click to expand...
Click to collapse
Wow! That really solved the issue, Thank you!!
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
This is currently only for Magisk root, I will update later for SuperSU
Credits : @Chainfire and some International forum discussion for original idea
Installation :
- Root device with magisk
- Download and Install attached zip from TWRP
- Reboot to system (Must)
Now you can reboot to recovery and check data mount is working.
Download
Click to expand...
Click to collapse
Thank you so much
I tried it on s8 plus & when system start after formatting Stuck on language choose !! Then i flashed nougat again!
Also tried it on S8+ but without formatting, i'm stuck on the lockscreen it seems like the touch screen isn't responding anymore after i flashed it. I restored from a back up to make my phone work again. Any news about this issue with S8+?
Bofahad said:
I tried it on s8 plus & when system start after formatting Stuck on language choose !! Then i flashed nougat again!
Click to expand...
Click to collapse
Marioabirached said:
Also tried it on S8+ but without formatting, i'm stuck on the lockscreen it seems like the touch screen isn't responding anymore after i flashed it. I restored from a back up to make my phone work again. Any news about this issue with S8+?
Click to expand...
Click to collapse
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
dr.ketan said:
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
Click to expand...
Click to collapse
I just tried it but the N8 zip failed, the S8 one worked better it showed internal storage size in TWRP but i couldn't use my touchscreen. I think we need one just for S8+.
dr.ketan said:
This if for S8 only
You can try my latest fix for N8, that may work cross device too. if that doesn't work then I will make for s8+
https://forum.xda-developers.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928
Click to expand...
Click to collapse
Thank you waiting S8+ one
Marioabirached said:
I just tried it but the N8 zip failed, the S8 one worked better it showed internal storage size in TWRP but i couldn't use my touchscreen. I think we need one just for S8+.
Click to expand...
Click to collapse
Oh ok got it
I will fix now and posting here in op, check first post after half an hr
You might got msg, device not supported right?
dr.ketan said:
Oh ok got it
I will fix now and posting here in op, check first post after half an hr
You might got msg, device not supported right?
Click to expand...
Click to collapse
Yes I did on the N8 zip
I have updated first post of this thread, it should work on both S8 and S8 + also added support for SuperSU
Test on S8+ and report back so this thread can move to crisscross development
dr.ketan said:
Data mount fix for TWRP on Oreo
We have similar issue on Note8 and looking to my fix on N8 @ownage16 approached me for similar fix for S8 device. He already have tested fix and reported working.
As many users are facing issue because of data mount issue with TWRP on oreo, till it get fixed here is temporary solution.
Download file according root method you are using
1. For Magisk
2. For SuperSU
Installation :
- Flash downloaded file from recovery - Ignore if any message with red color regarding data mount while flashing
- Reboot to system (This step is Must)
- Done !
Now again you can reboot to recovery to check for data mount fix.
This can be use with any working TWRP/Kernel for S8/S8+
Credits : Credits : @[email protected]@osm0sis and some International forum discussion for original idea
Click to expand...
Click to collapse
Unfortunately it also said device not supported
Marioabirached said:
Unfortunately it also said device not supported
Click to expand...
Click to collapse
Open build prop and check what is device name
Or send me build.prop
dr.ketan said:
Open build prop and check what is device name
Or send me build.prop
Click to expand...
Click to collapse
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=R16NW
ro.build.display.id=R16NW.G955FXXU1CRB7
ro.build.version.incremental=G955FXXU1CRB7
ro.build.version.sdk=26
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.0.0
ro.build.version.security_patch=2018-02-01
ro.build.version.base_os=
ro.build.version.security_index=1
ro.build.date=Mon Feb 19 23:23:54 KST 2018
ro.build.date.utc=1519050234
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD6016
ro.build.tags=release-keys
ro.build.flavor=dream2ltexx-user
ro.product.model=SM-G955F
ro.product.brand=samsung
# ro.build.product is obsolete; use ro.product.device
ro.build.product=dream2lte
ro.product.name=dream2ltexx
ro.product.device=dream2lte
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-GB
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=dream2ltexx-user 8.0.0 R16NW G955FXXU1CRB7 release-keys
ro.build.fingerprint=samsung/dream2ltexx/dream2lte:8.0.0/R16NW/G955FXXU1CRB7:user/release-keys
ro.build.characteristics=phone,emulator
# Samsung Specific Properties
ro.build.PDA=G955FXXU1CRB7
ro.build.official.release=true
ro.config.rm_preload_enabled=1
ro.build.changelist=12993656
ro.product_ship=true
ro.chipname=exynos8895
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=universal8895
ro.board.platform=exynos5
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=88
ro.hwui.layer_cache_size=58
ro.hwui.path_cache_size=16
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=2
ro.hwui.drop_shadow_cache_size=6
ro.hwui.r_buffer_cache_size=8
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=4096
ro.hwui.text_large_cache_height=2048
#
# from device/samsung/dream2lte/system.prop
#
#
# system.prop for universal8895
#
ro.arch=exynos8895
ro.kernel.qemu=0
ro.kernel.qemu.gles=0
persist.demo.hdmirotationlock=false
# read DS/SS property
import /efs/factory.prop
#Enable S.LSI USB settings
dev.usbsetting.embedded=on
#RILD debug level setting
ro.debug_level=0x494d
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product.first_api_level=24
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.opengles.version=196610
debug.slsi_platform=1
debug.hwc.winupdate=1
af.fast_period_size=192
af.fast_track_multiplier=1
ro.hdcp2.rx=tz
keyguard.no_require_sim=true
ro.carrier=unknown
vendor.sec.rild.libpath=/vendor/lib64/libsec-ril.so
vendor.sec.rild.libpath2=/vendor/lib64/libsec-ril-dsds.so
persist.radio.sib16_support=1
ro.security.icd.flagmode=multi
security.mdf.result=None
security.mdf=None
ro.security.mdf.ux=Enabled
ro.security.mdf.ver=3.1
ro.security.wlan.ver=1.0
ro.security.wlan.release=1
ro.security.mdf.release=1
ro.security.fips.ux=Enabled
ro.security.fips_bssl.ver=1.2
ro.security.fips_skc.ver=1.8
ro.security.fips_scrypto.ver=2.0
ro.security.fips_fmp.ver=1.2
security.ASKS.policy_version=000000
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
camera.disable_treble=1
ro.config.ringtone=Over_the_Horizon.ogg
ro.config.notification_sound=Skyline.ogg
ro.config.alarm_alert=Morning_Glory.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.ringtone_2=Basic_Bell.ogg
ro.config.notification_sound_2=S_Charming_Bell.ogg
ro.build.scafe.version=2018A
ro.sf.lcd_density=420
ro.sf.init.lcd_density=560
ro.error.receiver.default=com.samsung.receiver.error
sys.config.activelaunch_enable=true
ro.wsmd.enable=true
ro.frp.pst=/dev/block/persistent
ro.multisim.simslotcount=2
ro.config.dha_cached_min=6
ro.config.dha_cached_max=19
ro.cfg.dha_cached_max=24
ro.config.dha_empty_min=8
ro.config.dha_empty_init=24
ro.config.dha_empty_max=24
ro.cfg.dha_empty_init=32
ro.cfg.dha_empty_max=32
ro.config.dha_th_rate=2.0
ro.config.dha_lmk_scale=1.0
ro.config.dha_pwhitelist_enable=1
ro.config.dha_pwhl_key=7938
ro.config.fall_prevent_enable=true
security.mdpp.mass=skmm
ro.hardware.keystore=mdfpp
ro.security.vpnpp.ver=2.1
ro.security.vpnpp.release=1.0
sys.use_fifo_ui=0
persist.sys.tcpOptimizer.on=1
sys.config.amp_perf_enable=true
ro.config.systemaudiodebug=abox&codecdsp
ro.security.vaultkeeper.feature=1
ro.gfx.driver.0=com.samsung.gpudriver.S8MaliG71_80
ro.hardware.egl=mali
ro.zygote.disable_gl_preload=true
ro.com.google.clientidbase=android-samsung
ro.opa.eligible_device=true
ro.control_privapp_permissions=log
ro.setupwizard.wifi_on_exit=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=8.0_r5
ro.build.version.sem=2601
ro.build.version.sep=90000
ro.treble.enabled=false
ro.build.selinux=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=exynos-m2
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
dalvik.vm.isa.arm.features=default
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=3.0
ro.config.iccc_version=3.0
ro.config.dmverity=true
ro.config.rkp=true
ro.config.kap_default_on=true
ro.config.kap=true
ro.kernel.qemu=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0xeaeafdd6573569bb96963e3e34597057321ea845000000000000000000000000
Marioabirached said:
# begin build properties
Click to expand...
Click to collapse
Test V2 and report
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Maybe wiping user data can help?
jeyaayyanar said:
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Click to expand...
Click to collapse
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
After the reset bootloop, I need this flash file for me.
Please could you help?
Alk142 said:
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
Click to expand...
Click to collapse
Please I have the same kind of device but mine is stuck on a guest user account and my notification, Developer options and a lot of stuff doesn't work.
Please I would be so grateful if you could dump your stock ROM for me so I could flash mine. Please bro, i have searched everywhere for the ROM but without success until I stumbled on this thread.
***Beware, not all KT107 are compatible with each others, make a backup first if you can and use at your own risk***
****This is for MT6580 with kernel:3.10.72+ , do not even try if you have different kernel or cpu****
I opened the casing of my tablet, here are the models number written on the mainboard:
directly on the board :
KT961C12_80_216_V3.0
on the sticker:
KT107_1+16_D2_31PIN_20170424
BOM:KT107C12_80_216_V3.0_1G 16G_RDA_GSM
四频_NB1_无按體_NDR_最产BOM_N20180928
*There might be mistakes in the chinese characters*
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
1: Root with KingoRoot
KingoRoot: https://www.kingoapp.com/
2: Install Flashify
Flashify : https://play.google.com/store/apps/d...shify&hl=en_US
3: Download this TWRP build :
TWRP : https://mega.nz/#!27QUFQ5J!nj5WNmD8yMTULrS2lc90bk1qWhRs-xY6b_ou229BgYM
4: Install the TWRP image to recovery with flashify
5: Reboot to recovery ( on my device I hold "vol up" + "pwr" to get to the bootloader menu, then choose recovery)
6: Copy the stock twrp backup to your device and restore
Stock TWRP backup : https://mega.nz/#F!jJ83Fabb!raIOtZSsqyMboVbb_5sDVQ
***You won't be able to use this backup without TWRP installed***
If you need the stock img to try to restore from fastboot I have those too:
system.img:
https://mega.nz/#!qY0RlIBI!lxsxP2Jn7bdQW_0zKQ8eoEcsadj0w7kru_CKqqnM_bc
recovery.img:
https://mega.nz/#!mAEiASpD!lJAMH1OilJ68vSdeGuP_wBWT9roDQfEyokqILFnr_Fg
boot.img:
https://mega.nz/#!zAFQlAiK!RMzjBvFZFjdkqwDdJvk_V63hGBgT7fDKUegFls-YGiA
SP Flash Tools Compatible ROM and scatter file:
https://mega.nz/#!rB8T1KjS!qya-pScSPdAV5cWLfmD-KN1nlxgb0yzo2vVmGATXjRo
Thanks a lot, please could you make the scatter file?
fueg said:
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
Thanks a lot Fueg, you have no idea how much I appreciate your sending these files, though I am yet to Flash them.
Please as I understand, the spflash tool requires the scatter file to be able to flash a ROM. Please could you make a scatter file for the phone too? I could have used fastboot to flash but my bootloader is not unlocked and I don't have access to my developer options to enable me unlock it neither could I install any apps on my phone as it is stuck in guest user mode.
I am just a novice in this stuff but if you have any other ways I could flash the ROM without needing a scatter file please could you tell me please?
Thanks you very again!!!
EDIT: Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.
Click to expand...
Click to collapse
Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.[/QUOTE said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Please so sorry, but the download link for the TWRP build still don't work.
fueg said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Aloydonez said:
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Click to expand...
Click to collapse
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Please help, I just ran into serious trouble
fueg said:
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Click to expand...
Click to collapse
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it...
You can also try this firmware:
https://yadi.sk/d/Gis_kl1y3UjJQC
It's a ROM for another KT107 variant...
Thanks Fueg, this is the information you requested
fueg said:
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it......
Click to expand...
Click to collapse
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
_____________________________________
(Below is what I found on the label on one of the heat sinks on the motherboard.)
TD_KT107_D2_1+16 31PIN-HNHBOE_M1D50-901
BOM:KT107C_A_V1.0_1G+16G_GSM B1_31PIN
MTKL20170818395
_____________________________________
( This below was printed on the PCB)
KT961C-V1.0 2016.07.29
_____________________________________
OS Properties
KERNEL: Linux version 3.10.72+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Nov 9 18:16:15 CST 2016
CODENAME: REL
Mainboard: unknown
Bootloader: unknown
Manufacturer: JTY
BRAND: Padking
Model: Padking
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: KT107
DISPLAY: Padking_V01
FINGERPRINT: alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
Release= 6.0
HARDWARE: mt6580
ID: LMY47I
TAGS: test-keys
Radio= MOLY.WR8.W1449.MD.WG.MP.V23, 2016/03/18 15:22
_________________________________'_'___
(This below is the build properties)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47I
ro.build.display.id=Padking_V01
ro.build.version.incremental=1477364172
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.version.security_patch=2016-01-01
ro.build.version.base_os=
ro.build.date=2016年 10月 25日 星期二 10:57:29 CST
ro.build.date.utc=1477364249
ro.build.type=user
ro.build.user=azhuo
ro.build.host=azhuo-desktop
ro.build.tags=test-keys
ro.build.flavor=full_KT107_NL-user
ro.product.model=Padking
ro.product.brand=Padking
ro.product.name=KT107
ro.product.device=KT107
ro.product.board=
# 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=JTY
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6580
# ro.build.product is obsolete; use ro.product.device
ro.build.product=KT107
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_KT107_NL-user 5.1 LMY47I 1477364172 test-keys
ro.build.fingerprint=alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/vsun/KT107_NL/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
#
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
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=no
# 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
# temporary enables NAV bar (soft keys)
qemu.hw.mainkeys=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=0
#ro.kernel.qemu.gles=0
ro.opengles.version=131072
#ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=210
ro.mtk_default_ime=com.sohu.inputmethod.sogou.SogouIME
persist.sys.timezone=
ro.jty.version.release=Padking_MID-2016
ro.jty.showdev=true
ro.elink.gemini=true
#ro.operator.optr=CUST
ro.build.screen_size_inches=10.1
#lqh add for romtool
ro.romtool.jtynetworkType=2G
ro.romtool.homepage=www.google.com
ro.romtool.front.picturesize=1600x1200
ro.romtool.back.picturesize=2560x1920
ro.jty.data.expandNum=0.5
ro.jty.fat.expandNum=1.5
#ro.romtool.fake_userdata=4.00
#ro.romtool.fake_pcstorage=8.00
ro.romtool.fake_memory=1
ro.romtool.fake_lcd=1280x800
ro.romtool.cpu_platform=MT6580
ro.romtool.cpu_corenumber=4
ro.romtool.cpu_frequency=1500.00
ro.romtool.showAddInfo=false
ro.romtool.fontsize=1.08
ro.romtool.screenbrightness=170
ro.romtool.screenofftimeout=60
ro.romtool.hlimit=true
ro.romtool.fat.name=Padking
#lqh add end
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.mediatek.chip_ver=S01
ro.mediatek.version.release=KT107_L1_20160428
ro.mediatek.platform=MT6580
ro.telephony.sim.count=2
persist.radio.default.sim=0
persist.radio.multisim.config=dsds
persist.md.perm.checked=to_upgrade
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
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
mediatek.wlan.chip=CONSYS_MT6735
mediatek.wlan.module.postfix=_consys_mt6735
ril.radiooff.poweroffMD=0
ro.frp.pst=/dev/block/platform/mtk-msdc.0/by-name/frp
ro.mediatek.version.branch=L1.MP6
ro.mediatek.version.sdk=4
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r2
ro.com.google.clientidbase=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.ms=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.yt=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.am=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.gmm=alps-full_KT107_NL-{country}
ro.mtk_gemini_support=1
ro.mtk_audio_profiles=1
ro.mtk_audenh_support=1
ro.mtk_lossless_bt_audio=1
ro.mtk_besloudness_support=1
ro.mtk_bessurround_support=1
ro.mtk_gemini_enhancement=1
ro.mtk_wapi_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_voice_ui_support=1
ro.mtk_voice_unlock_support=1
ro.mtk_voice_contact_support=1
ro.mtk_wlan_support=1
ro.mtk_gps_support=1
ro.mtk_omacp_support=1
ro.mtk_search_db_support=1
ro.mtk_dialer_search_support=1
ro.mtk_dhcpv6c_wifi=1
ro.have_aacencode_feature=1
ro.mtk_fd_support=1
ro.mtk_oma_drm_support=1
ro.mtk_cta_drm_support=1
ro.mtk_widevine_drm_l3_support=1
ro.mtk_eap_sim_aka=1
ro.mtk_fm_recording_support=1
ro.mtk_audio_ape_support=1
ro.mtk_flv_playback_support=1
ro.mtk_fd_force_rel_support=1
ro.mtk_wmv_playback_support=1
ro.mtk_send_rr_support=1
ro.mtk_rat_wcdma_preferred=1
ro.mtk_tb_call_speaker_on=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.mtk_enable_md1=1
ro.mtk_flight_mode_power_off_md=1
ro.mtk_pq_support=2
ro.mtk_miravision_support=1
ro.mtk_miravision_image_dc=1
ro.mtk_wifi_mcc_support=1
ro.mtk_system_update_support=1
ro.mtk_sim_hot_swap=1
ro.mtk_thumbnail_play_support=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_perfservice_support=1
ro.mtk_cta_set=1
ro.mtk_mobile_management=1
ro.mtk_antibricking_level=2
ro.mtk_cam_mfb_support=0
ro.mtk_cam_mav_support=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_live_photo_support=1
ro.mtk_motion_track_support=1
ro.mtk_privacy_protection_lock=1
ro.mtk_bg_power_saving_support=1
ro.mtk_bg_power_saving_ui=1
ro.have_aee_feature=1
ro.sim_me_lock_mode=0
ro.mtk_dual_mic_support=0
ro.mtk_is_tablet=0
ro.mtk_voice_extension_support=1
wfd.dummy.enable=1
ro.mediatek.project.path=device/vsun/KT107_NL
persist.mtk.wcn.combo.chipid=-1
service.wcn.driver.ready=no
ro.com.android.mobiledata=false
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
persist.sys.dex2oat_white_list=com.isoftdimension.co.id.sixpay:com.instagram.android:
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
Aloydonez said:
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
. . .
. . .
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
maybe this:
https://cloud.mail.ru/public/4XAT/4nnv5t5WY
or this one
https://drive.google.com/file/d/19pCWODtS3BdN-PGRQVXt26taGboBJCsp/view
you can also try those:
http://4pda.ru/forum/index.php?showtopic=803557&st=0#Spoil-58377265-8
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware, I have not been able to find an exact match...
Anyway if you keep trying different firmware chances are that you will eventually find one that is compatible with your device (in my case I had to try about 10 and the one that works was not an exact match but it still works 100%)
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Aloydonez said:
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Best of luck to you, I hope something works!
Click to expand...
Click to collapse
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
The display drivers are indeed contained within the ROM. Apparently your display is not the same then the one I have. If you have a backup of your previous firmware you can look for a tutorial on haw to extract the files you need (inside boot.img and system.img), and another tutorial on how to port ROM for mediatek 6580.
If you don't have a backup you will have to try to find a ROM with the display working to have the drivers you need ..
flashing twrp
hello fueg
thank you for your efforts
well i need to flash twrp file but i could not root my tablet. this give me one option ;to use sp flash tool. my questions to you
1- i review the scatter file you submitted and compare it to the one i see when i connect my device; there are many differences in start address and size; so which one i should use?
2- since iam flashing only the twrp file in recovery.img section; do i need to includes other sections in the scatter file?