[Q] Capacitive buttons (home and back) wont work anymore [SOLVED!] - Galaxy S I9000 Q&A, Help & Troubleshooting

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!

Related

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] Back Button Problem for i9000T - specifically

Ok so i have found several threads referring to this but mostly speak of a possible fix where we are supposed to do *#*#2663#*#* and upgrade the touch key FW.
There is a disclaimer where it specifically says it is for the i9000M with some people getting errors after doing it on non i9000M devices.
So does anyone know if this solution works for the i9000T version or if there is another way to disable this?
I can live without screen capture so if anybody knows how to simply turn that off i would also appreciate.
thank you
barnetty said:
Ok so i have found several threads referring to this but mostly speak of a possible fix where we are supposed to do *#*#2663#*#* and upgrade the touch key FW.
There is a disclaimer where it specifically says it is for the i9000M with some people getting errors after doing it on non i9000M devices.
So does anyone know if this solution works for the i9000T version or if there is another way to disable this?
I can live without screen capture so if anybody knows how to simply turn that off i would also appreciate.
thank you
Click to expand...
Click to collapse
Hi,
I have the same problem of the back buttong activating itself & my phone is I9000T, I have ran the update as indicated above which took 2 hours looping & never fixed the problem!!
Thanks

[Q] Softkeys not working after update

I updated my SGS using Kies to 2.2.1. I have not rooted the phone or made any other changes to the firmware before this. After the update, my back key randomly seems to have gotten "stuck" and pressing the home key snapped a screenshot. This was bad enough. Now, both softkeys have stopped working, although the home button seems to work fine. I have done every reset on the phone that I can find, but still no help. Of course, I am still running 2.2.1. I can't think of any other cause for the problem except the update. Has anyone else had or heard of this and does anyone know of a fix?
SGS GT-I9000T
Firmware 2.2.1
Kernel version 2.6.32.9
Build number FROYO.UBJP9
PDA I9000TUBJP9
Phone I9000TUBJP9
CSC I9000TUUBJP9
Build Info 2011.01
Sent from my Laptop 'cause the **** phone won't work right.
I have had this problem before. What I had to do to fix it, was flash a 2.1 rom with Odin.
If you don't want to go that route, check in Kies somewhere in the tools tab for an emergency firmware recovery. Hook the phone up and see if that will fix your issue.
Have you factory reset your phone?
I have already tried the factory data reset and the factory format. Nothing from either of those options. I tried the Kies emergency recovery and it is asking me for a code that I have no idea where to get...
I am downloading the files now to try the Odin flash...I guess we'll see how that works.
The next logical question would be why did this happen? Will I be able to update to Froyo? Or is this gonna happen again the next time I try to do an official update?
It could just be a buggy flash. I really don't know the answer to that.
If your 2.1 rom has 3 files, flash with a 512 pit and re-partition.
If 1 file, no pit no re-partition.
Yes, you will be able to upgrade to Froyo afterwards.
Not sure what happened, but something didn't work right.
After the first flash, all appeared to be well, but when I tried to swipe the screen to unlock it, nothing happened.
So I tried it again. Now, there is an eight sided star type thing that keeps flashing on the screen. If I disconnect the USB cable, the Samsung screen keeps flashing. I can't get ADB or Odin to recognize anything.
Any ideas?
PHEW! Using the button combinations I was able to get back into download mode and I am currently flashing again. The most surprising thing is that the button combination trick didn't work before. Hopefully it will work this time.
Damn! So much for that. Even after flashing again, everything just keeps flashing. I would greatly appreciate any help or ideas that anyone might have.
Alright, final update for the night. I finally got it flashed, and its now flashed to
2.1-update1
I9000XXJG1
Kernel 2.6.29
ECLAIR.XWJG5
PDA I9000XWJG5
Phone I9000XXJG1
CSC I9000OXXJG4
At some point I might try to do the Froyo update again.
Now the bad news...soft keys still not working. Any other thoughts on what could cause them not to work?
The firmware that you have just successfuly flashed, was it 3 files or just 1?
Have you tried to update and touch key drivers previously?
I updated with a 3 file which I found at samfirmware.com. It's currently the only thing I could get to work. I believe that it is what I had before the Froyo update. And I seem to have all functionality except the softkeys.
I haven't done any other updates since or any driver updates. I didn't even know there were any.
Did you use a 512 pit and re-partition?
I had this problem before once, and I flashed this firmware and it resolved the issue. It's up to you if you want to try it. It is an Australian 2.1 firmware.
http://www.megaupload.com/?d=45UEDN35
If you want to give it a try, use a 512 pit and re-partition.
Alright, I downloaded your files, but when I tried to unzip the files, I keep getting an error the the files are corrupt. Not sure what is going on there.
I am a dumba$$. I just realized that my wife has the EXACT same phone as me. We got them at the same time, so all the original information is the same. What I need is:
GT-I9000T
2.1-update1
Baseband Version I9000TUBJG7
Kernel version 2.6.29 [email protected] #2
Build number ECLAIR.UBJG5
PDA I9000TUBJG5
PHONE I9000TUBJG7
CSC I9000TUUBJG4
Is there anywhere that I can get this firmware? Is there anyway to make a backup copy from my wife's phone that I can just install on mine? I do not have root access on here phone, and after all the trouble I'm having with mine, I don't think that she'll let me, so hopefully there would be a way to do it without it.
Hey man,
I did a little searching for you, but could not find that exact firmware. I did find this, and it should work.
Here's the thread.
http://forum.xda-developers.com/showthread.php?t=907701
Here's the download
http://www.mediafire.com/?7wgu37wek6vybia
Rom info
GT-I9000T
Baseband Version2.1 update1
Kernel Version 2.6.29 [email protected] #2
Build ECLAIR.UBJI1
PDA: I9000TUBJI1
PHONE: I9000TUBJH1
CSC:I9000TUUBJI1
Edit: I did read through this thread a bit, and it seems that this rom may disable 3 button recovery. If that's the case, I would still flash this to get your softkeys working again. Make sure to flash the 3 button fix after this firmware flash if it no longer works.
I actually found and flashed that firmware a little while ago with no improvement. Still no softkeys. I am completely confused. I thought this was software, and now I am beginning to wonder. Is there anything else that I can install that might fix this?
Since I no longer have stock firmware and don't seem to be able to be able to find the original again, I'm not sure that I am even going to be able to take it back to my carrier, since I believe that the warranty is voided unless I can return it to the original firmware.
Hello,
I'll keep an eye out for that firmware, it has to be somewhere you would think.
In the meantime, to pull the backup from your wifes phone, I do believe you need root access. Maybe you can pursuade her by cooking her a nice dinner with a good bottle of pinot noir
In the meantime, I'll keep looking for you.
I'm not even sure how long it's been anymore, but I am still working on this...
Okay, so I think I'm just going to swipe my wife's phone and root it while she is not looking...
My question is this: Is there a guide that will tell me how to 1. root (then unroot) her phone and 2. create a backup of her firmware that I can install on my phone. Also, if said backup can be used with Odin, I will be happy to share it here since it seems to be lacking and much needed.

