A friend has an S4 (i9505) from Vodafone Spain (ATL), unlocked and using another operator microSIM (Jazztel). Last week, via OTA, she received the latest update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
After installing that OTA update, the signal level is very low, even none inside buildings, etc. This was not happening before.
In addition, the 2 soft keys (on both sides of the Home button) are not responding anymore, not even lighting up.
The Home button works, so... I think that it's not a hardware problem. Too much coincidence that the update and that hypothetical hardware problem happened at the same time...
First I did was a total hard reset, to factory settings, etc. No success, both problems (signal and soft keys) were still there.
Second, I flashed ROM manually via Odin. I flashed latest PHE one, so no Vodafone bloatware anymore: http://www.sammobile.com/firmwares/download/59311/I9505XXUHOJ2_I9505YXXHOJ1_PHE/
No success, still the same. I then did again a hard reset to factory setting, with Wipes first... and nothing.
Next thing I will do (when i have the phone in my hands again) is flashing with Odin the previous PHE one, and crossing fingers: http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/
Anyone with the same problem? Any solution/suggestion?
Flashed next-to-last Stock ROM for PHE http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/ and no success
Then I flashed Base HOH2 (4files+PIT) with Odin and... nothing either.
No idea what to try next. Suggestions?
Same here, after OTA no menu/back buttons (neither backlight or functionality)
Current status:
- seems to affect quite a lot of people, there are more threads like this on various sites
*e.g. here, here, here
- happenning after both OTA or ODIN based update to latest 5.0.1 ROM (for me it was i9505XXUHOJ2)
My findings so far:
- NO rom change seems to fix this
- it seems that touch keys' FW is updated (physically on the chip) along with the update (to version 0x12)
- Touch key FW update in menu *#2663# not applicable as it says that it won't update - versions are the same (you can check the version of driver used by ROM and the actual FW in chip on this page)
NOTE. my girlfriend has the buttons working after successful update and has both in version 0x12
Conclusion:
- It seems that the FW flashing process of the touch keys controllers somehow failed => phone says that it's also ver. 0x12 (same as android driver) but it is probably corrupted
- Re-flashing of the chip could solve the problems, however there are problems with this:
NOTES.
Menu *#2663# won't let us do the flash because of the version check - Can we use ADB to force the update on a rooted phone? Does anybody know how?
There is a slight chance, that it'll be fixed if Samsung will release some newer update which updates also the keys' FW
Samsung could release a fix, that will flash this manually as a lot of people have problem with this
!EDIT:
I've found very similar problem + solution on the Vietnamese forum bellow (don't use the files as it's for different phone!):
- to sum it up - force downgrading the FW, the update again... (any ROM cook that could help?)
see here
regards,
J.
I completely agree with you. I also tried the *#2663# path, the phone also has 0x12 touch keys FW, and it doesn't let me reflash it, either. Don't know what FW was there before the OTA update.
I have been told about the first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/download/44821/I9505XXUHOB7_I9505OXAHOB7_DBT/ and also about the last 4.4.2 one: http://www.sammobile.com/firmwares/download/40046/I9505XXUGNK4_I9505OXAGNK4_DBT/
Maybe one of those... makes something again on the Touch Keys FW?
I couldn't try anymore bcs I gave the phone back to my friend (with accesibility touch keys on-screen)
HI, have you found a solution? My Italian S4 suffered the same bug after the same upgrade. I tried to contact samsung and they said I need to replace the screen because upgrading the firmware put the electronic under stress and they got broken. I don't believe them because too many people have the same problem + my screen is two days old! Please help me!
Same problem for my S4! how we can flash/reflash/downgrade soft touch fw?
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
oiluj said:
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
Click to expand...
Click to collapse
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
kosmodisk said:
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
Click to expand...
Click to collapse
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
oiluj said:
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
Click to expand...
Click to collapse
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
BUBA0071 said:
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Click to expand...
Click to collapse
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
MoLoCEL said:
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
Click to expand...
Click to collapse
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
wild081 said:
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
Click to expand...
Click to collapse
download it again
@oiluj
HOE3 works for me. Problems start from HOF onwards.
I have also tried flashing HOA7 DBT and upgrading. Problem persists. My touchkey firmware is 0x1a and won't update no matter what Firmware package I tried. Up to now i have tried: GNG2, GNI2, GNK4, HOA7, HOB7, HOD7.
I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
MoLoCEL said:
[MENTION=3170873]I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
Click to expand...
Click to collapse
The phone that that girl gave to me, for fixing... was completely in official status. Always official ROMs, and official OTA updates, from first minute. And the problem was caused by latest official OTA update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
So the problem was not caused by any custom ROM or a not official one.
oiluj said:
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
Click to expand...
Click to collapse
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
BUBA0071 said:
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
Click to expand...
Click to collapse
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
kosmodisk said:
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
Click to expand...
Click to collapse
Wups it have been some time since it was custum, but in any cace it must have been some of the first lollipop roms. I gave to my mom 13 feb 2015 and i did a lot of flashing before that, i think one of the roms i tryed was Project Chaos. but also i tryed all the google editition roms for i9505 and cyanogen.
but when it whent back to stock it i used PDA I9505XXUHOD7 CSC I9505NEEHOD2 NEE firmware
I've got a question. When you flash the HOA7 file from the Mega link, do you use only the AP file, or you use AP,BL,CP, CSC and PIT files?
I'm gonna try to fix my S4 but i'm not sure about the right process I should follow.
Thank you!
Related
Ever since updating to this ROM a strange behavior would occur intermittently. Normally when navigating, BOTH BUTTONS stay lit and function as they are supposed to. When the malfunction occurs only ONE BUTTON stays lit and the other button that is not lit behaves as if it is stuck; the only way to unstick the button is to sleep/wake the phone or hold the Power button and hit Home to escape. It may return to normal for awhile but will return eventually. Any suggestions?
I tried searching for the solution but could not find an answer.
I have already tried:
1. flashing back to stock JPY with ODIN with repartition; result-same intermittent problem
2. Flashing darky rom again: result-same intermittent problem
3. Clearing data and cache from both ROMS: result-same intermittent problem
Sent from my GT-I9000T using XDA App
There is another thread - Touch Screen Keys "Menu & Back Buttons" that sounds similar but it doesn't specify the exact symptoms I'm describing.
I'm beginning to think it's ROM related vs hardware since the problems with problematic touch keys on any thread I find always mention "Darky ROM" describing "when" the problems start occurring.
Sent from my GT-I9000 using XDA App
Darky problem why not ask Darky .
jje
This morning I flashed Darky 8.1-NoWipe. The problem still occurs intermittently, but recovery from problem is not quite as annoying; now I can get the "non-lit" button to get unstuck faster by hitting it a couple of times and pausing in between those times. This behavior further leads me to believe this is more of a firmware prob.
When I use SGS Tools and enter Touchscreen Firmware Version I get the following info:
Phone's TSP FW Version: 22
Part's TSP FW Version: 22
TSP threshhold: 40
Phone's Touch key FW Version: 0xa9
Part's Touch key FW Version: 0x4
Current Firmware:
Model: I9000T
PDA: I9000XXJPY
PHONE: I9000UGJL2 (problem occurs also with Darky stock JPY)
CSC: I9000OXAJPX
This behavior further leads me to believe this is more of a firmware prob.
Ever since updating to this ROM a strange behavior would occur intermittently.
Is that not the answer its the rom one of many many user problems with that rom .
Clean formatted phone with a stock rom .
jje
Hi, just to add
on my phone it reads
Phone's Touch key FW Version: 0xa9
Part's Touch key FW Version: 0xa9
Maybe hitting touch key FW update button will solve the problem
This is a hardware problem
My phone started doing this also...the return button would work sometimes and other times would go off and act as stuck! Firmware version did not help. It would do it on stock 2.2, even 2.2.1 or Darkys.
I have sent it back to Samsung for repair. They know of this issue. Call Samsung or go to your nearest Samsung repair center.
I'm not completely convinced it is a hardware problem.
I can return to a working unit if I re partition and go back to eclair. Also the symptoms improve from darky 8.0 to 8.1. I also pm'd a guy with a similar problem and he went back to eclair and finally to doc rom without the problem re occurring.
I'm not ruling out either but would like to continue to hear about other's experiences.
Did the rep who diagnosed your problem say what part failed exactly?
Sent from my GT-I9000 using XDA App
i made a thread about this like yesterday, but my problem was that my menu button would activate on its own. This is my second sgs from bell, and this one came with JL2 and was having that problem. I flashed seeARMS rom to see if it would go away, and it didnt. So what i did to fix my problem was to go to stock JL2 with odin, used sgstools to update the firmware of the touchkeys, and that worked fine. Reflashed seeARMS and it still works fine. So just go back to JL2, firmware upgrade, flash back to darky's and it hopefully it'll work.
I'm tempted to perform the touch screen firmware upgrade via sgstools but I read a thread where it actually broke one guy's keys and I don't want to worsen the problem.
How many out there have performed the touch screen firmware upgrade successfully? Better yet, how many of you had something go wrong with the touch screen firmware upgrade?
Sent from my GT-I9000 using XDA App
Guys just stick with Official stock rom 2.2.1 JPY.
It's the best firmware up-to-date. I've had my fair share of Custom roms. But I've found that this firmware, JPY is the most stable one yet. Custom roms f*up core apps like camera, email etc which later on won't work with Market apps like
Plus customs roms you have to update like twice a week!!! it gets really annoying...
120 + apps installed and no lag jPY ftw!!
My phone reads:
Phone's Touch key FW version: 0xa9
Part's Touch key FW version: 0xff
Currently on Darkys v8, trasigs kernel
PDA: XXJPY
PHONE: XXJPY
CSC: XAJPX
And mine is working without any problems m8, good luck
It doesnt make sense why firmware would do this to only one of the soft buttons!
If it was a firmware issue both the buttons would have the issue not just one!
On mine it was only the return button....i started having this issue after they replaced the main board due to bad internal SD card. I noticed once the phone warmed up it would do it. If I left it alone for a bit so the screen cooled down, it would be fine. So, heat was causing the issue. It was doing this on the stock firmware the phone came loaded with JL2 and Darkys 8.0.
I'm the one who wrote it broke my buttons when i tried updating. However, I also said that I flashed back to JL2 Bell Official, then updated the fw for the buttons and went back to Darky's and since then, my buttons have worked perfectly. Try that!
Short Version: Flash back to JL2 from Bell, update Phone's Touch key FW version, flash back to Darky. All is well.
//edit: Here's the post explaining how to update the Touch Key Firmware: http://forum.xda-developers.com/showthread.php?t=869492
I ended up flashing to the stock publicly official firmware for my device.
Since I have an I9000t, that meant jl1 firmware.
I then applied the touch key upgrade (that moved me to 0x5) and proceeded to move back to Darky's ROM 8.1. No button problems since.
Sent from my GT-I9000 using XDA App
dinged said:
I ended up flashing to the stock publicly official firmware for my device.
Since I have an I9000T, that meant jl1 firmware.
I then applied the touch key upgrade (that moved me to 0x5) and proceeded to move back to Darky's ROM 8.1. No button problems since.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm having the same issue and the only way to partially solve it is to restart the phone: it would work for a while but after that they would lock again
Phone bricked!!!!
Kewjoe said:
I'm the one who wrote it broke my buttons when i tried updating. However, I also said that I flashed back to JL2 Bell Official, then updated the fw for the buttons and went back to Darky's and since then, my buttons have worked perfectly. Try that!
Short Version: Flash back to JL2 from Bell, update Phone's Touch key FW version, flash back to Darky. All is well.
//edit: Here's the post explaining how to update the Touch Key Firmware: http://forum.xda-developers.com/showthread.php?t=869492
Click to expand...
Click to collapse
Well, I updated my I9000T with that I9000UGJL2 and after Odin ended, the phone stayed there with a black screen, as if it had no power!
I've tried every combination of buttons possible and it won't start up, not even show an error message or something!
What can I do?
Dan_Aykroyd said:
Well, I updated my I9000T with that I9000UGJL2 and after Odin ended, the phone stayed there with a black screen, as if it had no power!
I've tried every combination of buttons possible and it won't start up, not even show an error message or something!
What can I do?
Click to expand...
Click to collapse
Flashing is a whole other topic. Hopefully, you had 3 button recovery mode already working before you tried flashing. If you did, you can try the techniques posted on the forums to get into 3 button recovery mode to reflash such as:
1. Pulling battery. Hold power button.insert battery and try volume down + Home + Power
2. Buy a usb jig on ebay that will put your device in recovery download mode
3. Search for other topics on bricking your phone or getting into 3 button recovery.
Also, to answer your other question. The reason why I upgraded the touchscreen firmware with the stock rom such as jl1 instead of any of the nonofficial newer roms out there was simply because I read some stories where people lost complete touchscreen control if they performed the upgrade with the newer roms.
My philosophy is always to go stock official before performing touchscreen firmware upgrade since there aren't many ways to troubleshoot if something goes wrong.
Sent from my GT-I9000 using XDA App
Dan_Aykroyd said:
Hi
- Is JL1 the latest, official firmware for I9000T? I couldn't find it in SamFirmware.com, where did you get yet?
Click to expand...
Click to collapse
Do a search on xda and you should find a topic and link to official I9000t stock rom.
Sent from my GT-I9000 using XDA App
dinged said:
I'm tempted to perform the touch screen firmware upgrade via sgstools but I read a thread where it actually broke one guy's keys and I don't want to worsen the problem.
How many out there have performed the touch screen firmware upgrade successfully? Better yet, how many of you had something go wrong with the touch screen firmware upgrade?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I've tried this on my wave and SGS the version of the touchscreen firmware didnt change but it did say it was successful
hi, I have an i9505 which I recently restored to stock (I previously had cm12.1). I flashed germany 4.4.2 kitkat and it worked fine.
I did all the updates using OTA, which at the end updates the phone to 5.0.1. Now I have the latest version (XXUHOH2), but I noticed that the back button doesn't work anymore, it doesn't even light up when I press it. The menu button works fine instead. I factory restored the phone through official recovery but it didn't change anything. Is it possible that the back button suddenly stopped working after I updated to the latest version because of an hardware failure, or is it a software problem? The phone hasn't dropped off the table once, and even with the first lollipop update the button worked.
i solved this issue by installing another firmware (XYHOE1)... it seems that my phone doesn't like the german one
Hi. I am having the same issue. I got the OTA update today and 5.0.1 was successfully installed on my phone. However, after the reboot, the back button stopped working and wont even light up. Is there any workaround aside from installing that firmware that you mentioned?
Will surely appreciate your response.
I haven't found a workaround, i tried both normal and black edition OH2 but the issue remains the same... however I flashed a custom firmware (and thus keeping OH2 bootloader and modems) and it works perfectly... so I think it's a bug found in OH2 firmwares which happens in some phones... flashing previous version of any firmware should fix the issue.
mIRChele said:
i solved this issue by installing another firmware (XYHOE1)... it seems that my phone doesn't like the german one
Click to expand...
Click to collapse
Can you give us a link for that firmware? I can't find that firmware anywhere. Thanks!
The latest firmware official for Gt-i9505 Germany (DBT) is this ONE.
mIRChele said:
hi, I have an i9505 which I recently restored to stock (I previously had cm12.1). I flashed germany 4.4.2 kitkat and it worked fine.
I did all the updates using OTA, which at the end updates the phone to 5.0.1. Now I have the latest version (XXUHOH2), but I noticed that the back button doesn't work anymore, it doesn't even light up when I press it. The menu button works fine instead. I factory restored the phone through official recovery but it didn't change anything. Is it possible that the back button suddenly stopped working after I updated to the latest version because of an hardware failure, or is it a software problem? The phone hasn't dropped off the table once, and even with the first lollipop update the button worked.
Click to expand...
Click to collapse
Please help me. I'm experiencing the same issue. I updated my phone to OH2 and after it finished updating, my back and menu button stopped functioning. Then received another update (OJ2) via Kies3, hoping that it will solve the issue I encountered in OH2 but nothing has changed. And now I downgraded my phone to a previous version of Lollipop (OC6) and it still not working.
Before updating my phone, I know and I'm sure my back and menu buttons are working fine that moment and like you, I haven't dropped my phone since I bought it so I'm sure this isn't a hardware problem. :crying::crying: Please help me. A big THANKS! :good:
sharinganxyeah said:
Please help me. I'm experiencing the same issue. I updated my phone to OH2 and after it finished updating, my back and menu button stopped functioning. Then received another update (OJ2) via Kies3, hoping that it will solve the issue I encountered in OH2 but nothing has changed. And now I downgraded my phone to a previous version of Lollipop (OC6) and it still not working.
Before updating my phone, I know and I'm sure my back and menu buttons are working fine that moment and like you, I haven't dropped my phone since I bought it so I'm sure this isn't a hardware problem. :crying::crying: Please help me. A big THANKS! :good:
Click to expand...
Click to collapse
Same problem for me. i tried even a Pit reflesh and dowgrade.
Same thing happened to me. I did the upgrade today, 24th Nov 2015, to Android 5.0.1 - Baseband versionXXUHOJ2 and my menu and back keys are gone. Very infuriating! Will Samsung fix this, or do I have to spend hours of my own time?
I have found a workaround, not ideal but helps short term. Go to Settings > My Device >Accessibility >Dexterity and interaction. Then switch on the Assistant menu. That gives you a little pop up square - available all the time - with 12 buttons including BACK and MENU.
I'm having the same issue. I came back to Kit kat coz I'm tired of Lollipop :silly:
same prb with me...i just updated my s4 to 5.0.1 everything is working fine but the back n menu keys are not working plz give me a solution to this problem
same problem
i back to 4.4.2 stock rom but still not workin -_- help guys
Phone's Touch key FW version: 0x10
Part's Touch key FW version: 0x12
I'v got the same problem.. I update my i9505 and buttons not working.. i flash with other firmware but still not working. plz guys help me
I wrote to Samsung to explain the problem. They know about it. They answered that they will fix the problem in the next update. Relax guys
Joku1981 said:
I wrote to Samsung to explain the problem. They know about it. They answered that they will fix the problem in the next update. Relax guys
Click to expand...
Click to collapse
I'm just a little bit calm, but surely to update we must wait a long time
vanDurka said:
I'm just a little bit calm, but surely to update we must wait a long time
Click to expand...
Click to collapse
I'm not going to move of Android 4.4.2.
very thanks Joku1981 i wait for a update my button still not working
code *#2663#
before flashing and touch button key working :
Phone's Touch key FW version: 0x10
Part's Touch key FW version: 0x10
after flash a update 5.0.1 : touch button key not working.
Phone's Touch key FW version: 0x10
Part's Touch key FW version: 0x12
Joku1981 said:
I wrote to Samsung to explain the problem. They know about it. They answered that they will fix the problem in the next update. Relax guys
Click to expand...
Click to collapse
Joku1981 said:
I'm not going to move of Android 4.4.2.
Click to expand...
Click to collapse
I will try, and waiting for more informations
goodluck
Any updates or solutions as yet please?
I had a perfectly working Galaxy S4 (GT-I9505), then after a recent update was pushed out, the softkeys now do not function. Soooo frustrating...... my confidence in Samsungs' Updates are now dented, I shall seriously think twice about allowing any updates through.
My 3A was running perfect when update A310FXXU2APDC came out. After updating I have sometimes problem with touchscreen. Sometimes i must press something twice or more to get it to work. No matter keyboard or icon or else. Do anyone encountered this problem before? Before touchscreen was super responsive. Will hard reset help?
kabuki8888 said:
My 3A was running perfect when update A310FXXU2APDC came out. After updating I have sometimes problem with touchscreen. Sometimes i must press something twice or more to get it to work. No matter keyboard or icon or else. Do anyone encountered this problem before? Before touchscreen was super responsive. Will hard reset help?
Click to expand...
Click to collapse
Same problem here, screen unsensitive and looks "crazy" often after unlock, looks related to the same software update. Hard reset didn't help for me. Any news for you?
Nope. Hard reset didn't help. No option to downgrade through Odin. I think that we must wait for next firmware update. Probably few months. I will write message to Samsung about this problem. Please do the same so they will know that there's an issue with firmware.
Hey guys, I have an A9 and had the same problem. I could barely navigate through the phone as touchscreen was non- responsive. I resolved the issue by upgrading to newer software release. I now have no problem.
You can downgrade to older version that was working via Odin. Get the required file from sammobile. If you are running 5.1 just make sure that OEM Unlock is allowed {developer option in settings}.
A new software update is out, it is called "A310FXXU2APE1".
I can't flash it until this week-end but I hope it is the good one !
Storka said:
A new software update is out, it is called "A310FXXU2APE1".
I can't flash it until this week-end but I hope it is the good one !
Click to expand...
Click to collapse
Please let us know when you falash this ROM if it helped
*#2663# then update all FIXED i hope you phone the best again hehe keep smile broo
harris210793 said:
*#2663# then update all FIXED i hope you phone the best again hehe keep smile broo
Click to expand...
Click to collapse
Thank you very much, this fixes the touchscreen lag
Thx to harris210793...
Thats work properly on my galaxy a3 2016...
Try *#2663#...and all my touch problem has fixed...
I had this problem for a few days, unresponsive touch, i couldnt write a single word without errors... and also my phone wouldnt recognize codes like *#2663* etc.,
I upgraded to a higher number firmware from sammobile/androidfilehost A3 2016 from A310FXXU3 to A310FXXU4( i found firmware for my country and flashed it with Odin 3.10.) and it fixed the touch and i could also enter codes and manage those subprograms with ease.
My galaxy s4 i9500 had kitkat installed and it was updated to lollipop last year. Thereafter in september while installing ota update phone restarted and suddenly back and menu key were gone blank.
Trued every possible trouble shoot available on xda and other sites to no avail.
1. Installed Stock kitkat again.
2. Installed other lollipop firmwares.
3. Installed cyanogenmod 12.1
4. Wiped phone many times using twrp.
5. Change of strip cable also did not work.
6. *#2663# menu shows blank in place of touch key firmware version/update.
Please if somebody could only figure out what has actually turned the phone like this..even if this is not solvable..at least i should know what went wrong..
Thanks.
There is a similar problem with the GT-I9505 models too.
It's probably related to a faulty update or something.
I don't know if there is anything you can do without professional help.
What you have to do is: you have to force the touch key firmware to update somehow.
GDReaper said:
There is a similar problem with the GT-I9505 models too.
It's probably related to a faulty update or something.
I don't know if there is anything you can do without professional help.
What you have to do is: you have to force the touch key firmware to update somehow.
Click to expand...
Click to collapse
Dear I have been looking for everywhere regarding force install touch key firmware but could not find any solution or patch.
Chupshah said:
Dear I have been looking for everywhere regarding force install touch key firmware but could not find any solution or patch.
Click to expand...
Click to collapse
There was a thread around here that might have some things you could try. I can't find it, but you can do a forum search.
It was for the GT-I9505, but some of it can probably be applied to yours.
Otherwise you might need the help of a professional since they have the necessary tools.
GDReaper said:
There was a thread around here that might have some things you could try. I can't find it, but you can do a forum search.
It was for the GT-I9505, but some of it can probably be applied to yours.
Otherwise you might need the help of a professional since they have the necessary tools.
Click to expand...
Click to collapse
I have gone through that thread it is about incompatible Touch Key and Part Key Firmware Version. I have already tried those fixes but no success. Even in that thread issue is not solved yet.
In my case that dialog box for touch key and parts key firmware update doesnot appear in *#2663#. :crying:
Hi all !
I'm here cause i really need your help and to be honest everything i've found on web so far, is telling totally the opposite things so i'm lost.
Let me explain a ltl, i purchased a Samsung Galaxy S7 Edge Duos/Dual Sim black version (SM-G935FD).
Actually i'm from France ( and i was travelling to Serbia for work, and broke my Note 4 )... The problem is i can't do any update from the phone "Registration Failed" when i click on it.
So after few hours on google, looks like the updates simply doesn't work cause i'm moving France - Serbia ... and the phone seems to be imported from Vietnam.
...
first of all, do you think this update problem is realy linked to this ?
second, i was searching on SAMMOBILE for SM-G935FD to try to put a French Firmware with odin (i don't even know if i can do such a thing without ****ing it up ?)... and on this model all i could find are countries from ASIA.
when i type *#1234# in call i get this :
AP : G935FXXU1BPJG
CP : G935FXXU1BPJG
CSC : G935FOXE1BPH1 (i'm not sure if its a O or a 0 ... the letter or the number :-/)
Model : SM-G935FD
in the Software Infos (in settings) i got this :
Android Version : 6.0.1
BaseBand Version : G935FXXU1BPJG
Kernel Version : 3.18.14-9519568
Version Number : MMB29K.G935FXXU1BPJG
...
please guys i spent a lot of money (in hurry) for this phone, and i'm scared that i got ****ed by the vendor...
if anyone here knows something and can help me... would mean a lot...
Thanks in advance for any kind of help guys.
please guys... if someone got any answer... would mean a lot...
as well if u need any information that can help you answer me feel free to ask...
thanks again.
No need to worry INAX93,
Firmware for 935F will work on 935-FD
Please go to the link below (external link)
http://www.sammobile.com/firmwares/download/115870/G935FXXU1BPLB_G935FOXA1BPL2_XEF/
You can download this firmware and flash it using Odin_3.12.3 in the download mode by pressing volume down+home+power key when ur phone is switched off and selecting the correct files (the firmware package contains 4 files, hence you need to select the correct slot) and you should be good to go with latest firmware for France...
Hope this helps...
max9979 said:
No need to worry INAX93,
Firmware for 935F will work on 935-FD
Please go to the link below (external link)
[not allowed link cause new member]
You can download this firmware and flash it using Odin_3.12.3 in the download mode by pressing volume down+home+power key when ur phone is switched off and selecting the correct files (the firmware package contains 4 files, hence you need to select the correct slot) and you should be good to go with latest firmware for France...
Hope this helps...
Click to expand...
Click to collapse
Thank you a million times! And yes it bhelps a lot!
I feel a lot better just with the hope your reply gave me!
So you are sure that i can go with this french firmware and will not get any trouble right? (cause the thing is that i'm not able to even find on Sammobile the firmware i currently have, and looks like its impossible to save from the device without rooting...)
I see a lot of people getring troubles with some functions not working...
And the last thing do you think the "registration failed" that i get when i click on manual update in the phone settings is linked to my location? (not being in Vietnam?)
Thanks a lot again!
Hello, french too, flashed Orange ROM for g935F on my brand new g935FD, everything OK.
Joyeux Noel
valiran said:
Hello, french too, flashed Orange ROM for g935F on my brand new g935FD, everything OK.
Joyeux Noel
Click to expand...
Click to collapse
Oh salut salut ! Thanks a lot! I guess i'll do try to do it today then! Thanks a lot!
Joyeux Noel a toi et aux tiens !
Merry Christmas to all of you guys! And thanks again for your help and kindness!
I use the ZTO 935F firmware on my 935FD with no problems, works without problems.
Dont worry INAX93 this is a confirmed official download of the French firmware. Dont worry it wont trip knox if done correctly and also your phone will be restored to french firmware without any trouble. I have done similar attempts of flashing official G935F firmware on my G935-FD without any problems am able to update and knox warranty also intact. So go ahead and wish you a merry christmas and a happy new year....
---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------
Registration will also succeed INAX93 so dont you worry...just go ahead and flash the firmware....cheers....
Hi guys !
I just wanted to thank you all one more time ! with your help i did it ! now my phone (SM-G935FD) is with his French XEF firmware !
So thanks a lot to all of you for your help !
Merry Christmas and Happy new year to all of you !
Hi dear experts !
Hope all of you guys are going well, that the new year brought only positive things to you and your family !
I'm back in this thread cause I need your help one more time... everything was well until approx 6 months ago maybe a ltl more... maybe when the 7.0 version went out...
Actually that's when I faced the problem cause i bought a Gear S3 Frontier... I started having troubles with notifications mostly, they were delayed (sometimes for 3-4 hours !)...
While doing a lot of tests in all ways... i found that when i uninstalled all the updates linked to the "Google" app, or disabling it... it solved the problem... Then 6-7 months later i got pissed of cause i wanted to use some of the Google Now features... So i started searching again... after all kind of tests, i finally found that the problem also get solved when my Bluetooth is OFF... When it's set to off i can have the last update for the Google app and everything works fine...
So as i discovered that, i started thinking... maybe the only problem i have actually is a problem with my Bluetooth... as it started 6-7 months ago, 7.0 Version, Gear S3... the point is I started using the Bluetooth before (for my car) and it was always on... but maybe all mixed together... the Google app updates, the 7.0 Version and the Gear S3 king od bluetooth use... is not mixing well... or i don't know...
then i remembered that i flashed my S7 Edge (g935FD) from Vietnam with a firmware from France (g935F)... and maybe i did something incorrect while flashing that led to some Bluetooth troubles that i just discovered... (i had some problems with bluetooth before, like reconnecting randomly to a bluetooth device even if i disconnected it or things like that... )...
So i started searching and find out that there is actually few different way of flashing it, using odin... and i was unable to find a clear explanation of the differencies to be able to understand what i need to do to flash my phone again and in the best conditions.
There is people saying that a bad way of flashing can lead to bluetooth issues (and other things even worse but ok...), so if someone here can explain me, how can i manage to do it the best way... it would mean a lot...
differences between CSC and Home_CSC for example ? then some people are saying "check the re-partition" others say that you must avoid that... how do I know what is the best to do ?
then a lot of them are talking about CSC codes ?
I hope someone will have answers, i want to try to flash it again to try to solve this problem, without bricking it, and also without triggering the knox thing...
thanks in advance for help again...
Ps : the problem i was talking about is :
https://forum.xda-developers.com/s7-edge/help/s7-edge-notification-delay-problems-t3635161
or even :
https://us.community.samsung.com/t5...and-Answers/Delayed-notifications/td-p/114947
no one ? please guys...
still no one to help ?
guys i need just to know if it may solve my problem to flash my phone...
i need to know if i need to check the "re-partition" thing in Odin... somewhere they say "you must check it if you are changing the CSC" and other say "You must avoid checking this unless you have a Pit file" ...
So what is the correct thing to do ?