Related
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.
I flashed my brothers phone with a JVR Korean firmware, the reception was terrible. I then proceeded to flash the JH2 firmware, thinking i could use that and upgrade to kies. BUT SMALL PROBLEM.
i found the firmware, flashed it along with csc and modem. but now when i open kies, it shows the JH2 Firmware in the software version area, but then besides JH2 its says (KOR).
I tried the reg hack, nothing worked, apparently my product code in "rededit" is set to the kor version, i tried changing it but nothing......how do i fix this?. its really pissing me off
edit** if i wanted, if its too much trouble to get back to stock, could i theoretically from froyo get cf root on it? then install gingerbread roms after flashing CWM through rom manager?
Try this to change your product code:
*#272*imei#*
Where imei# is the actual imei # to the phone.
Please keep in mind, changing this will wipe the phone to factory default
greeced said:
Try this to change your product code:
*#272*imei#*
Where imei# is the actual imei # to the phone.
Please keep in mind, changing this will wipe the phone to factory default
Click to expand...
Click to collapse
SO when i do that i can change the product code right? not the IMEI code? cause i dont really feel comfortable changing the imei code :s
EDIT* thaat code wont work!!
---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------
Hey the code didnt work! and i also reflashed using odin! it shows on KIES all the CSC: JH2, PDA: JH2 but after JH2 it says (KOR) and "this version cannot be updated."
is the phone rooted?
Best course of action if you want official stock 2.3.3 on the phone would be if it was rooted, then download SpoofFw from the market and change the firmware to the Canadian region one. I believe the program sets the phone to JL2.
After that, plug it into kies, it should want to update to KC1 first, then to KG3 (2.3.3).
After that, the product code will most likely still be KOR. If it is, do the code I mentioned above and change it to BMC.
greeced said:
is the phone rooted?
Best course of action if you want official stock 2.3.3 on the phone would be if it was rooted, then download SpoofFw from the market and change the firmware to the Canadian region one. I believe the program sets the phone to JL2.
After that, plug it into kies, it should want to update to KC1 first, then to KG3 (2.3.3).
After that, the product code will most likely still be KOR. If it is, do the code I mentioned above and change it to BMC.
Click to expand...
Click to collapse
I was using this method
http://forum.xda-developers.com/showthread.php?t=835628
phone is NOT rooted, but apparently using this you can just trick kies, and it should push a update! BUT everytime kies wants to start sending the update, my usb disconnects!?? and its only when kies wants to push the update to the phone
edit** i also tried flashing CF root thorough ODIN, has 2 files, the pit, and the pda CF root file...when flashed my screen just stuck at the GT I9000M logo..
Unless I'm wrong, that method hasn't worked in a while.
If you can root your phone, do so.. its pretty easy after that.
If you don't want to root, then download KC1 from samfirmware, and install it via odin. after that KIES should update to KG3. If it doesn't, I know the code I mentioned above works on both Froyo and Gingerbread.
However if your phone is still disconnecting, you may have to reinstall the drivers for the phone on your PC.
Can you link me to it? i cant seem to find it, i have a username also :s
edit* found it, will try flashing and hopefully this works
---------- Post added at 01:03 AM ---------- Previous post was at 12:45 AM ----------
So i downloaded the KC1 firmware, and inside the rar file is called a I9000UGKC1_homebinary.rar, and inside that when extracted is a modem,zimgage, and other junk files....what am i supposed to load on the phone?
I dont see any csc, or modem files, is that huge homebinary supposed to be flashed on pda? so all your flashing is PIT and PDA?...
editt** never mind, you just put the huge file on pda, and select the pit and flash
Are you sure its a .rar file you downloaded and not a .tar?
If its a .tar, just put it in the PDA section of ODIN. Do not unrar or untar it.
Ok thank you so much Greeced, who sat here with me for the past little while triyng to fix this problem! After flashing the KC1 firmware, Kies now is updating my firmware....as of right now its backing up all my files. Once again thanks sooo much. Another reason why i love xda. They always help with all 3 smartphones ive had
Ha, you're lucky you had a question to the one problem I knew the answer to... I'm still very new to all this too... And many have helped me.
Glad it worked... Just remember if the product code is still KOR, the code above will now work.
Edit* - and for good measure, once the phone is back on KG3 and the BMC product code, be sure to boot into recovery mode and wipe cache and factory default to clear any residuals that may have remained behind. Otherwise you may get a few force closes.
greeced said:
Ha, you're lucky you had a question to the one problem I knew the answer to... I'm still very new to all this too... And many have helped me.
Glad it worked... Just remember if the product code is still KOR, the code above will now work.
Edit* - and for good measure, once the phone is back on KG3 and the BMC product code, be sure to boot into recovery mode and wipe cache and factory default to clear any residuals that may have remained behind. Otherwise you may get a few force closes.
Click to expand...
Click to collapse
Running into another problem, it will say checking firmware bla bla, downloading, but then my gt on the bottom right corner of kies, says "connection lost." it keeps doing this and is getting rather annoying....
edit** IMEI code did the change thingy, will test again...
Ok try this:
Before you do anything, boot into recovery mode and wipe cache and factory default, then try KIES again. If it still doesn't work:
1. Go into device manager with the phone plugged in, and remove the samsung drivers (uninstall).
2. Disconnect your phone.
3. Uninstall KIES.
4. Restart your computer
5. Download a fresh copy of KIES and install it.
6. Plug your phone in and have it install the drivers.
7. Run KIES and try it again.
greeced said:
Ok try this:
Before you do anything, boot into recovery mode and wipe cache and factory default, then try KIES again. If it still doesn't work:
1. Go into device manager with the phone plugged in, and remove the samsung drivers (uninstall).
2. Disconnect your phone.
3. Uninstall KIES.
4. Restart your computer
5. Download a fresh copy of KIES and install it.
6. Plug your phone in and have it install the drivers.
7. Run KIES and try it again.
Click to expand...
Click to collapse
Never mind! i got it working! did the imei code you said to do! kies is now updating! thanks for the help buddy! Now time to get onto that 20% final project due tomorrow. Sigh, family first really appreciate the time you took to help out sometimes people just skip over threads like this, thanks buddy
Anytime... thanks
+1 this has worked for me to flash a bell phone back to stop w/ the latest update
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
I had a similar SIM card issue when I tried to activate the 1700MHz band in Service mode (for fun). Wipes and stuff didn't solve anything. The way to revert it for me was flashing a full stock Samsung firmware in Odin.
Can you provide more details on how you did this?
Where does one get a full stock sammy note firmware?
Are there some good instructions on this?
I have flashed my SGT via odin several times. Same odin? Same process?
In the development section you will find some versions.
The key for me was flashing a new Modem (Radio/base band) image via Odin I think. I changed Kernels and ROM's but only flashing a ROM including the Modem got rid of my SIM issue. Not sure because in the end I flashed a full N7000OXAKJ1 firmware in Odin from here:
http://forum.xda-developers.com/showthread.php?t=1310513
It did the trick, though the tread is dead. I think any ROM including Modem might help, I currently running the 2.3.6 N7000ZSKK1 firmware and it is great, also included a Modem.
http://forum.xda-developers.com/showthread.php?t=1342797
fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
when this happened to me, also due to turning on 1700, I was able to reset my phone by doing a factory reset. Unless your modem.bin is corrupted, you should not have flash a new rom.
- frank.
ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...
fwelland said:
ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...
Click to expand...
Click to collapse
Here is Chodthewacko posted about it:
http://forum.xda-developers.com/showthread.php?t=1335920
Factory reset and toggle band settings seems to have worked for him. I got frustrated and Odin flashed everything, that worked for me.
whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...
fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
OMG I have the EXACT same issue as you, and I got mine from NEGRI also! It was working perfectly until last night --- all of a sudden I got that circle and I've been trying to fix it since then! Please keep me posted if you find a solution, I was going to try and contact Negri tomorrow for an RMA.
still nothing.
I did a root. No changes...
I did a rom flash of kk1 ... no changes....
I was trying to reflash the modem with KJ6 modem....but have a signature failed problem...
now what???
I solved my issue by a combo of those steps.
I did full flash in Odin of jk1. When I rebooted that didn't solve things so I wanted to flash the other recommendation, kk the Chinese rom.
Upon entering recovery I noticed I lost 2e and was on 3e. So I had to download chainfire's rooted jk1 kernel and do that zerg rush to get root. It was while I was doing that that suddenly my similar got recognized. By the time it finished installing the rooter kernel I had full reception again. I flashed kk just for good measure and its been smooth since. Hope it works for you too and I'd love to know what the heck broke it in the first place??
Sent from my GT-N7000 using XDA App
hi fwelland, it's hk1981...so you tried the rom flash and it didn't work?
Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k
fwelland said:
Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k
Click to expand...
Click to collapse
I had that problem too, it doesn't detect that CSC and then goes ahead and applies something. Check to see if you are in 3e recovery, I think you are after having flashed vanilla JK1.
Re-flash Chainfire's rooted kernal for your appropriate version and then go back into recovery and it should be 3e and you can flash thru CWM then.
Also note; each time I flashed, I also wiped data/cache/davlik just to be sure.
yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1
fwelland said:
whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...
Click to expand...
Click to collapse
My rough guess is that the phone has a list of 'valid service menu options', and it cross references it with what is on the SIM card.
Once the phone decides it's not going to read your sim card, the service menu is blank. This is a real headache.
That's why once I set the 1700+2100 combo, and my phone boycotted my sim, I wasn't able to set it back.
That's really dumb, imho, to have a one way toggle like that. I'm fine for settings to enable/disable other settings, but for a setting to disable itself? ugh.
I would really like to know what's going on. I was planning on switching to AT&T before my next trip (which is soon) but I can't risk my phone glitching out like that during the trip.
Actually, the ROM is on my SD card so I guess it wouldn't be THAT horrible, but it's certainly not something I want to do. Perhaps we just need a way to flash back the modem.bin, assuming it's corrupted.
- Frank
Sorry typo on my part. You are in 3e recovery because of that base flash, now you need 2e recovery which you can get via chainfire's rooted kernel. His installation procedure runs a batch file that uses that zerg rush exploit which I gather is partially from gingerbreak. It was during this procedure that my baseband suddenly came back, my sim card finally detected.
Once that was done, I entered 2e cwm with volume up,power,middle button and did erase of data,cache,davlik and then flashed kk rom via zip file.
Sent from my GT-N7000 using XDA App
fwelland said:
yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1
Click to expand...
Click to collapse
For me flashing all partitions via Odin worked (no pit file or repartition). Tried all sort of stuff from recovery first with no result.
I don't know what partition flash from Odin did the trick, but you could try Odin flashing a Modem separately and check if that works. If not try the rest?
Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....
fwelland said:
Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....
Click to expand...
Click to collapse
Oh when you flashed jk1 I assumed you did it the old way via Odin and the multiple files. That's how I did it and you're right, that may be what fixed it as when I used to brick my sgs and sgs2, it was always a full Odin flash of stock that brought it back from the dead
To flash in Odin put your phone in download mode. Fire up Odin. In csc point to csc file. In phone section point to modem and for PDA you point to the code file. Don't put anything for pit or bootloader and unchecked the repartition toggle.
Connect your phone and wait for Odin to detect it and show yellow in the status window. Press start and you're good to go. Hope this does it!
Sent from my GT-N7000 using XDA App
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.
So, I recently installed CM9 and on top of that SlimBean 2.6. Both worked otherwise perfectly, but I couldn't get my 3g connetion to work on either one, unless I turned "National Roaming" on. I checked the Acces Point Name settings, and they seem to be fine. I can't find my service provider on the Network operators list though. I read that a new modem migth do the trick, but I have no idea if that will help or which modem to choose.
I had a similar problem after going to CM9. I even had my APN (access point names) settings disappear randomly also.
Solution for me was to turn 'airplane mode' on....wait 30 seconds then turn off.
Strange as it sounds but it actually worked for me. But in the end, (after 1 day) I changed to samsungized 12.1 JB rom because I found that I had to use that airplane mode on/off alot and was too much of a pain.
Hope this helps.
If not, I'd revert back to a stock rom then upgrade to a stable JB rom
Tried just that, but no luck so far. Any other suggestions?
Taatero said:
Tried just that, but no luck so far. Any other suggestions?
Click to expand...
Click to collapse
Id recommend trying a good stable stock rom with a 512_pit repartition via Odin, just to see it it improves the modem or not.
The rom im going to suggest has a replacement Modem file within.
Might sort the problem.
Ive used this stock rom to fix my many problems ive had after custom roms.( Mainly format errors i had )
Its from 'HotFile' site and took me around 20 mins to download it.
But it might be worth the wait in your case.
Rom File:
http://hotfile.com/dl/140301534/be8872c/I9000XXJVU_I9000OXAJVU_OXA.rar.html
Here Is the Pit File and Odin version I used. ( 3rd box down the page )
http://forum.xda-developers.com/showthread.php?t=1102881
And heres the Root file. Get " CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS " :
http://forum.xda-developers.com/showpost.php?p=15188469
s1_odin_20100512.pit Goes in PIT ( repartition checked )
CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 Goes in PDA
GT-I9000-CSC-MULTI-OXAJVU.tar.md5 Goes in CSC
MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5 Goes in phone
Sorry if im telling you what you already know with how to use Odin, just making sure.
After rom install pop this root on with Odin via download mode.
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS goes in PDA
I reckon its worth a shot.
Must make sure the 3 wipes are done before the rom install. I learned this the hard way and messed my
phone up for a while.
Problem solved! I did some googling around, and found a solution. Apparently my carrier, Saunalahti, is known for having problems with 3g on custom roms. I found out that a nexus s modem by the name of i9020AUCKF1 might work. And sure enough, it did the trick! No more roaming! Anyway, thanks for taking the time to help me!