Database Develop

[Q] Capacitive buttons (home and back) wont work anymore [SOLVED!]

Hey there,
I recently screwed around with something i shouldn't have (the touchscreen FW option in SGS Tools) and "updated" the firmware for the touchscreen and touchscreen buttons.
Now the main problem appears that back & home will not work no matter where they are... and it is getting quite annoying.
Any ways to fix this?
already tried flashing a 512pit and re-partitioning but it still doesnt work.
JUST FIXED IT:
Solution incase anybody else has a problem with this.
Get an original firmware for your phone (eg mine is a Bell GT-i9000m so i got the JH2 Firmware which provides FW version 0x2/0x02)
all i did then was hit "touch key FW Update" and it flashed the firmware to the originals that work with the hardware.

risqu3 said:
JUST FIXED IT:
Solution incase anybody else has a problem with this.
Get an original firmware for your phone (eg mine is a Bell GT-i9000m so i got the JH2 Firmware which provides FW version 0x2/0x02)
all i did then was hit "touch key FW Update" and it flashed the firmware to the originals that work with the hardware.
Click to expand...
Click to collapse
Eh sorry, but can you clarify this. Where did you get the stock JH2 from and how did you flash it? Can you flash it on the phone if it's already running JH2?
Thanks

I have the same problem.
Can someone help me?

do this on a captivate?
could I get this on a samsung captivate? Im new to this-any detailed steps would be greatly appreciated!

I9000 Menu and Back key not working

I have somehow disabled the menu and back key on my I9000.
Gone back to the orginal ROM, still not working. Was using Darky 8.0, might have done something in SGS tools. Can someone please help!
Thanks

Try flashing stock firmware of your phone
Then update the touchkey firmware

Ive Flashed to orginal but not go, Tried several versions but not luck. Where do I find the touchkey firmware?

HI Everyone,
Im getting really desperate, I cant find how to get the menu and back keys functioning again. I have look hard on the forums but no real answer.
What I know is I went into SGS Tools in 2.2.1 ,I pressed an update touch screen I think.
please help!
Cheers

Could be hardware I've had to repair two phones where touch buttons don't work
Sent from my NCC-74656!

HI,
After I did a firmware upgrade I F*&d out. Must be software
The Phones TSP FW - 22
Parts TSP FW - 22
TSP threshold - 40
Touch key FW - 0xa9
Parts Touch key FW - 0xbf

+1 same here, I could not fix it
what version of phone you got?

I *just* had this issue.
Started out with my back key hanging on me after getting a custom ROM installed.
So I attempted to update my firmware for the menu and back keys and lost them both.
This seems to be any custom ROM, cannot handle the touchkey firmware update.
How to fix:
Grab ODIN and your stock 2.2.x firmware.
Disable lagfixes if you need to.
Flash it.
Update your touchkey firmware ( *#*#2663#*#* in dialer)
Now reflash a CWM kernel with ODIN
Re-apply your custom rom from sd.
I used the wipe option whenever possible so I would recommend the same.
My touch keys are once again working perfectly and Darky's rom is screaming fast.
I found the issue and fix after noobproof tipped me off to search out this thread:
http://forum.xda-developers.com/showthread.php?t=869492

ieatrocks said:
I *just* had this issue.
Started out with my back key hanging on me after getting a custom ROM installed.
So I attempted to update my firmware for the menu and back keys and lost them both.
This seems to be any custom ROM, cannot handle the touchkey firmware update.
How to fix:
Grab ODIN and your stock 2.2.x firmware.
Disable lagfixes if you need to.
Flash it.
Update your touchkey firmware ( *#*#2663#*#* in dialer)
Now reflash a CWM kernel with ODIN
Re-apply your custom rom from sd.
I used the wipe option whenever possible so I would recommend the same.
My touch keys are once again working perfectly and Darky's rom is screaming fast.
I found the issue and fix after noobproof tipped me off to search out this thread:
http://forum.xda-developers.com/showthread.php?t=869492
Click to expand...
Click to collapse
Thanks.
FOr gods sake, everything was going fine until i started poking around sgs tools "oh what's this? touchscreen firmware update yes please!" doh..
back to square one

Very Very thaks.
Works fine for my, it took the same problem as that as an idiot from a custom rom touches in update touch keys and they stopped working.
Thaks really

ieatrocks said:
I *just* had this issue.
Started out with my back key hanging on me after getting a custom ROM installed.
So I attempted to update my firmware for the menu and back keys and lost them both.
This seems to be any custom ROM, cannot handle the touchkey firmware update.
How to fix:
Grab ODIN and your stock 2.2.x firmware.
Disable lagfixes if you need to.
Flash it.
Update your touchkey firmware ( *#*#2663#*#* in dialer)
Now reflash a CWM kernel with ODIN
Re-apply your custom rom from sd.
I used the wipe option whenever possible so I would recommend the same.
My touch keys are once again working perfectly and Darky's rom is screaming fast.
I found the issue and fix after noobproof tipped me off to search out this thread:
http://forum.xda-developers.com/showthread.php?t=869492
Click to expand...
Click to collapse
unfortunately, this method seems not working for me, please correct me if i did the steps wrongly.
I have samsung galaxy s vibrant, model is gt-i9000
I flashed the phone with odin. in the pit i have 502, and jpy for the pda.
after flashing, i update the touch key fireware by pressing the numbers that brings the update menu. and pressed the the update button.
after updating, the back key and menu key are not working.
then i rooted the phone then install darkys rom 9.2 extreme.
after installing the rom, the keys are still not working.
here the version of the touch key firmware:
phones touch key fw version: 0xa9
parts touch key fw version: 0xa9
phones tsp fw version : 22
parts tsp fw version: 22
tsp threshold: 70
if anyone has different method please let me know
thanks

still nothing
this is killing me. Ive flashed back to 2.2.1 and tried all the other steps. The only problem is that my phone orriginally came with 2.1. I wanna try everything with my original firmware. Does anyone know where i can download a copy 2.1. from?

I had exactly same problem with damn 'return' softkey. I have searched and tried a lot of methods and no chance, I recomend you to go to samsung repair center. Aparently they replaced motherboard and screen to repair this issue.
Sent from my GT-I9000 using XDA App

sorry, dont use forums to much, made a repeat

no way out
eggtony said:
unfortunately, this method seems not working for me, please correct me if i did the steps wrongly.
I have samsung galaxy s vibrant, model is gt-i9000
I flashed the phone with odin. in the pit i have 502, and jpy for the pda.
after flashing, i update the touch key fireware by pressing the numbers that brings the update menu. and pressed the the update button.
after updating, the back key and menu key are not working.
then i rooted the phone then install darkys rom 9.2 extreme.
after installing the rom, the keys are still not working.
here the version of the touch key firmware:
phones touch key fw version: 0xa9
parts touch key fw version: 0xa9
phones tsp fw version : 22
parts tsp fw version: 22
tsp threshold: 70
if anyone has different method please let me know
thanks
Click to expand...
Click to collapse
i took my phone in for work today as ive tried everything and cant get it to work. Ive flashed almost every bit of firmaware i could find and and i could not get it work at all. When i took it to them they said that they've had a ton of problems with the new firmware frying the soft touch buttons. If you cant get your buttons to work i would recomend taking it to where you bought it and seeing if you can get warranty or even just send it out for repairs. Although sometimes it is just an issue with the firmware for the touch screen. Please let as many people as you can know that its a really really really bad idea to update the touchscreen firmware when you have flashed your phone with any roms other than the stock firmware that came with your phone. Have fun! I know i will waiting 4-6 weeks to get my phone back and sitting with a blackberry 8330, oh well, better than nothing.

Hey guys,
When I flashed my carrier stock rom I did not use any PIT options.
If JPY was the rom your carrier issued you then that should be the one you use.
Basically, the touchkey firmware update worked for me on a stock, carrier issued 2.2 (not 2.1 or 2.2.1, though those may indeed work) rom.
Once touchkey was re-updated in the stock, unrooted rom, I flashed back to custom roms as normal.
It looks like you did some pit repartitioning and used a JPY rom not issued by your carrier.
Also, my gt-i9000 is bell issued, so I've got to be wary when repartitioning not to kill my sbl.bin fix and introduce sd corruption issues; so I flash a stock rom with a bootloader update if I think a custom rom may have wiped it out.

eggtony said:
unfortunately, this method seems not working for me, please correct me if i did the steps wrongly.
I have samsung galaxy s vibrant, model is gt-i9000
I flashed the phone with odin. in the pit i have 502, and jpy for the pda.
after flashing, i update the touch key fireware by pressing the numbers that brings the update menu. and pressed the the update button.
after updating, the back key and menu key are not working.
then i rooted the phone then install darkys rom 9.2 extreme.
after installing the rom, the keys are still not working.
here the version of the touch key firmware:
phones touch key fw version: 0xa9
parts touch key fw version: 0xa9
phones tsp fw version : 22
parts tsp fw version: 22
tsp threshold: 70
if anyone has different method please let me know
thanks
Click to expand...
Click to collapse
you said you have a vibrant and you flashed back to jpy.
if you have a vibrant the product must be GT-I9000M
if you have a vibrant (gt-i9000m) you must flash to your carrier's latest rom-as far as i know bell's latest rom is jh2, search the forums for that- then update your touchkey fw.
hope this helps.

NoobProof said:
you said you have a vibrant and you flashed back to jpy.
if you have a vibrant the product must be GT-I9000M
if you have a vibrant (gt-i9000m) you must flash to your carrier's latest rom-as far as i know bell's latest rom is jh2, search the forums for that- then update your touchkey fw.
hope this helps.
Click to expand...
Click to collapse
it did work !!
appreciate much brother

hey!
I had the fu***** same problem, so this is how I solve it.
First i had Eclair 2.1 then update to Froyo 2.2, I typed *#*#2663#*#*
Then click Touch key FW update and my back and menu button was broken.
So I flashed back Eclair 2.1 re-ryped *#*#2663#*#* Then click Touch key FW update and my buttons was fixed!!! So you can flash again any ROM you want.
Let me know if it works for you.
follow @androidmx

I have replaced the front panel of Galaxy S, later menu and back button didn't work. I thought lcd is broken but update firmware of the lcd helped.

[Q] trouble with my Sasktel Galaxy S

I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)

I am also on sasktel and am an impulsive flasher (1-5 times daily) Heres an easy, fast fix. GO here:
http://www.darkyrom.com/community/index.php?threads/guide-installing-rc5-easy.2382/
go to section enabled "For GT-I9000 users only" and follow step by step. You can stop at step 2 if you want to leave your rom stock samsung or do last few steps to have darkys on there. EIther way once done you'll also have to enable the 850 band *#2263# then enable wcdma 850 option. Also you will have to manually enter your APN under network options. I use inet.stm.sk.ca for sasktel. Note that the Ficeto_JVB.zip download there includes all needed to flash (.pit file, rom, odin). THis is always my fail safe method after boot loops ( I always screw something up playing around lol).
ps: also depending how desperate you are and how trusting you are, I work at sasktels head office in the cornwall and if you wish I am sure I could take 15 mins out of my day tomorrow to do this for you, although you will not be able to get through security so you will have to trust me taking off with your phone lol. email me at [email protected] if needed.

trouble is I can't put things on SD card because I can't get it to load android

You won't be able to load eclair through Odin because JL2 installed a new SBL (secondary boot loader). Go to samfirmware.com, download JL2, and use odin to flash that. Once that's flashed it should fix your issues. Then, if you want a custom ROM, try the romkitchen (romkitchen.org).

problem solved!! turns out darkyrom did fix my phone, I couldn't push the zip file to my phone but their tar file got my phone working! Thanks for all the help

Dougustine said:
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
Click to expand...
Click to collapse
I loled, I've been in the same boat, wife is always asking me why I always have to mess around with stuff. Shoulda seen her face after I soft bricked the phone the first time.

Just rooted my phone
I am new to this, I can do all kinda of things with my pc but with my phone a different story lol. I don't understand when you say "Eclair". Is that a different model or is that stock. I am too from sasktel.

Android 2.1 is Eclaire, 2.2 is Froyo and 2.3 is Gingerbread... Ice cream is next 4.0

hi guys, I know this is an old post but has anyone successfully unlocked their Sasktel i9000 vibrant without paying any unlock code service? has anyone tried anything like the SGS Unlock Pro that claimed to unlock all GSM galaxy S phones but did not list Sasktel? anyways, from the sound of it is Darky's rom currently the best for i9000's? I wanted to try CM9, so i did the super 1 click root and followed the CM wiki page to push clockwork recovery to the phone through Heimdall Suite but both times i tried failed and stuck in a boot loop so both times i ended up going through Odin to fix it. (super 1 click root didnt seem to stick b/c i lost superuser after fixing the phone w/ Odin, is that normal?)
anyways i had a very unique situation, originally had a Bell i9000m but died 1 week later tried to fix it numerous times for 7-8 months ( i live in U.S., and Sammy refuse to fix it b/c i dont have a canadian address they can send it back to b.s.) anyways finally landed myself a dead i9000m w/ broken screen, so i took both apart and put the working parts together. now 1 working phone with 3 problems: 1) so it seems that it's currently locked to Sasktel (it can be done but i'm curious if there is a cheaper way or even free) 2) CM wiki suggested Heimdall push CW recovery cause boot loop (some on xda suggested flashing the phone back to 2.2 (or 2.1??) first) 3) i was playing around and click on screen update and lose my touch keys ever since (ppl also suggest flashing it back to 2.1 and reupdate the keys, but will a bell i9000m 2.1 stock rom be compatible w/ the i9000m from Sasktel?)
anyways lots of questions there but if anyone can answer anyone of these would be greatly appreciated.
thanks in advance
Update: problem 1 is taken cared of. SGS Unlock Pro worked like a charm. tested, working. other 2 problem still unsolved.

Need some advice with i9000M

Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat

By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)

So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!

Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks

UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys

Please help guys, I know some of you out there have got this stuff nailed down!

Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.

Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?

When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha

Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.

Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!

Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess

One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..

Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.

That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?

Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat

If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.

You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium

Quebec province

Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.

[Q](SOLVED) - Need 2.1 firmware for I9000M (Bell, Canada)

Hi Everyone,
Recently, I got a Galaxy S I9000M from a friend. The phone was running 2.1 firmware when I got it. There were two updates for the phone from kies(2.2 & Gingerbread) I updated the phone to 2.2 froyo from kies. later, kies stopped to recognise my phone. so I thought to root my phone and did using rootme 2.2. I don`t know if the phone was rooted but I could see superuser. Then I flashed with some ROM and messed my phone. on booting the phone stuck on blinking on galaxy s logo and will not start. After flashing few more firmware, I am stuck on brick picture on phone. I cannot go to recovery also but I can go to download mode. I am guessing that flashing the stock 2.1 may help to start the device. I have searched everywhere to find the stock 2.1 for i9000M but cannot find because many links are dead and samfirmware.com does not show me the old firmware. By the way, I have downloaded stock 2.3.3 (samsung-updates.com) which I don`t know will work.
Please help me to find the stock firmware or any other way though which I can solve my problem. Tell me which files do I need and how can I flash.
Thanking everyone in anticipation.
Edit: I found stock froyo 2.2 files and phone is working again