yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
Problem start when you have already 0x12 when first version was 0x10 from code *#2663# , so with this 0x10 and 0x12, cannot more turn back to 0x10 that's the Fw version of touch working....you now are saying that flashing this CM12.1 you can turn back to 0x12 and 0x1a? mhmmmmmmmm :cool: read any previous post with some user with this configuraction and Softkey Touch button Not working....
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
When I was on HOJ2, I'm sure it said 0x1a on one of the 2 entries, I'm not sure which one (I think the bottom one) and what the other was (I think 0x12).

If those numbers are hexadecimal (which I think they are) it makes sense: 0x1a is installed on the IC, and the firmware comes with 0x12, which is lower than 0x1a and because of that it can't 'upgrade' the firmware because a 'newer' is already installed...

I don't know if any of this is right, it's just a theory. I don't really know that much about it, but it seems logical...
[Galaxy S 4 Q&A, Help & Troubleshooting] sergey9816:
Guuys...

What about all buttons and sensors not working?

Can I erase emmc without using jtag box?

And what do u think, in service center they can do it or they can just offer new motherboard?
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
Isn't problem of New or for Repair via "NAND_RE TP" and "Format+Update fw" the EMMC, this is my Full work, and if was this the issue, had solved from many time, have a couple of EMMC and Programs for Repair in USB only.

If you Erase EMMC w/o having JTAG box you risk that LOST all partition and phone not power on more.

Service Center say you of purchase New Display, ISN'T Motherbord issue but IC TOUCH of Full LCD, clear now? ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] sergey9816:
Hi, thx for reply:)

I was formatting nand many times and install varios fw without getting lucky:(

All my buttons(pwr, vol+-, home, menu, back) and all sensors(gyroscope, light sensor, etc) not working, so its not the display keys fail(also chip label is 0065-that means that they must work, right?)

And im asking about will guys in service center can downgrade my bootloader?

Or its my mistake and i missunderstending you?:)
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
Yes with right IC 0065 will be working....but if you flash this with good Kernel that's not the same in STOCK FW but in softwere Touch key...but read only one previous page is explained all very clear.

If you are good to build one Kernel for Force Touch Update has solved you problem, anyway you have good Chip not Fake are just in good way, if you are lucky can be testing many New STOCK FW, (latest), can be find right one:good:

Real Solution is something where you have a way for Flash Kernel for Touck key and restore Original Key.

