I recently bricked my phone by installing 2.2.1 over 2.2.1 + Voodoo lagfix, ie, I didn't uninstall voodoo before flashing 2.2.1 stock again. I got around it by using a JM8 pda + JM4 modem and a 512 pit repartition, then going up to 2.2.1 again using just a PDA with no pit/repartition.
I was just wondering, since I didn't technically remove the EXT4 file system by uninstalling voodoo, how did the system get converted back to RFS (or did it...)? Basically I'm asking about the relationship between the PIT repartition and the file format the phone uses (does repartitioning ALSO reformat the internal SD)?
My quadrant score is around 1100-1200 running stock 2.2.1 JPY, so I know the system is back to RFS (as opposed to the 1800 with EXT4), but will there be any little 'gremlins' so to speak in the future? Phone is working fine as it now.
Any replies would be appreciated!
Thanks
When you use PIT file, it removes any modified file systems, its essential to remove lag-fix before flashing, but sometimes we forget... luckily its not the end of the world.. a few flashes with different firmwares and all is back to normal...
its just a pain in the arse having to do all that so that's why we remove lag-fix first...
but it doesn't affect the internal sd card.. so you shouldn't get any further issues..
Thanks
I was reading up on some other thread, and that's exactly what I thought the PIT file does. I was just confused because normally when you re-partition something it doesn't automatically format in PC's, but apparently Samsung is nice enough for the PIT's to partition + format for you.
I tried reflashing 512 pit repartition + 2.2.1 at first and that didn't work... Now I'm wondering why rolling back to JM8 with repartition THEN to 2.2.1 without repart worked if they use the same PIT In my mind repartition would simply wipe the file system and set up the partition for the OS/kernels and 2.2.1 would slot in nicely... Apparently not.
Funnily enough bricking my phone doesn't scare me, but not understanding what the hell is going make me wants to cry though. I actually locked my usb cable inside the product box until the next XEU update comes out, haha. Phone reception is just as crap with the JPY version vs the old VAUJP4 (vodafone australia froyo) but loading apps, contacts, etc seems much faster.
On a tangent I went to get my contacts off an old inactive 3 SIM, and noticed I was getting like 4-5 bars (around -80dbm signal) with HSDPA as the mobile network type (emergency calls only). With the default vodafone sim the network type switches to UMTS with something like -105dbm with about 0-2 bars normally. I don't use data on my plan (it's like 100mb... don't wanna incur ridiculous charges if I go over), and the voice quality doesn't seem so bad... but is there any way to get better reception, ie switch networks. Kind of clueless about this stuff as my old k800i had 5 bars all the time!
i am with vodafone UK and i have terrible 3G signal.. i only use GSM now and i always have full signal, and data connection (2G) isnt super fast but it works everywhere. Perhaps you could try it
and as for rolling back to JM8 firmware, JM8 includes 'dbdata' which is what gets corrupted alot when flashing all the time, causing errors and boot loops, thats why so many people recommend it.
but you can go direct to the latest 2.2.1 from JM8, so its not too bad i have bricked my phone many times in the past fortnight, but thanks to XDA im still up and running
I did a little digging again and turned up the same conclusions about the dbdata file. Apparently all the froyo versions don't have this dbdata.rfs file (that JM8 does), so when I repartition straight to a 2.2.1 rom everything was deleted from the repartitioning and is copied without the dbdata file, bricking itself.
But if I go from JM8 > JPY without repartition, I'm assuming all the OS/kernel/modem crap from the JM8 is overwritten with the new JPY files, but the other required systems are left alone. I guess Samsung only updates/creates the files they need too... I'm assuming all the 'sensitive' folders in root like /efs (where your IMEI is) are left alone by the reformat/lagfix? I still have my original one so it seems as if this is the case. I've read about some 'leaked' ROM's that actually change your IMEI number, and I guess they just over-write this folder when they are flashed, instead of leaving it alone.
Makes me wonder how they actually get stock 2.2 firmware on the phones in the first place. They probably use some JTAG system to do it en-masse, but it doesn't change the fact that they have to add random files in order to get it to work or actually have to do it 2xfold. Why couldn't they just include all required files in official roms, regardless of if it isn't updated, rather than making it like assembling a file system jigsaw puzzle.
If we ever get gingerbread, I bet there's probably some file/directory that 2.2 introduced/took out/changed and I'll have to flash my phone 3 times from 2.1 > 2.2 > 2.3!
The feeling of understanding the how/why's of unbricking is actually the same level of relief I felt when unbricking my phone... I'm happy with performance for now, the stress of this is too much to continue messing about with ODIN and ROM's. I think I'll stick with Kies and stock XEU firmware for now (doubt I'd bother with any local australian roms, all are branded bloatware, and XEU gets updates faster!). Kind of freaked out about the IMEI changing thing after some forum searches now (given that I don't wanna mess with odin to root my phone and back up my IMEI file, I might break it again, haha!) so I think I'm done with flashing. However...I have this urge to fiddle with my phone even though it works perfectly fine (and stresses me out unbelievably waiting to see if it works) and I'll probably do something worse this time... I want a totally unbrickable droid to fiddle with, haha. The open-source thing with android is nice and all, but with PC's you usually don't take a trip to the service center and incur a $10-300 bill when you **** up a piece of code. Most motherboards have a literal ROM that stores back-up BIOS settings so you can NEVER brick your computer short of ripping the backup BIOS out of it's socket...
I totally need to destroy my USB cable...
IMEI is fixable if it gets corrupted, im sure i seen a thread about in on here, along with a million others lol
I would recommend Odin over Kies anyday Kies is responsible for A LOT of bricked phones, i mean look how many thread there are on ' Help Kies bricked my phone' you dont see as many for 'odin bricked my phone' (unless the user doesnt know how to use')
What ever problems you run into, i guarantee someone has already run in to it, and i bet there is a solution too,,, If your looking for an 'Unbrickable' Droid... its sitting in your pocket !!!
its upto you to give up the whole Hacking + Modifying thing, but me personally,,, Never ever,,, dont give up on your phone.. all it takes is a 10 minute read up and your questions will be answered.
Related
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
[Q] Bell Canada - Froyo Update using Kies Hack
Has anyone successfully upgraded their Bell Galaxy S to Froyo using the Kies registry hack?
If you so, any issues to be worried about?
Id like to know this as well
Here here. Someone please risk blowing up their phone so we can know if its safe to hack our kies in order to get froyo ten minutes before it is officially released
Sent from my GT-I9000M using XDA App
DON'T DO IT.
first boot - fine, a bit laggy. after reboot, FC then now in endless boot cycle. can't even get to download/recovery mode anymore. when i plug it in, it'll show it's charging though (big green battery icon).
hoping i can still send it out for repairs.
Did anyone manage to update from 2.1 to 2.2 using reg hack methods?
I tried 2 different reg configurations but still kies doesnt show any updates. I cant understand how people are lucky or am I the stupid one who cant do this? I ve never seen anyone saying " reg hack doesnt work for me"
Maybe the problem is Canada. Anyone out there who successfully updated in canada?
Another problem is even if I manage to update someday, when the official update comes to canada will I be able to update it through kies, or because my phone has a different region software it won't be possible?
the one that caught me out initially was not changing the model name in the registry to i9000 from i9000m
After changing that...update went perfect
The JP6 update works perfectly from a stock bell 2.1 i9000. Used 512 pit and no re-partition. I didn't lose 850 like I did with previous releases, so I can still text message in my condo
Yup; got it to work also.
I'm on a Bell i9000M that I unlocked and use on the Rogers network.
For this to work, I had to get the the latest version of Kies from samsungapps.com/about/onPc.as and the registry changes I made are as follows:
"Model Name"="GT-I9000"
"SoftwareRevision"="I9000XXJF3/I9000SWC/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEE"
"HIDSWVER"="I9000XXJF3/I9000SWC/I9000XXJF3/I9000XXJF3"
Note that Keys won't let you update unless your battery is at least 50% full.
I ran Quadrant on it and only went up from 850 to 975. Looks like the IO lag still isn't fixed....
Edit: I decided to do a factory reset after this to wipe off the Bell apps and it looks like I lost the 850 Mhz band along with the apps...
please anyone... i just updated my galaxy 19000m using the kies hack, all went well no problems at all. Froyo was working well 850 band still there. Rooted with the SuperOneClick, all seemes fine. Went to bed last night and woke up to my phone beeping at me, i unplugged it and when i woke up it wont turn on just blinks the galaxy s i1900 screen.
3 button doesn't work and i dont know what to do, can't reboot, hook up to pc... I am lost.
Can you get the download mode to work? (Vol. down + power + home key). You may be able to flash bell stock JH2 rom with Odin.
i don't know about any other i9000m users, but i have had nothing but problems with froyo on this phone. works well for a bit, then starts to get corrupted it with FC's and can't mount sd card, blah blah blah. i've flashed jpk and jpm a good 6 times with repart and wiping too.
i personally am waiting on a specific release of froyo for canada.
i know the hardware is different between the international version and ours, so i think that minor difference is causing this "instability."
Weird, I had JP6 running for two days without any issues whatsoever. The phone is fast, even without a lag fix. The GPS now locks within 15 seconds with 5-20m accuracy. Everything seems to just "work" better.
What i did (in order)
1) reformatted my SD card
2)Cleared Cache and data using recovery options.
3)Reset the system to stock.
4)Flashed JM8 using odin, with repartition and 512 pit
5)flashed jp6 using odin and 803 pit
6) cleared cache and data
7)re-created the APN
I've been mostly using Wifi ever since (im close to my data gap)
Hope it does not turn out badly in the next few hours/days.
At least i have a backup of everything
i had mine for for a week, and i rebooted a bunch of times to install modification and root.
seemed to happen after a reboot.
though i didn't go to jm8 first as everyone else said just flash straight to jpk, so that might have had an impact.
post your results after a few more days and reboots, i'm curious.
yes i can get the download to work, tried with odin3 android + slp with orig JH2.zip and 512.pit it reads.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
i have no idea what to do next.
I got it from wireless wave less then a month ago but i doubt they will take it back
Wow, literally 5 minutes after i said i did not have problems, my phone got force closes and does not start anymore. Very Weird.
I guess ill go back to jm2 for the time being
To all..... Yup i Bricked it.. im not too sure how. Anyhow I got it 26 days ago at wireless wave, I just brought it in and they just looked at it said it was strange and gave me a new one... THANK GOD!!
For me im going to hold off till the update comes out for Canada before i flash anything, I'm just too noob I guess, and don't need a paper weght
Bricked mine too it seems. Well all points to the internal SD card being corrupted or something. Argh. And i had it for 2 months so ill have to send it back for repairs. Hopefully they wont be some pain in the a$$ and refuse it.
kind of sucks.......i bought this phone with the intention to flash 100 different roms a week, and now were restricted to only canada specific roms or else we run the risk of corrupting the sd card..........all i can says is "pure scam!"
wang1chung said:
kind of sucks.......i bought this phone with the intention to flash 100 different roms a week, and now were restricted to only canada specific roms or else we run the risk of corrupting the sd card..........all i can says is "pure scam!"
Click to expand...
Click to collapse
lol? or are you serious.
pretty serious........maybe i exaggerated "slightly" with 100 roms a week, but the rest is true......nothing but problems flashing any other rom except the canadian specific ones. the fact that (according to the poll) there is more than a 20% failure rate of the sd cards for no reason doesn't help either. the fact that most i9000m users that have ran froyo have had issues (myself included). i totally regret buying the canadian version of this phone as i have to baby it for fear of it self-bricking. why would i joke about buying something that i can't use to it's potential? doesn't that piss you off? i could punch a nunn right now.........ok, once again, slight exaggeration.
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 ?
Hello XDA!
So, ive been in contact with someone who downloaded a galaxy S carrier froyo file i was able to nab whilst KIES was busy updating my phone and wasn't looking.
Seems that his phone may be bricked and i'd like to find out if it is and importantly, why.
So, the details are as such:
This telstra SGS was rooted and running darky's. Somehow this setup got messed up. Dont know, was never told.
Download mode was available via a jig, so my supplied files were added to odin. I currently do not know what was selected beyond PDA> telsgsfroyo.tar.md5 (think thats what i called it). As an aside, i flashed this file onto my own phone and had no issues. Also, this
So, i am told that after the flash, recovery ran its usual post odin flash commentary. the phone stayed on the S bootscreen for 5 minutes before the phone went blank. It has not responded to the power button or jig since.
Normally i would say just try 3BR/3BD as the telstra SGS has these in full working order. Also, the froyo and eclair ROMs available for my carrier are not complete firmwares, neglecting dbdata.rfs, boot.bin and sbl.bin (was under the impression the last two being neglected = good?) with a known workaround to deal with the lack of dbdata.rfs in our firmwares.
Unfortunately, and also not yet explained to me, the JIG is being used as both 3 button modes stopped working for him.
So, tldr version:
Can the phone be saved without taking it in for repair?
Was this just an odin hiccup, something ticked that shouldn't have been in odin or are the files i supplied bad. I was a little quick to remove the files from my megaupload account so ill edit this post when the reupload is done. joys of dsl and all
edit: file is on megaupload, /?d=Q9L4YYND
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.