From what I have gathered... this seems to be a problem that only I have encountered, or at the very least something that I have deemed annoying enough that now I have to solve it... but I recently threw Gingerbread onto my i9000, quite successfully I might add, but I decided I wanted to go back to Froyo until the official release of 2.3 comes out of Samsung, since I am a big fan of "stock".
Problem is, every single ROM (I am at ten and counting) always results in Kies telling me that there is no update available. I have been loading only stock ROMs onto my device, so I am a little confused by this, since even the 2.1 firmwares have given me the same message. I know that, when I had Froyo loaded on stock, the message read that everything was up to date or something along those lines. Having that knowledge just means I won't be able to stop trying to put things back to stock until I see that same message again.
Anyone able to shed some light on what is happening here and how to fix it? Ideally I would love to load up 2.1 Eclair, update to Froyo using Kies and then just call it a day.
(PS. on Gingerbread I am getting some weird "static" screen popping up every time I restart... is that normal? I will take a picture and post it into the Gingerbread review forum if I can capture it.)
i was in a similar boat as you, loading 2.3 was no problem but going back is a pain in the ass.
BE WARNED! I spent nearly a day and i know a fair amount about what im doing, i even had to make the USB jig to force download mode at one point (testing different ideas) so be prepared for some issues.
what i did was use odin to flash stock JL2 (9000M bell version here), with 512 pit and a CSC file from another build (sorry i forget), bootloader update repartition clear efs checked. Thats the ONLY thing i could find to get me back to stock without any internal SD error messages.
IF YOU FLASH THE WRONG THING OR THE FLASHING PROCESS SCREWS UP YOU CAN BRICK YOUR PHONE. Read twice, do once.
See if you can find a stock rom for your area, what your phone came with, with the proper pit file and csc file.
Best of luck, you are not alone. I will definately be waiting for a less buggy leak before i switch back to gingerbread.
Kies reads and looks for the correct software for your product code and firmware tied to the supplying network .Once you install different roms you may change those details and Kies cannot find the correct details on your phone to recognise and match it to a firmware .
Spoof product keys and Kies registry patcher posts may help .
jje
Thanks for the quick answers guys... I shall plug-and-chug a bit more tonight and see if I cannot get something to work... then I will be back to post of my success (or failure).
You can use SpoofFw to trick Kies think you are on an official fw, the let Kies do the stock upgrade for you.
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Wirebrook. I already replied to one of these today. Same happened to me. flashed back to jpu with a view to using kies to upgrade me to jpy but it wouldn't. So flashed eclair jm1 and kies upgraded me to jpy so I suggest that. You'll have to flash bootloader afterwards though as you'll lose 3 button reboot. But don't panic
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 rooted, ADW launcher + gingerbread theme
I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Its not an official rom its a Samsung stock rom not the rom that was supplied with your phone . Kies might update it or might not .
You have firmware provided by the original phone seller and product codes hardware id firmware id for that . Kies will see that and update .
But its going to show not the firmware supplied by the original phone seller and tied to product code etc . Then requires you to Spoof Kies for an update .
jje
@Mossy1963
I'll give it a shot this evening... I have the JM1 firmware glaring at me in the face on my desktop right now, though... not sure that worked right the first time.
@JJEgan
As long as it is all "stock" I am pretty much fine with it at the moment. Not too bothered with having it tied to it's specific product code so much, although that would be nice.
wirebook said:
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has mys product code become screwed up?
Click to expand...
Click to collapse
That error message its actually wrong, you get it because nv_data.bin could not be found in /efs folder.
This could be due to a faulty flash where Csc was not applied correctly in recovery on the first boot.
Reflash with Odin is the solution.
Sent from my GT-I9000 using XDA Premium App
@Mossy1963
No cigar whatsoever... Kies simply stated there was no update to be done. Oh well.
@LuffarJoh
Tried reflashing... didn't work either.
Aaaaand to make things weird, that sometimes-working Antenna suddenly started working with an Eclair ROM that it hadn't worked before. Then after a reboot... nothing anymore. And now I have flashed the thing back to Gingerbread and what do you know... no more antenna. I would much rather have a working phone as opposed to a "perfect-stock" phone, so it looks like I might have to get an exchange... and perhaps acquire what I was after in the first place at the beginning of this thread anyways.
Hi, I was wondering exactly the same thing after flashing 2.3.3 today. I just like the idea of being able to plug the phone into kies to get a proper release although, I've no doubt the exact same version will be available for download. Has anyone got any useful info ?
Related
Hi all,
When I bought my phone it shipped with I9000XWJFB/I9000OXXJF5/I9000XXJF5/I9000XWJF5.
Shortly after I flashed to I9000XWJM2/I9000OXXJM1/I9000XXJM1/I9000XWJM2, through Kies with Test Mode On.
When the JPC firmware came out, I flashed it onto my phone using Kies (with the registry fix and Test Mode On).
I later found out it was causing problems with the SalesCode (ie. nv_data.bin/md5),
so I deleted mv_data.bin/md5 and eventually restored to JM7 (using ODIN)
and was back to the original SalesCode and seemingly had everything back.
Now, out of curiosity I wanted to see if I could make Kies flash JM1/JM2 back as it did previously,
but I've found that no matter what I do to the registry, Kies will always tell me: This device's version cannot be updated.
Is there something I'm missing, or will Kies simply no longer function after I flashed JPC,
even though I reverted, restoring my old nv_data.bin/md5 in the process.
Motjida said:
Hi all,
When I bought my phone it shipped with I9000XWJFB/I9000OXXJF5/I9000XXJF5/I9000XWJF5.
Shortly after I flashed to I9000XWJM2/I9000OXXJM1/I9000XXJM1/I9000XWJM2, through Kies with Test Mode On.
When the JPC firmware came out, I flashed it onto my phone using Kies (with the registry fix and Test Mode On).
I later found out it was causing problems with the SalesCode (ie. nv_data.bin/md5),
so I deleted mv_data.bin/md5 and eventually restored to JM7 (using ODIN)
and was back to the original SalesCode and seemingly had everything back.
Now, out of curiosity I wanted to see if I could make Kies flash JM1/JM2 back as it did previously,
but I've found that no matter what I do to the registry, Kies will always tell me: This device's version cannot be updated.
Is there something I'm missing, or will Kies simply no longer function after I flashed JPC,
even though I reverted, restoring my old nv_data.bin/md5 in the process.
Click to expand...
Click to collapse
Samsung seems to have removed all firmwares that were available in test mode. As far as I know the only working codes are those that have been officially released.
Sent using my personal Dis-organizer GT-I9000
mickeko said:
Samsung seems to have removed all firmwares that were available in test mode. As far as I know the only working codes are those that have been officially released.
Sent using my personal Dis-organizer GT-I9000
Click to expand...
Click to collapse
I hope you're right
Though I've seen plenty of posts suggesting JM1/JM2 was still available, i dunno.
Yeah, the engineering mode is now disabled on Kies.
I think it has something to do with the fact that thousands of request were made in engineering mode during one day.... The script on Samsung update server has been modified to reject proto requests and only show official updates.
Hey guys.
I know this has probably been asked/answered a million times before, but hopefully you can understand me wanting a final confirmation before i risk my £500 phone...I have done a lot of reading around this subject, and and *think* i have my head around the most of it now.
Sorry for the block of text, I have put my actual questions in blue to make them a little easier to spot.
So I have the 16GB Galaxy S from Vodafone UK. It is currently completely stock (not even rooted), and is running the JF3 firmware. The details of the phone are:
PDA: I9000XXJF3
Phone: I9000XXJF3
CSC: I9000VODJE4
The phone is unbranded, and will accept an o2 SIM, so I assume it is SIM unlocked.
I am wanting to try out Froyo on my device, and think the JM8 build is going to be the most appropriate.
Do I need to root/backup anything on my phone first? (I am fine with losing apps etc, and would rather reinstall from scratch anyway).
I have signed up to SamFirmwares, and have downloaded the file GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM, which I believe is the right firmware for my phone and region. I have also downloaded the s1_odin_20100512.pit file, which i *think* is the right one.
I also got the CSC_I9000OXAJM1.tar.md5 file which i think should be the right one. I also have Odin3 v1.3.
Can someone please just confirm these are the correct files for me?
So, all I need to do is:
- Start ODIN.
- Put my phone into download mode.
- Select the Re-Partition box, and make sure Auto Reboot and F. Reset Time are checked.
-Select the CODE file in the PDA box, and the Modem file in the PHONE box.
- Put the CSC_I9000OXAJM1.tar.md5 in the CSC box.
- Press Start.
Am I right to think my phone will now flash?
What are the likely-hood of me bricking/destroying my phone if I follow this procedure?
Again, I'm sorry that you have probably answered these questions a hundred times before, but hopefully you can understand why I want to be sure I'm doing this right .
Before you do anything please check if you CAN access download mode. If you can then its all GOOD! you are spot on and I congrats you on doing your research as many don't. Also PLEASE don't install the Froyo Betas as you can see for yourself (JPH/JP3) that theres ALOT of problems on it especially if you don't know much about flashing. Just wait another week or less for OFFICIAL FROYO as if something does go wrong we can actually get support from Samsung as its OFFICIAL.
Also NO you do not need to root your phone. You can do that if you choose to afterwards with a rom update/custom mod. Or just download the samsung root app from market rooting is very painless.
JM8 is NOT froyo.. It's eclair... (JP# is the currently designated Froyo series, but I suspect the designators may change after it becomes stable to the per-month thing)...
Honestly, at this point of time though, it isn't worth it. Samsung seems to have backported the highmem patch to eclair anyway, and Froyo isn't yet stable. Furthermore, there are reports of people's imei getting corrupted (which is fine if you back up /efs maybe, but it still isn't a safe operation).
Honestly, unless you have a need for the new API's, just wait until it's released (it's expected by the end of the month). And then, to be uber safe, use kies to upgrade.
Although, at this point of time, you should probably upgrade your firmware to a newer version of eclair anyway (using kies), because JF3 is ancient, and plenty of problems were fixed in August.
Thanks for the advice guys. I thought JM8 was a Froyo release. After researching more tonight, it seems the JP releases are less than stable at the minute, so i'll stay away from them and wait for the official release.
I updated my firmware via Kies this morning, and am now running:
PDA: I9000BUJM4
Phone: I9000BUJM3
CSC: I9000GVODJM3
The system seems to be running pretty much the same as before. There is no lag etc and it all runs smooth enough.
The only problem I have is that the software updated has now filled my phone with Vodafone branding. It has the Vodafone start screen, and loads of crappy Voda apps on it.
Is there a way I can remove these? or at least make sure I get a "clean" upgrade with the next software update (would removing the SIM before updating work?
You COULD root your phone and use Titanium Backup to remove the apps you don't want. But in all honesty I say get the latest official rom that your provider has. Be it the old JF3 as when Froyo comes out and you do (fingers cross) get a problem you can get actual support. This moment in time I would recommend you do nothing but go back to JF3 and wait for Froyo. But its your device so upto you
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.
so i flashed back to stock to see if it would work.. i dont know curiosity killed the cat right. anyway i then checked to see if mini kies would work and upgrade to 2.2 again just to see if it would not like i need it, many custom roms for cappy that are way better than stock 2.2. i was only checking to see.
so like i said it says unregistered device and wont let me upgrade dont know if the 2 are related or not.
anyone have a guess? also there was a mini kies update may have done something to also i checked and my IMEI is still the same number it matches the # on the box it came in.
Which version of GB did you have loaded?
You can always try the regular Kies version as GB is for I9000, see if that registers.
ok so update to anyone interested.
i relfashed back to 2.1 aka jf6. few days later.
tried mini kies again and worked just fine. must have been server connection problem on samsungs part, big suprise there. lol
so now fone is 2.2 samsung stock firmware.
i know it sucks i was only curious to make sure my fone could still odin 1click since my fone 1010 build. i never had problems using one click before so i hoped it would be no problems. never needed to add 3button combo fix my fone always had it, it is a refurb and always have had good refurbs, i think they need to be judged at a higher passing than brand new anyway, i digress.
after flashing and reflashing many GB roms, flashing back to stock jf6, absolutley no flaws or errors in fone can still use mini kies if want to, fone is as stock as the day i got it. so GB flash your asses off, just be smart and dont forget your steps. have fun and read reread your GB install steps very carefully.
I know this was resolved, but I had a similar issue and it never corrected itself. I found the problem to be that my product code was changed by one of the roms I had previously installed. I followed the instructions in the link below and it allowed me to set my product code to what it was from the factory. I can now update through Kies Mini without getting the "unregistered device" error.
http://forum.xda-developers.com/showthread.php?t=880223
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.