So, you Know who can do it?, is easy write "find someone who can modify the kernel code to bypass the touch key FW version" ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] sergey9816:
Didnt know anyone:(

And didnt find right kernel and rom:(

Yhank you for assistance, my friend
[Galaxy S 4 Q&A, Help & Troubleshooting] Qiut:
Here's my quick introduction:

I'm pretty much a novice to all this. So, don't think that I know what I'm talking about ;)

Previously had 4.4.2 I9505XXUGNH6_I9505XSAGNH1 flashed phone for quite a few months. Last week I updated OTA to 5.0.1, on restart my soft keys didn't work. My immediate thought was to downgrade back to my original 4.4.2 firmware. That didn't work. This time I flashed it back to I9505XXUHOJ3-20151216152347 (5.0.1). Still didn't work.

But reading through the thread, I remember that I got my screen replaced a while ago. And reading peoples replies implied that that could well be the problem.

So, my plan now is to replace the new IC that came from ebay with the screen with the old original samsung IC.

I'll try to remember to let you know how I go. But from what I've read, seems like a promising approach.

Thanks again to kosmodisk.

Edit: So, I just remembered that when I replaced the sreen, I moved all the components from one from to another.

Sooooo, the original should actually be in my current phone???

Could someone let me know the exact part that I have to buy?

And maybe link me a youtube tutorial?
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
But my screen is still the original, never replaced, and I also have this problem...

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
Guys, be carefully that Issue will be solved only whit Chip price via HW, not is 100% for all OK, but try for to see what 16 pin, (not 24 pin), of sensor Flat Touch key you have.

Ii's very easy, just remove all back cover and have in fron you eyes this Flat going under the Glass and connected to other that goes in Motherboard, Read if there's writen 0065xxxx , this is the Original IC Chip mounted in Full Original, (not fake ebay, aliexpress itc..), Samsung LCD.

If you see other sigle like 236Axxx, go in Good store also spent few $ more and Purchase New "Sensor Touch Button" and make sure that you see IC Chip of 16 Pin with this sigle: "0065xxxx" , than replace this or send to anybody that work in it, and for me now turn back to working.

Other Test first of Purchase this new sensor is:

From other Broken Diplay but with Original 0065xxx Ic Chip, connect Temporary all this sensoor to other Flat that goe in motherboard then use Sensor w/o mounted touch these manually, (not to be Brute), and if are working, ok cause of you problem, (how all other), solved.

Now can replace and put all in his right position and next time Be carefully when purchase Replacement Part :good:

Who isn't good for do this HW work only for who live near to me can contact me

Regards
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
IMO Samsung should just fix this in their firmwares, at least for the people with stock screens. If other roms or older firmwares don't have this problem, they definitely can. It's just a matter of Samsung willing to fix it...

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
I seem to have solved the problem by flashing an Older boot image from I9505XXUHOC6. After updating to the latest ROM simply flash just the older boot image and your golden. Don't know what the boot image stores that fixes this problem however this doesn't change the Touch keys controller FW, however, the menu and back keys are back to normal. Perhaps this could be a jumping point for someone more technically adept to change the FWs back to 0x12 more 5.1
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
Seem very strange becouse i've flashad many Kernel, (boot.img) from many Old Fw version w/o any result, always Not change Fw ot Touck Key controller.

Only one question: What type of IC Chip have you in you Flat of Touch sensor?

0065 or 023A...???

This isn't Samsung Issue, but BAD hw mounted in some I9500/9505, so Samsung isn't responsable for these problem, any Stock FW can repair one problem that for Samsung is only Hw.
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Not sure of the IC chip model in my phone, can i find out this though an App?
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
No, it's very Easy, just remove back Cover and w/o touch nothing you ncan see one IC chip of 16 pin in the flat connected in touch screen, help with youtube or google if not know how remove back pannel/cover and just loock for this ic chip
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Haven't checked it yet but I flashed CM 13 Marshmallow 6.0 and CM 12.1 and my hardware keys have no problems after. I have never had any repairs done to my S4, working properly now after flashing newer ROMS.
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
This Not tested solution by me is Only for I9505 LTE, but this thread is Also for the I9500 Version Not LTE and whith totally diffrent CPU...so can be somebody can solve installing the cm 12.1 but all other not solve his issue since for first not replace this Ic chip...
[Galaxy S 4 Q&A, Help & Troubleshooting] avro.bd:
will Downgrading to Kitkat solve this issue? Please anybody can tell?

S4 i9505 LTE
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
The problem is exactly the same on my phone. I find it really annoying because I'd like to use it with the stock firmware, but this problem forces me on custom roms. In this case it is NOT a hardware issue, since it works on other roms. The problem appeared when updating the stock rom, so Samsung obviously broke something in the update. I just don't think they're aware of it, since it only affects a limited amount of users...

Some rom could also be the cause. Maybe cm or another rom included a wrong firmware that got somehow flashed on the IC. But even then it's strange that the problem only appeared after an official update...

Does anyone know a way of contacting a Samsung developer? Emailing customer service will probably just end up with a 'We can't help you any further because your warranty expired' answer, but I'll give it a try tomorrow...
[Galaxy S 4 Q&A, Help & Troubleshooting] lauterm:
Downgrading to kitkat fixed it for me on i337 (AT&T S4).
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Yes the hardware keys work on kitkat, testing it now, however, if and when you update to Lollipop 5.01 problem persist.
[Galaxy S 4 Q&A, Help & Troubleshooting] Qiut:
I don't think that'll fix it.

I updated my S4 i9505 OTA, my previous version was 4.4.2.

I noticed the buttons stopped working, so first thing I did was flash it back to 4.4.2.

But that didn't help because it won't downgrade your button FW. (I'm pretty sure.
[Galaxy S 4 Q&A, Help & Troubleshooting] ba4epe:
Ok. I tryed using all files, and it working for me. :good:

Before Flashing:

Phone's Touch key FW version: 0x12

Part's Touch key FW version:0x1a

After Flashing:

Phone's Touch key FW version:0x10

Part's Touch key FW version:0x1a
[Galaxy S 4 Q&A, Help & Troubleshooting] vanito:
It's solution for all and final solution, you are only lucky and for sure you Ic Chip is OEM original 0665 and not Fake one 023A.

Firmware cannot downgrade the Softwere of "Touch Key", sure you are only lucky how other 5% of the users.

I've done all Test with all Fw, (4 part file + Pit), EU zone, (my I9500 was been assembled for EU zone), and was working perfect with any Stock Fw from 4.2.2 to 5.0.1 of all world then one CHN Stock Fw has caused this issue.

Are been obbligate to test also CHN Stock Fw becouse also with professional tool phone was always w/o signal, (Imei Clean, Efs Perfect, NV 100% ok), so when have cecked Ic Chip was one Broken not OEM 023A, replaced this with 0065 Original one and first downgrading to 4.4.2 phones repaired, "Sensor Touch Button" full working...:good:

Issue now is that i not want upgrade more becouse there's risk of Upgrade other time also the softwere of Touch key.

Full Solution is Find one Kernel that Force this softwer Touch key to downgrade if happen other time, but at today no one developer have get out something of this for these model, thre's for Nexus or other but Not for I9505/I9500.

WARNING, cm 12.1 have good success but Only for I9505, bad success with cm 12.1 Nightly for I9500, to many bugs, all tested 100%.

regards;)
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
But wait, does downgrading to kitkat fix the firmware when you have a stock screen? What does your phone say on the *#2663# screen?

Verstuurd vanaf mijn A0001 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] et_pedro:
Hi,

I have also the same problem with the touch button after updating the last OTA and with a replaced screen (3rd Party). I've tried several Stock Roms and also cm13 and Ressurection Remix (cm13 based) but none downgraded the fw. Also, I can't execute the function *#2663# on cm13, can someone help, please?
[Galaxy S 4 Q&A, Help & Troubleshooting] karimartine:
Hi,

After flashing the new stock, strangely enough I got:

Phone's Touch key FW version:0x09

Part's Touch key FW version:0x00

and both keys are not working of course even on Cm11 or CM12

Does this mean my IC is fried?

I too had to change the screen some 4-5 months ago.
[Galaxy S 4 Q&A, Help & Troubleshooting] faisallibra:
Hey guys. I've S4 i9506 LTE-A and I've lost both back/menu touch keys after last OTA update on (22-12-2015)

I've gone through the complete thread and I've tried almost all stock roms available at sammobile.com for i9506 t-mobile Germany and along with it I've also tried CM 12.1 but unfortunately unable to recover menu/back buttons.

Currently I'm stayed on build i9506XXUBNA2 (v4.3) and following test (*#2663#) details of touch keys

Phone's touch key F/W version:0x10

Part's touch key F/W version:0x12

Can anyone please help me how to downgrade part's touch key F/W version to 0x10 as well.
[Galaxy S 4 Q&A, Help & Troubleshooting] avro.bd:
How to contact samsung officials (who releases update)??

Seems only they can solve it ! :confused:
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
Contact Samsung support, explain it well and link some of these threads. I did this, and for once the support assistant didn't treat me like a moron telling me to make sure the phone is powered on. He said he forwarded it to the appropriate people, but also that they hadn't heard a lot about the problem yet, so maybe multiple people reporting it will help...

Verstuurd vanaf mijn A0001 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] Azertyman59:
THX

HI,

I'm a french new member, and i really want to thank you because of a replacement of a broken screen with a "clone" one with a fake 023 chip...and everythings go right upto i've made the update of my galaxy S4 with the last lolipop version, my sensitive keys don't work after reboot. I've tired everything I could find across the web, it's just here that i've found the answer.

I was lucky to find a s4 for spare parts (sim card reader KO) of witch i've took the "original" screen (with and MAGIC the sensitives keys come working back.

Sorry for my english mistakes, i hope this post understandable. :p

Best Regards and VERY GREATS THANKS TO ALL MEMBERS OF THIS WONDERFUL FORUM !! ^^

SeB :laugh:
[Galaxy S 4 Q&A, Help & Troubleshooting] FirasPersian:
Guys hope everyone is doing good

I have changed my screen soft keys and they are working fine now

But when I have it to my friend to change it he flashed a different rom of the stock rom and then changed the touch keys. I wonder if I flash myself the stock rom or downgrade from lollipop would the soft keys stop working again ???
[Galaxy S 4 Q&A, Help & Troubleshooting] :
I've found a temporary fix :

Using an old kernel

With Imperium Kernel 3.1 -> Sensor Touch NOT WORKING

With Imperium Kernel 2.9 ->

Sensor Touch WORKING

I've uploaded the files on my Dropbox, please try and tell me

