Database Users

Mystery solved - rooting CAN mess up your touchscreen (indirectly)

A few days ago, an associate of mine came to me and said his touchscreen worked great out of the box, but then he rooted and the touchscreen became very erratic.
I said no way, you must have played with some JSS15J custom ROM or did the OTA upgrade. He said absolutely not and showed me his version was still JWR66N.
I was still a bit skeptical thinking maybe he had the unit connected to the usb cable when he tested before or was holding the tablet in his hands.
After more "research" (I'm understating how involved this was) I found out he was actually right. *Indirectly*, rooting did mess up his touchscreen.
It wasn't root or SuperSU that did the damage. It was that the process to install root involved running TWRP 2.6.0.0 (which he didn't even flash onto the recovery partition, choosing instead to boot directly into memory)
I don't know if any of you noticed the first time you ran TWRP, but there is some long 15-20 second pause before it comes up the first time, but on subsequent starts, it comes up right away.
I found out what is happening during that pause is your touchscreen firmware is being upgrade to JSS15J levels. It isn't TWRP doing the upgrade. It is because TWRP bundles in the JSS15J kernel which then does the upgrade underneath the hoods.
As an aside, if you run the latest (as in released today) TWRP 2.6.1.0, you will get upgraded to JSS15Q level multi-touch firmware.
This also explains a LOT of confusion with people saying they were on JWR66N and still have lots of multi-touch issues with others saying JWR66N was perfect and there were no issues.
It is quite possible, for the people having issues on JWR66N, while they thought they were on JWR66N because they never ran any ROM nor did the OTA, they might have just run TWRP (or possibly CWM, I haven't checked) and from the standpoint of the touchscreen they were placed at JSS15J levels even if their ROM was JWR66N.
Now, I am not blaming TWRP or saying it is broken. The issue is with the touchscreen firmware from the manufacturer. It just so happens in this case, TWRP is the messenger. So don't shoot the messenger (which includes me)

OK so my touchscreen has a deadzone in it, it has a long thin line from the top to bottom on the right side, i have prepared for a replacement, should i unlock the bootloader and try it again with new twrp? it is on the latest firmware.

pashinator said:
OK so my touchscreen has a deadzone in it, it has a long thin line from the top to bottom on the right side, i have prepared for a replacement, should i unlock the bootloader and try it again with new twrp? it is on the latest firmware.
Click to expand...
Click to collapse
I suggest you try this post
Take that multi-touch! Fix and lock in what works for YOU regardless of updates

sfhub said:
I suggest you try this post
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
BIG Thanks to you for resolving the mistery. Just flashing latest TWRP version 2.6.1.0 improved the touchscreen response dramatically for me.
Now the question is in case Google comes with with new firmware for Touchscreen, how do we make it in sync with TWRP? Is it not TWRP will always override the Touchscreen firmware bundled with it (right now JSS15Q level multi-touch firmware) even if we flash new Google official firmware?

anantk1965 said:
BIG Thanks to you for resolving the mistery. Just flashing latest TWRP version 2.6.1.0 improved the touchscreen response dramatically for me.
Now the question is in case Google comes with with new firmware for Touchscreen, how do we make it in sync with TWRP? Is it not TWRP will always override the Touchscreen firmware bundled with it (right now JSS15Q level multi-touch firmware) even if we flash new Google official firmware?
Click to expand...
Click to collapse
Won't be an issue (at least not in the way you think), according to Google/Asus, newest your tablet has ever encountered always wins.

Flashed 2.1.1 but still some problems.
How can i check if i have the right (newest) touchscreen-firmware?
Thanx in A.

MasterElwood said:
Flashed 2.1.1 but still some problems.
How can i check if i have the right (newest) touchscreen-firmware?
Click to expand...
Click to collapse
reboot phone
adb shell
su -c "dmesg | grep 0x3029"
A042 is newest (JSS15Q/JLS36C) but isn't necessarily the "right" touchscreen firmware for your tablet.

sfhub said:
reboot phone
adb shell
su -c "dmesg | grep 0x3029"
A042 is newest (JSS15Q/JLS36C) but isn't necessarily the "right" touchscreen firmware for your tablet.
Click to expand...
Click to collapse
Something like this???
[ 1.866058] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029
[ 1.868560] [ektf3k]:The firmware was version 0xA042 and id:0x3029
And what is the 2.1.1 you guys talking about?

I don't know what 2.1.1 he was talking about. I figured it was a typo and he meant 6.1.0.0 twrp.
Your kernel has the A042 firmware so it is from JSS15Q or JLS36C. This is just a comment on the kernel. You might be running a different version of the ROM.

sfhub said:
I don't know what 2.1.1 he was talking about. I figured it was a typo and he meant 6.1.0.0 twrp.
Your kernel has the A042 firmware so it is from JSS15Q or JLS36C. This is just a comment on the kernel. You might be running a different version of the ROM.
Click to expand...
Click to collapse
Just this past weekend I loaded twrp 2.6.1.0 and I flash every official CM10.2 nightly that shows up (from get.cm); so currently running the cm-10.2-20130905-NIGHTLY-flo nightly. So between them I must have landed A042 somehow.

2.6.1.1 is my new TWRP version.
Sorry - forgot the 6

MasterElwood said:
2.6.1.1 is my new TWRP version.
Sorry - forgot the 6
Click to expand...
Click to collapse
Just noticed on the twrp page, the latest recovery binary is 2.6.1.0 but if you install that and boot to recovery, it actually says 2.6.1.1.

anantk1965 said:
BIG Thanks to you for resolving the mistery. Just flashing latest TWRP version 2.6.1.0 improved the touchscreen response dramatically for me.
Now the question is in case Google comes with with new firmware for Touchscreen, how do we make it in sync with TWRP? Is it not TWRP will always override the Touchscreen firmware bundled with it (right now JSS15Q level multi-touch firmware) even if we flash new Google official firmware?
Click to expand...
Click to collapse
For a newbie who rooted his phone using WugFresh and now is having touch screen problems (keyboard gets stuck on a key; is that the same problem?) how do I :
1. Find out what version of TWRP I have?
2. "Flash" latest TWRP version? (newbie instructions please)
3. If the problem is with the multi-touch firmware and TWRP is just the messenger, how would a TWRP update fix the firmware?
Thank you for your time and help.

I suggest you just look at this thread.
http://forum.xda-developers.com/showthread.php?t=2428133
You'll be better off than trying to follow your current plan of attack.

Anderson2 said:
For a newbie who rooted his phone using WugFresh and now is having touch screen problems (keyboard gets stuck on a key; is that the same problem?) how do I :
1. Find out what version of TWRP I have?
2. "Flash" latest TWRP version? (newbie instructions please)
3. If the problem is with the multi-touch firmware and TWRP is just the messenger, how would a TWRP update fix the firmware?
Thank you for your time and help.
Click to expand...
Click to collapse
1.Boot in recovery, you will see the version 2.6.0.0
2.Check ..\WugFresh\Development\data\Recovery_Custom\TWRP what file you have in,most likely is the old one, named openrecovery-twrp-2.6.0.0-flo.img)at least it was yesterday with Wug up to date, it may change soon.If this is the case, go to 3, if you already have a newer version go to 4.
3.Download from TWRP site the latest one (openrecovery-twrp-2.6.1.0-flo.img in fact is 2.6.1.1 after flashing) and copy it in ..\WugFresh\Development\data\Recovery_Custom\TWRP folder (and delete the old one you have already there).
4.In WugFresh just do again "Root and flash recovery "(check the box). You will get the new recovery installed (just did that).Boot in recovery and check the version to be sure.

