Join us on Tl   Wh

Hovatek Forum MOBILE Android [Please help] Touchscreen messed up after wrong firmware

[Please help] Touchscreen messed up after wrong firmware

[Please help] Touchscreen messed up after wrong firmware

onasre
onasre
onasre
Newbie
4
27-02-2019, 12:11 AM
#1



Hello
Well guys , I have Jiayu G6 (mtk6592) , had to flash Stock Rom , but mistakenly downloaded and flashed Jiayu S2 (mtk6592) firmware .
the phone went Dead , then i downloaded and flashed the right Firmware for G6 . now its working fine but the touch screen messed up , when i click on something it will respond somewhere els .. 
Flashed the stock recovery with sp flash tool , i tried all Stock recovery available for this device and same problem , i tried Restore my TWRP Backup but the touch screen problem did not fix ..
I have the whole backup which i made before flashing the S2 firmware ( see image attached ) .. but do not know what to do ?
any idea? 
i do not know if the S2 Kernel burned something on the Mainboard .. i do not know if buying new touch screen will fix it or not
Attached Files
.png
g6.png
Size: 11.73 KB / Downloads: 3
hovatek
hovatek
hovatek
Administrator
49,753
27-02-2019, 10:31 AM
#2
(27-02-2019, 12:11 AM)onasre Hello
Well guys , I have Jiayu G6 (mtk6592) , had to flash Stock Rom , but mistakenly downloaded and flashed Jiayu S2 (mtk6592) firmware .
the phone went Dead , then i downloaded and flashed the right Firmware for G6 . now its working fine but the touch screen messed up , when i click on something it will respond somewhere els .. 
Flashed the stock recovery with sp flash tool , i tried all Stock recovery available for this device and same problem , i tried Restore my TWRP Backup but the touch screen problem did not fix ..
I have the whole backup which i made before flashing the S2 firmware ( see image attached ) .. but do not know what to do ?
any idea? 
i do not know if the S2 Kernel burned something on the Mainboard .. i do not know if buying new touch screen will fix it or not

so it seems there are two different variants for this model, maybe more
try flashing preloader.bin and lk.bin from your backup
was this backup made before OR after you needed to flash stock rom?
why did you need to flash stock rom in the first place?

did you try all the roms @ [ Login to download]   >> ROM > G6 ?
password: j2ug
This post was last modified: 27-02-2019, 10:46 AM by X3non.
onasre
onasre
onasre
Newbie
4
27-02-2019, 01:55 PM
#3
hi
thx for answering me
the backup was made long time before this happens .. the phone wifi was not stable it kept disconnect so i thought reflash the stock firmware to see if it will fix it but mistakenly flashed the S2 Rom ..

i tried to flash preloader.bin and lk.bin from my backup ,but that did not fix it .. still the touch screen not responding well .. i do not know if flashing wrong firmware could Cause hardware fail ..i kinda have feeling it burns something on the IC chip for the touchscreen chip ..just not sure
thank you for the Rom link , but none of the rom Helped .. same thing .. touch not working right ..
hovatek
hovatek
hovatek
Administrator
49,753
27-02-2019, 04:13 PM
#4
(27-02-2019, 01:55 PM)onasre hi
thx for answering me
the backup was made long time before this happens .. the phone wifi was not stable it kept disconnect so i thought reflash the stock firmware to see if it will fix it but mistakenly flashed the S2 Rom ..

i tried to flash preloader.bin and lk.bin from my backup ,but that did not fix it .. still the touch screen not responding well .. i do not know if flashing wrong firmware could Cause  hardware fail ..i kinda have feeling it burns something on the IC chip for the touchscreen chip ..just not sure
thank you for the Rom link , but  none of the rom Helped .. same thing .. touch not working right ..

how about flashing the entire backup you made?
unless your phone fell or something hit the screen then its still software related
unpack system.img from your backup and check build.prop for the build number using method 4 @ https://www.hovatek.com/forum/thread-16005.html
post the build number here
onasre
onasre
onasre
Newbie
4
27-02-2019, 05:28 PM
#5



Thank you 
i have tried to restore all files in the folder "files to flash" it was restored but the touch screen did not work ..i have flashed the stock firmeware with no luck..this is my build.prop  backup file.

