Related
Hi all,
I have a GT-I9000M from bell and I just recently upgrading to froyo(jk4) through kies. My phone has never been rooted/lag-fixed, unlocked and flashed before. After upgrading to froyo I have a problem with the back button being "stuck".
This does not happen all the time but occasionally at random it does and is very annoying since I am used to pressing the back button instead of the home button.
Here are the symptoms:
When I press the back button, it would appear to be stuck. The light for the back button is off(and i can't press it anymore), menu key is still light up. I can't press the menu key, I can press the home button but that just takes a screenshot because of the back key still stuck. Another thing is when I press the power button ONCE, the screen closes and then immediately turns back on.
The only way to make it "unstuck" is to press the power button since it "shuts" off the touch buttons. Even then when once I press the back button again it will get stuck. The back button will start working properly after some time randomly. I cannot relate this problem to any specific applications or actions I do. It seems to happen randomly.
I've done a factory reset before I upgraded. Did an additional two factory resets after the upgrade because of this problem and formatted my sd but the problem still persists.
What can I do to fix this problem if can be?
Thanks
EDIT: Thanks to BlackDino for the solution!
BlackDino said:
Ok, goto your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
Let me know if this fixes the issue for you too,
I had the same issue and after doing this I haven't seen the problem in a number of days.
This may or may not work, I have found this menu on my own and don't know if it will solve anything
Click to expand...
Click to collapse
EDIT2: Thanks to Kewjoe to pointing out if you're not on a i9000m rom!
Kewjoe said:
Had to flash JL2 back, redo this and get the proper firmware for the i9000m. My buttons are back
So to be clear, do not run this command from a non-i9000m ROM or you will lose your buttons!
Click to expand...
Click to collapse
Well since I couldn't find any solution, I flashed back to stock jh2 but the problem still persists... I updated through kies again to jk4 but same thing. This is really annoying now. Any ideas? =/
Ok, goto your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
Let me know if this fixes the issue for you too,
I had the same issue and after doing this I haven't seen the problem in a number of days.
This may or may not work, I have found this menu on my own and don't know if it will solve anything
I'll let you know if it fixes it!
Thank you!
BlackDino said:
Ok, goto your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
Let me know if this fixes the issue for you too,
I had the same issue and after doing this I haven't seen the problem in a number of days.
This may or may not work, I have found this menu on my own and don't know if it will solve anything
Click to expand...
Click to collapse
I am having the same problem. Never had this problem at all with 2.1. I am also going to try your suggestion and report back.
Thank you,
So far so good. Usually by now the problem would come back. So I can confirm it works for now! Also, the touch keys seem to be a lot more responsive than before.
Thanks BlackDino!
The problem seems fixed for me too.
Thank you.
Glad this fixes the issues for everyone!
Had the exact same problem and this fixes the problem for me too. Thanks!
This actually "Broke" my back and menu buttons. I'm on Darkyy's 7.5 Rom with Speedmod Kernal K12F 512hz (JL2 Modem). I assume it probably tried to download a FW for an international i9000 and it wasn't compatible with my i9000m hardware. *shrug*.
Trying a factory reset to see if i can get my buttons back.
Had to flash JL2 back, redo this and get the proper firmware for the i9000m. My buttons are back
So to be clear, do not run this command from a non-i9000m ROM or you will lose your buttons!
This happened to me out of the blue on JL2. Luckily, it looks like the fix worked for now. Any word of this problem coming back for those who have applied the FW update? Normally i'd apply the fix and forget about it but this device is so janky...
Kewjoe said:
This actually "Broke" my back and menu buttons. I'm on Darkyy's 7.5 Rom with Speedmod Kernal K12F 512hz (JL2 Modem). I assume it probably tried to download a FW for an international i9000 and it wasn't compatible with my i9000m hardware. *shrug*.
Trying a factory reset to see if i can get my buttons back.
Click to expand...
Click to collapse
Just tried this and my buttons broke as well... I am on a Bell Vibrant running the latest Doc ROM and SpeedKernel 12I with JL2 modem.
I just reboot and it's still broken... will have to flash JL2, re-run this trick, then flash the ROM back.
Wow... less than 24 hours after I got my SECOND replacement phone... the internal SD has died through this process.
Way too frustrating.
markhole said:
This happened to me out of the blue on JL2. Luckily, it looks like the fix worked for now. Any word of this problem coming back for those who have applied the FW update? Normally i'd apply the fix and forget about it but this device is so janky...
Click to expand...
Click to collapse
It's been two weeks and several rom and kernel flashes, this issue has not reappeared.
Sent from my GT-I9000m
I can also say that this method worked great. Flashed back to JL2, firmware upgrade, and then flashed seeARMS rom.
edit got it fixed
Kewjoe said:
It's been two weeks and several rom and kernel flashes, this issue has not reappeared.
Sent from my GT-I9000m
Click to expand...
Click to collapse
I need help! I have I9000T, and broke my back and menu button.
The trick worked with elcair 2.1 but I upgraded to Froyo 2.2.1 and the trick completely nullify both buttons!
Make Hard Reset and wipe factory reset and wipe data/partition, the problem still append!
anyone can help me? should downgrade to Eclair 2.1?
Thanks a lot!
I remember doing that for the screen and the keys - ive got an international i9000 with the firmware versions
phones tsp fw version : 22
parts tsp fw version : 22
tsp threshold : 70
and
phones touch key fw version : 0xa9
parts touch key fw version : 0xa9
what versions are other people running?
cbdrift said:
I remember doing that for the screen and the keys - ive got an international i9000 with the firmware versions
phones tsp fw version : 22
parts tsp fw version : 22
tsp threshold : 70
and
phones touch key fw version : 0xa9
parts touch key fw version : 0xa9
what versions are other people running?
Click to expand...
Click to collapse
I´ve GT-I9000T with
tsp fw version : 22
parts tsp fw version : 22
tsp threshold : 40
phones touch key fw version : 0xa9
parts touch key fw version : 0xa9
Rom
PDA: I9000XXJPY
PHONE: I9000UGJL2
CSC: I9000OXAJPY
Build Info: 2010.12
and the trick broke my buttons back and home
I have been using some custom rom's around here, Doc's and some Darky's and they were perfectly fine.
Some days ago, I started the SGS Tools application, and got to the "Secret codes".
I was just curious about it, and I got into the "Touch key firmware version"
So there was 2 options, to upgrade the Touch key, or the touch screen.
I pressed the touch key, and then the screen said "PASS" and boom !
The touch keys stopped working.
I tried everything, wipe all, flashing back to 2.1, then back to Darky's, and Darky's Odin. Nothing is working.
It's a driver problem as it seems, can anyone, anyone please help me?
Thanks, I will be so greatful!
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source: http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
xlittle_lambx said:
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source:
Click to expand...
Click to collapse
Hey mate.
Thanks alot! but it doesnt work.
I flashed about 3 rom's. 2.1 rom, original from my country 2.2 rom,
and allways did fw update, but none working.
What can I do?!?
Did you do a complete clean install of your stock rom? What I mean by that is you wipe data/factory reset before and after you flashed your phone's stock rom. As the guide I linked utilized a carrier stock 2.2 rom, try flashing the carrier stock 2.2 for your phone. Wipe data/factory reset in recovery mode, and try the firmware update again via dialer *#*#2663#*#* and select "Touch key FW update" . Reboot your phone.
I have the Bell Mobility I9000M model, as the guide is intended for, but it should work on the international version as well (I'm assuming you are from Asia or Europe?)
Hopefully your touch key issue will get resolved, if not by me, then someone else with more expertise in this forum.
Yes, I have tried all those, but nothng helps.
Someone can help please? thx
help please?
help? please
I have exactly the same problem.##Help
help guys.. please
I have also this problem : (
Has no one any other solution for this problem ?!
Lot's here got this problem, please if someone know's how to fix the problem, please help us all. I tried all, I tried any 2.1,2.2,2.3 rom out there, the JM9 [that shouldve fixed my problem] but non helps.
I finally managed to solve the issue by reflashing to a stock 2.2.1 and using the ##code thingy.
duckbill22 said:
I finally managed to solve the issue by reflashing to a stock 2.2.1 and using the ##code thingy.
Click to expand...
Click to collapse
can you please give me the exact rom you downloaded? thanks.
I came across a thread in another forum that discussed this touch key problem while I was trying to flash Darky's 9.2. You will need to flash to a stock rom. While in stock, go to your dialer and type the following:
*#*#2663#*#*
Then click Touch key FW update.
The touch keys become unresponsive if you try to update the firmware after a kernel change other than stock. Hope this helps.
Source: http://androidforums.com/galaxy-s-al...imal-risk.html
__________________
Download Software
returnix said:
can you please give me the exact rom you downloaded? thanks.
Click to expand...
Click to collapse
The ROM in question was: I9000UGJH2
Sorry, I had to get home to look this up as I only used this ROM to solve the issue and went straight back to Darky 9.3.
I hope this helps
duckbill22 said:
The ROM in question was: I9000UGJH2
Sorry, I had to get home to look this up as I only used this ROM to solve the issue and went straight back to Darky 9.3.
I hope this helps
Click to expand...
Click to collapse
man
thanks you
so much, I really dont know how to thank you.
I will open a thread that will explain to all that this problem happend to them too.
THANKS!
Ditto, I had the same problem, bought the phone from a guy and it already had a custom firmware on it. I screwed up the menu and back keys by upgrading the touch key firmware.
I eventually found this thread, upgraded (or rather rolled back) to the original firmware (in my case I9000UGJL2) and re-applied the touch keys firmware upgrade and voila now my keys work again after a month or two of pulling hair.
nice work and lots of thanks
After a painstakingly long search (upwards of 5 hours, gee thanks SOPA) I finally got ahold of original firmware, flashed and followed the post, worked great Thx! BTW this was for a Canadian Bell GT-I9000M, which I flashed to KC1 to get to work if anybody has similar original firmware finding issues, (took a few trial and errors)
I have the same problem on my galaxy mini, anybody know a galaxy Rom that fix my problem?
Normally I hate haptic feedback, and set vibration for notification only. But today I got a Galaxy S which completely does not vibrate. Ok, I set everything that could possibly make it vibrate, but it still does not.
Is this a hardware issue or can it be fixed by any other software solution?
Please help
PS: I applied 3-button combo fix by ODIN3 method. Unfortunately, I did not pay attention to this issue before applying the fix, can this be a possible cause of the problem?
Thanks
PS: I applied 3-button combo fix by ODIN3 method. Unfortunately, I did not pay attention to this issue before applying the fix, can this be a possible cause of the problem?
Yes if the problem was not there before ..
Try a factory reset.
jje
Thanks for your reply. I did a factory reset, but the issue remains. I heard somewhere it might be caused by installing OCLF, which I also did...
I found an item name /lib/modules/vibrator.ko, guessing this is something to do with vibration and tried out but got no luck yet...
JJEgan, what's with you and not using the "quote" function? It's confusing.
what firmware are you on?
i had this weird issue on the bell i9000M on the stock 2.1 firmware (whatever the firmware version was before JH2). my text message notifications would not vibrate when i received them, but after i updated the firmware, the issue was gone.
kenrick.du said:
what firmware are you on?
i had this weird issue on the bell i9000M on the stock 2.1 firmware (whatever the firmware version was before JH2). my text message notifications would not vibrate when i received them, but after i updated the firmware, the issue was gone.
Click to expand...
Click to collapse
Mine won't vibrate at all. I am using Froyo, and have flashed a few ROMs to see if they help. No luck so far though. I am kinda thinking of sending it back to the seller
Yeah, it sounds like a hardware issue then if you're already running froyo. Hopefully they'll send you a new one that works.
Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Bucika said:
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Click to expand...
Click to collapse
It could be the framework changes you did with the battery.
Flash a stock ROM back on it, see if that solves your problem.
Im facing same problem.. Today was the second time the soft keys wuldnt work since i bought the note 1 week ago..after i ended a phone call it took me back to the call logs so i pressed the return soft key but it wuldnt take me back to home screen!! I cant find what causes that issue however it was fixed after i rebooted the phone.. Im on stock KKA
Sent from my GT-N7000 using xda premium
Bucika said:
Hello, i have my Note rooted, and installed framework for circle battery.
I have baseband XXKJ4 android 2.3.5, besides that everything is stock !
At first everything was working great, no problems whatsoever but now from time to time my soft keys freeze and i must reboot device to get them working again.
So what could be the problem? Should i unroot it and take it back to get it repaired or is that normal? How should i fix it?
Tnx for advice !
Click to expand...
Click to collapse
That's a known issue on 2.3.5
On a number of occasions it happens after a call.
Just switch to the latest stock in the 2.3.6 series and all should be OK.
vizvin said:
That's a known issue on 2.3.5
On a number of occasions it happens after a call.
Just switch to the latest stock in the 2.3.6 series and all should be OK.
Click to expand...
Click to collapse
I also have a stock Galaxy Note & have this same problem sporadically. I don't understand your advice. Could you help an Android noob and put it in language I can understand!
Cheers
albielyons said:
I also have a stock Galaxy Note & have this same problem sporadically. I don't understand your advice. Could you help an Android noob and put it in language I can understand!
Cheers
Click to expand...
Click to collapse
He means: Just update your phone from Android 2.3.5 to 2.3.6
The forum has several threads about updating and rooting
OK, I have figured out that 2.3.6 is the android version. But my phone is already onto that version installed, so I can't upgrade to it to fix the problem....
Any other ideas?
albielyons said:
OK, I have figured out that 2.3.6 is the android version. But my phone is already onto that version installed, so I can't upgrade to it to fix the problem....
Any other ideas?
Click to expand...
Click to collapse
Try to reflash the stock rom, it might solve your proplem