If I update TWRP with GooManager, does that also update to JSS15Q-level touchscreen firmware?

jjmai said:
if i update twrp with goomanager, does that also update to jss15q-level touchscreen firmware?
Click to expand...
Click to collapse
2.6.0.0 -> jss15j
2.6.1.0 (2.6.1.1) -> jss15q
Once the version goes up, it doesn't come back down.

Does that means I just need to flash JSS15Q kernel after flashing recovery and it will be solved?

macaumen said:
Does that means I just need to flash JSS15Q kernel after flashing recovery and it will be solved?
Click to expand...
Click to collapse
That will get you the JSS15Q touchscreen software.
Whether it "solves" your issue, makes it worse, or has no effect will depend on which touchscreen variant you have.
If you find it makes things worse, you will not be able to just restore the JSS15J kernel to go back (nor use TWRP 2.6.0.0). You can flash them and they will boot fine, just your touchscreen software will not go back.
You will need to see this post for a solution:
http://forum.xda-developers.com/showthread.php?t=2428133

sfhub said:
That will get you the JSS15Q touchscreen software.
Whether it "solves" your issue, makes it worse, or has no effect will depend on which touchscreen variant you have.
If you find it makes things worse, you will not be able to just restore the JSS15J kernel to go back (nor use TWRP 2.6.0.0). You can flash them and they will boot fine, just your touchscreen software will not go back.
You will need to see this post for a solution:
http://forum.xda-developers.com/showthread.php?t=2428133
Click to expand...
Click to collapse
Do you mean that once the touch software is updated, it will not be able to downgrade by flashing previous kernel (or TWRP)?
I updated to JSS15Q at the very beginning. Followings are my steps:
1. Grabbed factory image and restore to JSS15Q completely
2. Flash TWRP 2.6.0.0 (2.6.1.x is not available at that time)
3. Root
4. Flash back to stock recovery
5. Flash JSS15Q kernel
If I understand correctly, I am on JSS15Q touch software, right?