[Q] I9000M rom on I9000

I am having problems with my back and menu buttons in that they just don't work. Have tried the *#*#2663#*#* trick on stock Roms in 2.1, 2.2 and 2.3 but still not having any luck. Under 2.2 when i ran the touch key FW update it said it passed but made no visible difference.
I have been searching on the web and everyone that i can find that had this problem has solved it by going to a stock firmware for a i9000M and doing the *# trick. But i don't know if they all have i9000M or are they flashing a i9000M rom on to a i9000 to get the soft touch buttons working.
So my question is can i flash a i9000M rom onto a i9000 fix the buttons and then flash back to a normal i9000 rom? (specifically i9000UGJH2 and i9000UGJL2)
Or if anyone else has fixed this problem can you let me know how because it is driving me insane!!!
I don't see why not as the i9000 and i9000m are vitually the same phones.
I bought a i9000m as I live in Canada and have flashed i9000 firmwares numerous times and haven't encountered any problems.
Just don't flash JH2 as this firmware had some major issues that actually bicked a lot of our phones.
Use JL2 instead if you want to stick to Froyo.
Hmmm... didn't seem to work tried to flash JL2 like you mentioned but the phone stop at the samsung i9000M screen (the very first screen) and got no further. I tried to leave it for about 15mins but was the same when i came back.
Anyone else got a suggestion of how to fix back and menu buttons on a stock standard i9000 (not i9000T or i9000M)... driving me insane!!!
Currently on XXJVR and the *#*#2663#*#* trick seems to say it passed and firmware version changes to either a9 or ff, but i still have no back or menu buttons .
Please help getting slightly desperate ...
I have the same problem, I have a 9000M and did a KIES update into 2.3.3 which screwed my phone, having nothing to reflash it I found only a 9000 ROM and it worked fine until I did a stupid TOUCH KEY firmware update now the keys are dead too...
I'm working on this now I have no idea where to start though files are hard to find online
---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------
If this can help you, get CHECK FUS online search for it you can get a lot of stock SAMSUNG firmwares from that, though I'm **** out of luck the only 'BELL' one which I was jumping around to have found doesn't seem to work when I flash the supposedly 9000M stock for mine, it just hangs and reboots at the 'S' logo screen when booting, I wonder whats wrong.
The only ROM I can get booting on this POS is a 2.2 FROYO for a i9000 JP2 which works fine, but I need to fix my keys.
MaTSuNg
I finally got a I9000M rom to work but didn't solve my problem anyways. I ended up going to cyanogen 7.1 and one day my buttons just started working again after I got a pxt message. since then I have flashed a number of different roms and buttons seem to come and go but after i flash if I just use the phone for a day the buttons eventually come good... so the problem is defintiely a software/firmware one but I can't seem to narrow it down anymore than that.
Cheers
MaTSuNg
You can get the 2.3.3 firmware here:
http://forum.xda-developers.com/showthread.php?t=1102881
Search for UGKG3. That's the one and only Gingerbread release to date for Bell.

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.

Categories

Resources