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
Is there a zte v9 thread?
Wish there was, it's a real pain searching to find any comments or updates on this model...
Ive experimented with 2.1 roms but nothing than rooting and customising a few roms which ive debranded and unlocked but froyo would be nice
Sent from my V9 using XDA App
Yes there is a thread about the ZTE Light V9
http :// forum .
xda-developers.com/showthread.php?t=883105&page=18
bootanimation
Does anyone know where the bootanimation is on the optus mytab / zte v9?
ZTE V9
How can I rooted my V9 quickly and safe?
serfistas1 said:
How can I rooted my V9 quickly and safe?
Click to expand...
Click to collapse
What type of V9?
Hungarian telenor one not perm rooted yet, I am working on it.
Others works with universal androot 1.6.2 beta 5
hi all...
i have problem...
i try to update from v2.1 to v2.2 but it goes wrong and now zte cant open... it stucks in screen with green icon of android with letter ANDROID... for all the time... i havent recovery... what can i do ? when i press power and volume down it goes me in ftm mode
hi
this is my first android phone, and i've tried to install APP2SD, but the phone goes into loop boot (vodafone logo repeated)
if i press volume up and power, it will not stop on the android screen, it will continue to vodafone logo.
when i connect to the phone tp PC and use the CMD from windows, and type ADP SHELL.... it will give either device offline or the device not found.
if i press the volume down and power, it will go to white screen written on it FTM, and also the device not found.
please any ideas????
My zte v9 is working with a own Froyo 2.2
Kernel 2.6.32.9-perf
[email protected]
Build number
V9_GENERICV.1.0.0B03
Optus My Tab 2.2 offical Update is here!!!! downloading now... only for pre-paid version .. i'll see if it screws my unit up as it a beeline custom rom 2.1 :O
http://www.zte.com.au/optus/V9.htm
bigthermalboy said:
Optus My Tab 2.2 offical Update is here!!!! downloading now... only for pre-paid version .. i'll see if it screws my unit up as it a beeline custom rom 2.1 :O
--URL EDITED OUT, I'm under 8 posts lolz--
Click to expand...
Click to collapse
Reflash using a Stock Rom first. They have set it so that it checks the device for exact match to the Optus Pre-Paid firmware before allowing it to continue.
Once someone does get the official Optus update installed I would much appreciate a complete ROM dump (Including the splash and oem images) so that I can restore my device onto the Optus ROM (and then modify it striping out the crap that is).
I currently have the leaked Android 2.2 on my V9, however this has a few quirks and I would like to experiment between the two versions to determine which is more stable and usable.
I bought my V9 in Taiwan which is called TWM_P2.
It works on v2.3.4(building number: GB_TWM_V9CV1.0.0B04) and I just found the way to root.
It's quiet easy only by one step.
download "super one click" which is a program for PC(not for your android).
Link your V9 to the computer and run the program.
Here is the tip, don't use v 2.0 or up, it will cause system error on you V9 and keep V9 rebooting.
It works on my V9 but I am not sure also works on AU.
I found the way on a Taiwanese forum-- "Mobile01".
I've installed the Cyanogen 7.1.0-V9, stable version, on my ZTE V9c, and now I'm having issues when i try to play some videos.
With .mp4 files, the audio becomes delayed.. also, it doesn't play rmvb even on realplayer.
A friend has one v9c too, but with the original rom in it, and he said that it play everything pretty well.
I've installed mobo player and the codec they asked for, but I still get this problem.
Any clues on how to solve it?
Thanks
I too rooted mah device n bt wifi frnt camera n sensor nt wrking! !!!!
Sent from my V9 using xda app-developers app
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.
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!
Hello !
I have some troubles with the update system of my phone (L31C432B161).
I flashed a custom rom when I was in android 7.0 and I wanted to come back in rom stock. I did a wrong thing and now, I'm locked in B161.
If I try to update it, the version shows beta test key or something like that and my phone has a lot of bugs.
I need help please ! :/
If you have the warranty, go to the official HUAWEI service and tell them that you never received any sort of update (of course lie.). If it works, they will update your phone
Resolved ! They changed my phone.
BreezX said:
Resolved ! They changed my phone.
Click to expand...
Click to collapse
Told ya
Huawei will always fix phones when it comes to faulty updates/non-updatable phones.