using encryption on s5 with cyogenmod12.1 seems to break phone

Hello I have a GM9000p (sprint s5 galaxy) that I rooted using superSU flashing via oden. I also installed cyogenmod recovery (latest stable release of of the wiki). Then i flashed the cm-12.1-20151007-SNAPSHOT-YOG4PAO334-kltespr.zip this appears to be the latest non-nightly build. Everything works fine on the phone except for the fact that when I encrypt it and try to reboot it, it gets stuck in a bootloop. help??

goldanthro said:
Hello I have a GM9000p (sprint s5 galaxy) that I rooted using superSU flashing via oden. I also installed cyogenmod recovery (latest stable release of of the wiki). Then i flashed the cm-12.1-20151007-SNAPSHOT-YOG4PAO334-kltespr.zip this appears to be the latest non-nightly build. Everything works fine on the phone except for the fact that when I encrypt it and try to reboot it, it gets stuck in a bootloop. help??
Click to expand...
Click to collapse
edit: I have found out that TWRP recovery may be able to help. how would i go about using it to "change block size" to give more space for header/footer? please help

S4 i9506 Soft Brick

Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?

zdfan said:
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
Click to expand...
Click to collapse
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?

GDReaper said:
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
Click to expand...
Click to collapse
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.

zdfan said:
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
Click to expand...
Click to collapse
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.

GDReaper said:
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
Click to expand...
Click to collapse
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?

zdfan said:
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
Click to expand...
Click to collapse
I'm a GT-I9505 user, can't really recommend you anything.
There's AICP, various CM13 builds and others. Just look through the GT-I9506 section (here on the forum) until you find something promising.

[Help] Rooting failed on latest build (14-8)

Hi there,
I am trying to root the latest firmware 7.0_NPJS25.93-14-8 with Magisk 13-3(which is latest till date). But after flashing the zip with the help of TWRP and wiping cache + Dalvik cache, the phone is not booting up. Black screen appears(Phone is not bricked, thank god). The LED keeps blinking(if connected with USB). I have go to bootloader and reinstall the whole firmware again.
What should be the issue? Please help.!

keyur1131 said:
Hi there,
I am trying to root the latest firmware 7.0_NPJS25.93-14-8 with Magisk 13-3(which is latest till date). But after flashing the zip with the help of TWRP and wiping cache + Dalvik cache, the phone is not booting up. Black screen appears(Phone is not bricked, thank god). The LED keeps blinking(if connected with USB). I have go to bootloader and reinstall the whole firmware again.
What should be the issue? Please help.!
Click to expand...
Click to collapse
Please describe which method you're following. Maybe this one https://forum.xda-developers.com/mo...ot-nougat-moto-g4-plus-t3484672/post69234580?
Also make sure you follow all the steps.

keyur1131 said:
Hi there,
I am trying to root the latest firmware 7.0_NPJS25.93-14-8 with Magisk 13-3(which is latest till date).
Click to expand...
Click to collapse
You need a custom kernel when trying to root! Rooting the stock kernel atm is not possible. You could try to flash a custom kernel (for example ElementalX or Vegito) made for stock roms and root again.

Thanks guys. Custom kernel helps.

Trouble flashing roms sm t350

Hello all, maybe you can help...
After finally getting a stable TWRP from @ashyx that finally booted, I attempted to flash roms and Gapps on my SM-T350. This should be simple enough, but every rom I flash either doesn't boot or boots with only sound and no display!!!!
Yes, I'm running TWRP 3.2.3-1 courtesy of @ashyx
Yes, I've wiped several times.... wiped internal storage sometimes too
I'm running the latest official 7.1.1 release from Samsung.... I cannot get anything else to boot!
Please offer some support, I need some help y'all!
-------------------------------------------
EDIT: THIS ISSUE HAS BEEN SOLVED
Check the latest comments for more info

I'm having the exact same issues, never experienced this before with any device. Hope someone can help or we can find a fix.

Same - SM-T350
I was able to install Jazzrom but none of the other SM-T350 roms. I can hear sound when I press the power button, but no display when trying Lineage 15 or 16. Jazzrom runs slow, that is why I'm not sticking with it. I have tried several versions of TWRP as well. 3.2.3-1 seems to be the only one that got Jazzrom installed. Thanks in advance for your time. Same issue with crDroid rom ver 5.2

my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device

elginsk8r said:
my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device
Click to expand...
Click to collapse
Tried that.... no luck. Everyone else who reported a problem is having the same exact issue as me.... it's strange.

Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.

heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
Hmm..... I will check this out. Thanks for the lead! I will let u know what happens

heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
This solved it!!! Finally!!! For clarification, anyone who is having this issue must downgrade to stock Marshamallow (BPK1) and flash twrp 3.2.1. It must have something to do with the newer oreo bootloader, so just downgrade and Viola! Success! :good: