Related
Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.
Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Isn't there a way to try and access internal sd card?
Have you try doing a factory reset?
Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/
terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App
Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
This has happened to me, I just flashed with an older version, for me JM5 worked fine.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App
I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)
worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...
I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.
...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."
yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje
cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing
http://forum.xda-developers.com/showthread.php?t=819551
jje
Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.
http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje
Sent from my HTC Wildfire using XDA App-if you can please post me back as my sgs went from being bricked to working again then just crazy .....
I have no clue how to help you.
The amount of information provided by you just overwhelms me.
But i have an idea, give me a second.
*gets magic 8ball*
*shakes it*
Try using it in a room that faces north.
Okay ; you've got a sense of humour,but posted another as I realised how limited in dialogue that first one was,thing is I have no experience of flashing + such + my sgs bricked I had to get a jig as my galaxy was shipped without the 3 button method,I tried to flash using odin but due to my basically non existent knowledge I never done it correctly obviously + the phone I previously had was now not registering on any network,it was as if it was locked or something so I downloaded dagentooboy's app (samsung galaxy s unlock) but even that app asked me if I had an sgs,I then tried Rom. Manager,things like that but nothing could recognise my device , this is basically my problem , I formatted my internal + external memory (8gb + 16gb) I think maybe I shouldn't have? My reason for formatting both was due to me not knowing how my sgs had bricked in the 1st place,all I ask for is some advice here hope you can help out? If you can it would be most appreciated,like I say I am a total noob,regards.....
Sent from my HTC Wildfire using XDA App
You are not the first one to semi-brick your sgs, the key is usually to get it into download mode.
Then use odin to flash a stock rom.
So i think you know how to get into download mode, and you already have odin installed.
It can be all found through search or just browing the stickies .
Taking a quick look i found this:
http://forum.xda-developers.com/showthread.php?t=846913
Grab a rom that seems suitable, no idea where you are from, you didn't say.
Flash hit with odin, there even a picture at the bottom of that post where to put what file.
I'm gonna go sleep now, try that and post results.
Thanks , forgot to say I'm from u.k.(scotland),will try as you say tomorrow,MUCH APPRECIATED.....
Sent from my HTC Wildfire using XDA App
I already read all kinds of guides to unbrick the Galaxy S but none of them worked.
First, the patient:
Samsung Galaxy S International Version, factory free. Froyo 2.2.1 (I don't know if it is related with this problem, but 2 or 3 weeks ago I updated from Froyo 2.2 to 2.2.1)
Now the symptoms:
Two days ago, several settings changed to default, and even though it looked weird I didn't worry.
Yesterday, when I went into the Android Market web, a message appeared, saying that I didn't have any phone registered in my account. I thought it was a phone problem (and boy, it was!) so I restarted it. It didn't. It shows the Samsung logo with the model, then the Galaxy S animation and that's it! a minute later the screen goes black and vibrates randomly, every 2 minutes or so.
The 'treatment':
I already had a problem like this in the past, but then it was really my fault. After desperately looking for the solution, I managed to do a hard reset by using the 'adb reboot recovery' command, because the 3 button combo didn't work. This time I used the combo, just in case, and it worked! but before showing me the recovery options some weird message about installing some csc stuff appeared. When the recovery menu appeared, I thought that the phone was OK, so I rebooted it without doing anything else (I should have done the factory reset, right!? but I didn't want to lose anything :S). Big mistake: the problem continues, and now the 3 button combo doesn't work!
The 'adb reboot recovery' command doesn't work either. When I use it, this message appears:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I have already done *almost* everything I found in the forums. The only thing I haven't tried is the USB jig method.
I should mention that I've never used Odin, or downloaded a custom ROM or anything like that. When I had Froyo 2.2 I rooted the phone but with the update it was gone. And that's it! no lagfixes, no custom ROMs, no nothing!
Can somebody help me?
PD: Sorry for my English, I am Peruvian .
I suggest that you flash back to stock Froyo 2.2 via Odin with pit 512 and repartition checked .
jje
How can I do it if my computer can't find my phone? Can Odin find it?
ultrachilled said:
How can I do it if my computer can't find my phone? Can Odin find it?
Click to expand...
Click to collapse
Sorry missed out use the USB jig .
jje
Does it really work?
Is it the only thing to do?
Besides, I have no electronic skills...
ultrachilled said:
I already read all kinds of guides to unbrick the Galaxy S but none of them worked.
First, the patient:
Samsung Galaxy S International Version, factory free. Froyo 2.2.1 (I don't know if it is related with this problem, but 2 or 3 weeks ago I updated from Froyo 2.2 to 2.2.1)
Now the symptoms:
Two days ago, several settings changed to default, and even though it looked weird I didn't worry.
Yesterday, when I went into the Android Market web, a message appeared, saying that I didn't have any phone registered in my account. I thought it was a phone problem (and boy, it was!) so I restarted it. It didn't. It shows the Samsung logo with the model, then the Galaxy S animation and that's it! a minute later the screen goes black and vibrates randomly, every 2 minutes or so.
The 'treatment':
I already had a problem like this in the past, but then it was really my fault. After desperately looking for the solution, I managed to do a hard reset by using the 'adb reboot recovery' command, because the 3 button combo didn't work. This time I used the combo, just in case, and it worked! but before showing me the recovery options some weird message about installing some csc stuff appeared. When the recovery menu appeared, I thought that the phone was OK, so I rebooted it without doing anything else (I should have done the factory reset, right!? but I didn't want to lose anything :S). Big mistake: the problem continues, and now the 3 button combo doesn't work!
The 'adb reboot recovery' command doesn't work either. When I use it, this message appears:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I have already done *almost* everything I found in the forums. The only thing I haven't tried is the USB jig method.
I should mention that I've never used Odin, or downloaded a custom ROM or anything like that. When I had Froyo 2.2 I rooted the phone but with the update it was gone. And that's it! no lagfixes, no custom ROMs, no nothing!
Can somebody help me?
PD: Sorry for my English, I am Peruvian .
Click to expand...
Click to collapse
Had a similar problem with mine, went from 2.1 to 2.2 on a factory unlocked phone and wound up in the same position you are in, first the pics in gallery started doubling up, then problem with market. 3 button combo no longer worked. Was pretty new to xda and sgs so didn't try adb. What I did do was bring it to my local vodafone shop, and even though it wasn't bought from them, they sent it off. Got it back within 4 days, free of charge, and the maintenance report stated that they had replaced a faulty display module, and upgraded it to 2.2.1, which wasn't available here at the time. (Doesn't make sense to me, but it must have been a hardware fail of some sort) but it got fixed, fast and for free.
ultrachilled said:
Does it really work?
Is it the only thing to do?
Besides, I have no electronic skills...
Click to expand...
Click to collapse
Yes it works, I used it. Now I have stashed my home made electric component at a very safe place as I know while working with hacks I am going to need it again.
You literally don't need much electronic skills. What you need is a Micro USB cable (buy the cheapest one that u can find if u have to buy).
Buy a 301K resistor (if not available then get as many to bring total to 301k, I bought 3 300K and 1 1K to make a total to 301K).
There are tutorials with pictures on this site, search and u will find them.
One last thing don't worry at all up to this moment your phone is fine. Once you have your JIG ready, post a message or I am sure some one will guide you through or PM me I most certainly will as I know exactly how frustrated you might be right now.
Cheers
Try to go to download mode (volume down+home+power) if you can do that, send me a private message and i will explain you about odin.
Something more: what is USB jig?
Espera. ¿he leido que eres peruano? ¿k c*j*n*s hago diciendotelo en ingles?
DMD9 said:
Had a similar problem with mine, went from 1.6 to 2.2 on a factory unlocked phone and wound up in the same position you are in, first the pics in gallery started doubling up, then problem with market. 3 button combo no longer worked. Was pretty new to xda and sgs so didn't try adb. What I did do was bring it to my local vodafone shop, and even though it wasn't bought from them, they sent it off. Got it back within 4 days, free of charge, and the maintenance report stated that they had replaced a faulty display module, and upgraded it to 2.2.1, which wasn't available here at the time. (Doesn't make sense to me, but it must have been a hardware fail of some sort) but it got fixed, fast and for free.
Click to expand...
Click to collapse
A friend of mine bought this phone for me in Spain and sent it to me, and here in Peru only Movistar has this kind of phones. I'll take it to them, but something tells me that their won't be as good as Vodafone's.
Khalid Ali said:
Yes it works, I used it. Now I have stashed my home made electric component at a very safe place as I know while working with hacks I am going to need it again.
You literally don't need much electronic skills. What you need is a Micro USB cable (buy the cheapest one that u can find if u have to buy).
Buy a 301K resistor (if not available then get as many to bring total to 301k, I bought 3 300K and 1 1K to make a total to 301K).
There are tutorials with pictures on this site, search and u will find them.
One last thing don't worry at all up to this moment your phone is fine. Once you have your JIG ready, post a message or I am sure some one will guide you through or PM me I most certainly will as I know exactly how frustrated you might be right now.
Cheers
Click to expand...
Click to collapse
Thankfully, the only thing I am sure is that my phone is fine... It's very hard for a Galaxy S to completely go FUBAR (unbrickable, I heard). But I'm really frustrated, not only with this problem, but with the RFS lag. I watch some friends' android phones (LG Optimus One, for example) go really smoothly while mine sometimes goes choppy, and it makes me envious Actually, the first time I f*cked with my phone was when I tried to use OCLF. The only thing left was to resign myself.
I expect to make my jig tomorrow, even though I have a very unsteady hand
miguelici said:
Try to go to download mode (volume down+home+power) if you can do that, send me a private message and i will explain you about odin.
Something more: what is USB jig?
Espera. ¿he leido que eres peruano? ¿k c*j*n*s hago diciendotelo en ingles?
Click to expand...
Click to collapse
I tried to get the phone in download mode and recovery mode with the 3 button combo, and nothing happened. As I wrote before, I could get the phone in recovery mode once, but now I can't. I should have done the hard reset then, damn it!
And about Odin, I heard that I can brick my phone with it if I do something wrong, so I never used it (I don't want an expensive paperweight ).
About your question, a USB jig is a 'device' (so to speak) that one can manually make with a mini USB connector and a 301k resistor, as you can see in a previous comment. It's supposed to make the SGS go into download mode when you connect it to the phone.
Acerca de escribir las cosas en ingles, pues creo que asi nos entiende mas gente, jejeje.
PD: Is it true that flashing a ROM, even a stock one (stock froyo, for example), voids the warranty?
Khalid Ali said:
Yes it works, I used it. Now I have stashed my home made electric component at a very safe place as I know while working with hacks I am going to need it again.
You literally don't need much electronic skills. What you need is a Micro USB cable (buy the cheapest one that u can find if u have to buy).
Buy a 301K resistor (if not available then get as many to bring total to 301k, I bought 3 300K and 1 1K to make a total to 301K).
There are tutorials with pictures on this site, search and u will find them.
One last thing don't worry at all up to this moment your phone is fine. Once you have your JIG ready, post a message or I am sure some one will guide you through or PM me I most certainly will as I know exactly how frustrated you might be right now.
Cheers
Click to expand...
Click to collapse
Let's say I use the jig. What should I do after that? right now my PC doesn't recognize my phone, it says there's no phone connected :S. When I get it in download mode, will my PC be able to recognize it?
Yes it should as I had the similar issue, Get the JIG working (when JIG works, ur phone will be in download mode) then using odin load the stock rom on your phone, first time after the load of ROM it will take several minutes to reboot so dont panic.
If you dont want to loose much of your data then make sure you DON'T click on repartition check box.
Send me a pm once u have jig working
Khalid Ali said:
Yes it should as I had the similar issue, Get the JIG working (when JIG works, ur phone will be in download mode) then using odin load the stock rom on your phone, first time after the load of ROM it will take several minutes to reboot so dont panic.
If you dont want to loose much of your data then make sure you DON'T click on repartition check box.
Send me a pm once u have jig working
Click to expand...
Click to collapse
Tonight I'm going to try the jig. Now, I remember the USB debugging isn't enabled. It isn't a problem, is it?
nope. Do follow the instructions (you should be able to find that on xda dev site) on how to use JIG to get into download mode though.
OK I managed to get it into download mode. Now what?
flash a 3 file firmware, with 512 pit and re-partition
then flash this on top http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
boot into recovery and do a factory reset.
then move onto what ever rom you want
I think your best bet would be trying to flash using EZBase to 2.2.
http://forum.xda-developers.com/showthread.php?t=991792&highlight=ezbase
Very user friendly instructions, meant for recovery purposes. After we get the phone booting and working again we can worry about trying a new ROM or Gingerbread.
I will continue the story where I left it.
I took the phone to customer service, and they managed to install an incorrect ROM, (my phone is I9000, they put a ROM for the I9000B) and they send it back to me, saying that my phone couldn't boot, so it should be a BIOS error. At least it goes into download mode. I want to flash stock Froyo 2.2 or 2.2.1. I have no idea how to do it, so please be very simple in your responses :$
PD: Once I get my phone working I'd like to try some other ROMs, I am really tired of the lag.
http://forum.xda-developers.com/showthread.php?t=939752
jje
What are the advantages of repartition?
re partitioning, repartitions the file system, along with flashing a new ROM with all 3 files, this restores the phone to a 'new like' state, as if it was out the box.
its also the best way to unbrick devices too !! i re-partition mine every couple of weeks. but i am a constant flasher
Hey there, i am feeling somewhat overwhelmed with all of the advice going on out there and need someone who can give me the answer to my specific problem hardware wise without breaking a sweat...
I flashed a froyo 2.2 rom onto my phone a while ago, recently all of my apps stopped working, and i could no longer install any apps.
Couple days ago i tried openning gmail and the screen went black and gave me the bzzzzzz...............................bzzz...bzzz...
vibrating error that you usually get when an app crashes.
Now the phone continues doing that even when booted up and stuff
It starts right after the S screen and repeats until the battery is removed.
My phone can't get into download or reset mode using the 3 button method so i bought a jig off of ebay, works like a charm.
however NOW, i cannot get the computer to see the phone; both when it is on and attached and in download mode and attached. Odin can't see it, neither can Kies.
If i can get either to see it, i can look up the flashing process to make sure everything is right.... but as of yet nothing i am doing is making a difference.
Thanks for any help
Ok, I'd focus on odin so disable Kies (in task manager processes - all the kies processes).
Then I would 1) reinstall the drivers (standalone ones) 2) Have a few versions of odin to try (like 1.3, 1.7 and ez odin) 3) Clean your usb port on the phone (and computer maybe too - whats the harm?).
Usually if you are sure the drivers are Ok then you should be able to odin working with a nice clean port. They are more sensitive to dirt/moisture or whatever than they should be.
Try that and let us know...
BTW Some people think that the order is important but I've never noticed that. I always have odin open and then connect it but cant hurt to try the other way around too.
Hey thanks alot,
I am at work right now but i am optimistic about trying that out lol.
Just so i know for when the time comes and if Odin works, what files do i need to flash it? .pit, .tar and anything else specific for Bell Canada?
I only ask because you are with Bell so it is probably a very simple answer for you. Otherwise I am sure i can find it elsewhere.
Thanks,
I'll keep you updated
Josh
Download the complete jl2 rom from link I posted yesterday (search my posts) with repartition ticked, then flash the kc1 rom from stock rom link on xda or at samfirmware.com and flash without repartition if you want the latest. You could just try the kc1 step but I you need to repartition.
Sent from my GT-I9000M using XDA Premium App
Hey man,
my phone has never been sent in for repairs or replaced...
I was reading one of your other posts and you advised another member to send it in and maybe they will replace/update hardware?
I have still had my phone for less than a year so sending it in will be no problem at all...
Should i flash to the latest myself or return to stock and send it in?
I really appreciate your help.
Thanks
Well he knows his is broken as he can see that his internal memory reads 0 (which means its cooked - ask me how I know...) and he was trying to fix it in a round about way. Or there was the guy who flashed a captivate rom - that was just a big no-no.
You might just have a corrupt partition or some other corruption in the file system. I seem to get that all the time and its a pain but very fixable .
Alright, sooo
-uninstall Kies
-install drivers only
-try to connect to Odin
-If succesful flash with Odin
-dance with joy
Got it, I will update you later when i get home.
Thanks
installed drivers on my work computer (32 bit windows xp) and nothing... I've tried phone off, phone on, phone in d/l mode... It doesn't pick up anything...
I can try it on my Windows 7 comp at home and see if that works but i'm wondering what the worst case scenario is just bringing into Bell and having them fix it... Am i looking at charges, warranty voiding, etc.. etc... to have it fixed or could i BS my way out of it?
Fuuuuuuuuuuuuuuuuuu
pretty sure i flashed the wrong firmware on my phone, when it boots up it says GT-I9000 not GT-I9000M.
It worked fine for like 6 months so i never questioned it... damn damn damn
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
I9000 firmware is completely compatible. The text you see is from the kernel which are always for i9000 unless you have one of the three bell firmwares. So that's not the issue.
Sent from my GT-I9000M using XDA Premium App
RogueCow27 said:
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
Click to expand...
Click to collapse
I would keep trying. I have gotten warranty before and I was in the same predicament as you almost except I knew that the internal memory was dead. But that was also around the time when most of the I9000M models were dying. They might be checking more now.
If you get odin to flash a stock rom then you can go for it but by then you should be able to fix it.
Sent from my GT-I9000M using XDA Premium App
Alright i will keep trying.
As far as the firmware goes, my gf and i both have the same phone, but she kept heres official and i put custom roms on mine (just the 2.2 because it wasn't available)
We are both on bell canada so i asked her to boot up her phone and the beginning message on hers says GT-I9000M so it freaked me out lol
I will try on my home computer,
keep your fingers crossed for me
Alright, so Odin can now see my phone (it was the damn cord, my Win 7 comp couldnt see it but my xp work laptop can)
Which firmware would you recomend flashing? Stock gingerbread or a slight variation?
I am at work right now so i can wait a bit for a good response. It'd really help me out if you could provide links and tips to the best firmware out right now (i have no problem flashing a custom ROM if it is good).
Thanks alot,
Josh
Succesfully Flashes Gingerbread 2.3.4
Thanks for all your help!!!
how did you manage to see it in odin?
i have te same problem with restarting just after first screen (after flashing to gingerbread) but i cant see it in odin so i cant flash it again?
when i connect it when turned off, a small icon appears with usb connected sound but its still not visible.
Is it maybe my win7?
help, anyone please
Did you start in Download mod? Did you kill the Kies processes in you Win7 task manager ?
If yes, sometimes Windows takes time to install the drivers (be sure ton be connected to the internet), you should also close and relaunch Odin.
i launched download mode with sdk, and now i cant start it.
i went to another pc with xp. it installs drivers but odin cant recognize it.
Well i did it on my work XP computer becuase WIN 7 wasn't recognizing it. But it turns out the whole time the cable i was using would connect to charge, but not act as a pc connection.