STEPS :

1. Copy the files on your SD Card

2. Use a custom recovery (TWRP/CWM) to flash

2.1 The Kernel Cleaning Script - Universal_Kernel_Cleaning_6.6_by_BluMak_TEAM.zip

2.2 The Imperium 2.9 Kernel - Imperium_LL_Kernel_v2.9.zip

3. Reboot

4. Enjoy

https://dl.dropboxusercontent.com/u/20756252/LL%20Kernel%20XDA/Universal_Kernel_Cleaning_6.6_by_BluMak_TEAM.zip

https://dl.dropboxusercontent.com/u/20756252/LL%20Kernel%20XDA/Imperium_LL_Kernel_v2.9.zip

Hope this will help
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Problem Solved

Just had to send a quick note to say i have managed to fix this problem. The way this can be fixed can only be done through Kies!! So flash an older system ROM and make sure everything reads Official, then run Kies so it can suggest an update., accept the update and it should start downloading the updates then update and reset your phone. I did this last night and true enough my menu buttons and back keys work with the latest stock version. However, when I checked my FW keys version it reads:

Phone's Touch key FW version: 0x12

Parts touch key FW version: 0x1c

See attachments.

My conclusion therefore with regards to this problem is that the problem has no connection to the FW version, but rather there is some information lost by Odin when flashing the latest ROM and only Kies can fix it. I hope this helps someone else as this problem really makes it so much more difficult to use your phone.

If this solution has helped you in some way please send me a thanks, I would appreciate it and would help me to know if anyone was helped by this solution.
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
So, was your screen the original? And you're saying it didn't previously work on that particular build, but after flashing with kies it does? I might try this tonight

Verstuurd vanaf mijn A0001 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
Ok I tried it and it didn't work for me, installed OE2 and update to OJ2 from there via Kies. Mine says 1a instead of 1c though... So were you using an original screen?
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Yup original screen, are your keys working with any other ROM?
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
Well, they work on OE2, cm12.1, cm13... But not on OJ2, even after flashing with Kies...

Verstuurd vanaf mijn A0001 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Regarding the 0x1c, I did have 0x1a as well a few days ago, it seems to increment every time I flash a cm13 ROM.
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
So it might work if I flash cm13 first, and then try kies flashing again... I'll give it a try tomorrow

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] fastzz:
whats the outcome? any fedback from tried cm13?
[Galaxy S 4 Q&A, Help & Troubleshooting] et_pedro:
Hi,

I have cm13 flashed and it still doesn't work but I didn't tried the process you're describing.

One thing I can't do is the *#2663# code. Is it a problem from the cm13 rom?

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
NO the *#2663# code only works on Samsung builds, at least as far as I know coz It doesn't work for me either with any version of CM
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
It didn't change anything... The IC version was still the same (1a) so I didn't even bother trying to update again.

So what cm13 rom did you flash exactly? Tried the latest nightly and flashed stock afterwards, but it was still the same.

But since the exact problem seems to vary a bit from phone to phone I'd like to be sure yours was the same as mine: The buttons work on older stock 5.0.1 firmwares (like OE1), and on cm roms (cm12.1, 13,..) but they DON'T work on newer stock firmwares like OJ2.

Was this your exact problem, that you were able to fix? And could you also tell from which firmware you updated with Kies, or describe the steps you did a bit more in detail?

If everyone with this problem could send it to Samsung support, they'll maybe fix it. I did it and he said he forwarded it, but I think they need some pushing...
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Yes that was my exact problem, sometime in December I installed the ROM below and for some reason or another I wasn't happy and decided to try and get back to stock, that's when I noticed the menu and back keys wouldn't work. This is when I first noticed the FW key was at 0x1a, but the rom was at 0x12. I followed pretty much all the advice I read in these forums regarding this to no avail.

There was a recommendation to flash the German build separately with it's pit file I9505XXUHOA7_OXAHOA7, which I did including the update to the bootloader and repartition options via Odin, tested this by flashing the latest ROM and it was still broken, so I decided to flash back an older Lollipop build for my phone, including bootloader on ODIN then updated this via Kies and it worked. I have surmised from the test i have conducted that this specific problem we encounter emanates from the bootloader.

The increment to 0x1c from 0x1a was most likely caused by this build http://xdaforums.com/galaxy-s4/i9505-develop/rom-crdroid-t3017844 , I'm pretty sure that's what triggered it, if not then it maybe some ROMS for the S6/Note 5 which in this case, I tried most of them currently available here. From last official ROM I decided to test the Note 5 / S6 ROM again and noticed this morning the FW reading were both on 0x1c so indeed it may have been this ROM that did it. http://xdaforums.com/galaxy-s4/i9505-develop/rom-albe95-s6-port-1-0-t3092479
[Galaxy S 4 Q&A, Help & Troubleshooting] dafonehacker:
OK so you flashed an older ROM via Odin with repartitioning and bootloader upgrade enabled? And after that updated via kies?

Verstuurd vanaf mijn A0001 met Tapatalk
[Galaxy S 4 Q&A, Help & Troubleshooting] andonsky:
Nope not quite, the ROM with the split up boot files is a German build since I had to try the suggested post this was the only ROM I had access to with the 4 files plus the pit. http://xdaforums.com/showpost.php?p=63904669&postcount=7 . I had tried this fix before but I did'nt reset the partitions or write the boot sector either, so this time I tried hoping this would be the fix. So to test this theory I then flashed via Odin the latest official ROM and the FW keys was still dead. So to fix this problem I flashed with Odin an official OC6 build which incidentally makes the keys work again, this version of lollipop has no problems with the keys. After completing this flash I then decided to go for broke and try the upgrade via Kies and that finally solved my problem. This route has saved my ass twice now as I remember having this problem when lollipop first came out but the I9505 did not have that build yet, so I decided to flash a ROM with that version. Got into the same mess as I was and I remember distinctly that I used Kies to fix my problem back then, that's why I tried it again when it broke. Now it's all good, and in fact, as I mentioned, I was trying out an S6 build again which bumped keys to 0x1c and decided to just re-flash via TWRP my backed up HOJ2 Rom and though the keys are back to 0x12 and hardware still at 0x1c I have no problems using the menu and back key with the latest lollipop ROM now.

One of the fixes I once mentioned on one of my post, was to flash the latest ROM but use just a bootloader of a lollipop ROM you know that works with your keys. This should then allow you to use the latest rom with your keys, however, this isn't the best solution as it brings in other problems in the long run. Our objective here would simply be to check if the problem your having is the same as mine. In my case once I flashed the older bootloader of the HOC6 ROM, I noticed that the keys we're working and my theory that this problem happens during boot time evolved into finding a more predictable solution.
[Galaxy S 4 Q&A, Help & Troubleshooting] Hvakhshathra:
Pls my i9500 after uptade soft keys not working? What should I do
[Galaxy S 4 Q&A, Help & Troubleshooting] thelittlecrow@hotmail.it:
Don't go mad. Probably your screen is not a original one. You have 2 choices: change the whole screen or find someone able to change just soft keys.
[Galaxy S 4 Q&A, Help & Troubleshooting] Hvakhshathra:
But after update this happened?
[Galaxy S 4 Q&A, Help & Troubleshooting] thelittlecrow@hotmail.it:
Have a look at previous messages. You'll understand everything.
[Galaxy S 4 Q&A, Help & Troubleshooting] Hvakhshathra:
My opinion problem is Firmware
[Galaxy S 4 Q&A, Help & Troubleshooting] thelittlecrow@hotmail.it:
My opinion? I've tried many screens with the same firmware on the same motherboard. Result? the only one that doesn't work is the fake one!
[Galaxy S 4 Q&A, Help & Troubleshooting] Hvakhshathra:
Screen is working soft key not working