Code:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=G6W 20141121-180733
ro.build.version.incremental=eng.scm.1416564310
ro.custom.build.version=1416564310
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Fri Nov 21 18:07:33 CST 2014
ro.build.date.utc=1416564453
ro.build.type=user
ro.build.user=scm
ro.build.host=v81
ro.build.tags=test-keys
ro.product.model=JY-G6
ro.product.brand=JIAYU
ro.product.name=G6
ro.product.device=G6
ro.product.board=S2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=JYT
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=MT92_S2
# ro.build.product is obsolete; use ro.product.device
ro.build.product=S2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=S2-user 4.4.2 KOT49H eng.scm.1416564310 test-keys
ro.build.fingerprint=JIAYU/S2/S2:4.4.2/KOT49H/1416564310:user/test-keys
ro.build.flavor=mt92_s2_g6w_jyt_kk_wcdma_sw_ldata_mul_tphone
ro.build.characteristics=default
# end build properties

# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP1.V2.10
ro.mediatek.platform=MT6592
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK1.MP1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/vanzo92_cwet_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=256m
dalvik.vm.heapsize=512m

# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0

# Power off opt in IPO
sys.ipo.pwrdncap=2

# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage

# USB BICR function
ro.sys.usb.bicr=yes

# USB Charge only function
ro.sys.usb.charging.only=yes

# audio
ro.camera.sound.forced=0
ro.audio.silent=0

ro.zygote.preload.enable=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=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
ro.nfc.port=I2C
mtknfc.status.type=unknow
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MTK_CONNSYS_MT6592
mediatek.wlan.module.postfix=_mtk_connsys_mt6592
ril.radiooff.poweroffMD=0
ro.config.notification_sound=F1_New_MMS.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=MidEvilJaunt.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
persist.sys.display.clearMotion=1
persist.clearMotion.fblevel.nrm=255
persist.clearMotion.fblevel.bdr=255
ro.lte.dc.support=0
ril.active.md=0
ro.init.ipo_setting=false
persist.sys.root_access=0
ro.init.show_bat_percent=1
ro.init.wifi_on=false
ro.init.bluetooth_on=false
persist.sys.timezone=Asia/Shanghai
ro.init.install_non_market_app=true
ro.init.profile_vibration=true
persist.sys.status_bar_alpha=0
persist.sys.lockscreen_alpha=128
persist.sys.launcher_alpha=179
ro.init.ringtone_vol=15
ro.init.notification_vol=15
ro.init.alarm_vol=15
ro.init.music_vol=15
ro.init.fm_vol=15
ro.init.call_vol=7
ro.init.roaming_ind_needed=true
ro.init.gesture_gallery=1
ro.init.gesture_camera=1
ro.init.gesture_music=1
ro.init.gesture_launcher=1
ro.init.gesture_browser=1
ro.init.camera_hide_appguide=true
ro.init.factory_code=5972
ro.init.screen_brightness=255
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hovatek
hovatek
hovatek
Administrator
49,753
28-02-2019, 09:31 AM
#6
(27-02-2019, 05:28 PM)onasre Thank you 
i have tried to restore all files in the folder "files to flash" it was restored but the touch screen did not work ..i have flashed the stock firmeware with no luck..this is my build.prop  backup file.
...
you build number is ifferent from the rest
firmware for G6W 20141121-180733 is @ [ Login to download]  
download and flash everything, if touch still doesn't function after flashing then its now a hardware related problem
EMMANUS
EMMANUS
EMMANUS
Senior Member
1,677
28-02-2019, 10:09 AM
#7
Something else you can try is booting to factory mode and perform a calibration (touchscreen) test. See if all the spots you touch indicate touches.
onasre
onasre
onasre
Newbie
4
28-02-2019, 11:11 PM
#8
thank you ...
done every thing and still no luck ... i believe its hardware fail but i do not know if its on the mainboard or the lcd part
hovatek
hovatek
hovatek
Administrator
49,753
01-03-2019, 10:55 AM
#9
(28-02-2019, 11:11 PM)onasre thank you ...
done every thing and still no luck ... i believe its hardware fail but i do not know if its on the mainboard or the lcd part

take the phone to a phone hardware repair technician for checkup
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt