Related
Hi, I've been using Darky's Rom for over a week now and everything was fine. I woke up this morning, and my phone was off. I found this strange because it was left on the night before, and it was completely unresponsive. I pulled the battery and attempted to boot it, but it keeps flashing the GT-i9000M logo and rebooting. I have Download mode working, which is good and I've tried flashing the stock firmware back, and it's not working. I've tried the repartition option with both the 512mb .pit file and the one that came with odin, nothing's working. Anyone have any tips?
Call samsung its toast. Check out some of the i9000m posts in the general forum.
Sent from my GT-I9000M using XDA App
Dang. Is there any chance Bell will be able to replace it for me? I'm guessing my issue is the corrupt internal microsd. Also, since I was a running a custom rom would it be a good idea to flash the bell FroYo through Download Mode before taking it in? Thanks for the response. Also, should I mention to them that I upgraded to FroYo?
As it is you have no warranty as you messed with the firmware so yes be on the safe side and flash to stock bell firmware . You can always act ignorant and say it went bad after the Froyo update .
jje
JJEgan said:
As it is you have no warranty as you messed with the firmware so yes be on the safe side and flash to stock bell firmware . You can always act ignorant and say it went bad after the Froyo update .
jje
Click to expand...
Click to collapse
Alright, that's what I'll do. Thanks for the advice.
As bad as I feel about lying, it's a physical problem with the device and I feel that I deserve a replacement. I didn't really have second thoughts about installing a custom ROM because the Galaxy S is virtually unbrickable thanks to download mode.
edit: Does anyone know where I can find the jk4 froyo that's bricking our phones?
Found it! http://forum.xda-developers.com/showthread.php?t=867309
Hi,
I was playing with ROM flashing and the like and I decided to go back to stock, so I did using the ODIN flash to JF6. However, it seems that I have trouble getting the JF7 update over the air to work. Any ideas?
Thanks
I'm a Noob, but you might try Kies - It should detect a newer version available and let you update that way. Much more reliable in any case if you ask me.
You can do search flashing to stock JH7 that should help you. If no one else has sent you a link by the time I get to my computer I'll send you a link I think it will be flashing 1010 build or something like that.
Sent from my GT-I9000 using XDA App
I've had more problems with kies than anything else, try the samsung website to update.
I see you was wanting JF7, I don't know what the difference is but this will get you back to stock JH7 Eclair.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I tried it, it works.
Well I want JH7, but I also want to be able to get the official Froyo when or if it comes out.
Bunkered said:
Well I want JH7, but I also want to be able to get the official Froyo when or if it comes out.
Click to expand...
Click to collapse
Like stated above.... flash using kies mini.... then you'll be ready for official AT&T froyo.
Alright thanks for all your help, Mini Kies did the trick.
Hey guys, i just screwed up my galaxy s using odin. I was trying to upgrade my firmware from 2.2 to 2.2.1(in fact I recently upgraded from 2.1 to 2.2) when my phone went dead.
Now that i turn it on by holding down vol-up + home + power, all i get is this message:
RST_STAT =0x1
PMIC_IRQ1 =0x3c
PMIC_IRQ2 =0x0
PMIC_IRQ3 =0x0
PMIC_IRQ4 =0x0
PMIC_STATUS1 =0xc0
PMIC_STATUS2 =ox2c
*
I would appreciate your help and time spent in giving me some tips or better yet solutions to solve this issue. Thanks.
More info: Any customization ie. rooted, lagfixed, custom roms?
I used s1_odin_20100512.pit after that my phone turned off giving me the messages i just explained.
Not that familiar with 2.2.1, but I would make the assertion that you should not be using PIT files to ROM flash unless you need to change the partitions. You should be using PDA files. You will probably need to search for the proper PIT and PDA files for stock 2.1 or 2.2 and flash those. Are you able to see the phone via ODIN?
Exactly what kind of phone do you have. Is it a captivate or I9000?
Sent from my SGH-I897 using XDA Premium App
search odin 1 click
and go back to stock
you should still be able to get to DL mode
It doesn't even load on odin nor my computer can recognize the device.
i have a captivate I9000. I think the problem should have caused it that when i started odin i clicked the re-partition box.
capo503 said:
It doesn't even load on odin nor my computer can recognize the device.
i have a captivate I9000. I think the problem should have caused it that when i started odin i clicked the re-partition box.
Click to expand...
Click to collapse
Ok well the captivate is not an i9000 it is an i897, so you are in the wrong place. Also might be why if you used odin files set for the wrong device. I would look into getting a jig.
it is an i897. However, after upgrading to 2.2 and rebooting the phone, i would see a screen saying that it was an i9000. So what you think is that i installed the wrong adin files? great!!
what does a jig would do to my phone?
capo503 said:
it is an i897. However, after upgrading to 2.2 and rebooting the phone, i would see a screen saying that it was an i9000. So what you think is that i installed the wrong adin files? great!!
what does a jig would do to my phone?
Click to expand...
Click to collapse
How did you update to 2.2? if you used the new update you would not have gotten and i9000 screen unless it is a custom rom, A jig will force it into download mode.
If you can get a jig to get you into d/l mode, check out this thread to get you back to normal.
I'm sure you can find some sources for the jig in this thread, but if you prefer to try to make one, yourself, look here.
This may be a handy thread for you, too.
I got the update from Samsung Kies. I got that screen after rooting my phone.
i did three things: update from 2.1 to 2.2, root my phone, and attempted to upgrade to 2.2.1.
The third thing i did messed up my phone.
I will try getting a jig and see what happens. I hope it works fine again.
capo503 said:
I got the update from Samsung Kies. I got that screen after rooting my phone.
i did three things: update from 2.1 to 2.2, root my phone, and attempted to upgrade to 2.2.1.
The third thing i did messed up my phone.
I will try getting a jig and see what happens. I hope it works fine again.
Click to expand...
Click to collapse
Ok if Keis updated your phone to 2.2 with the i9000 screen then you dont have a i897 captivate. you have the i9000. mainly sense there is no keis upgrade for 2.2.1 for the captivate.
I was using odin to update to 2.2.1 and ended up bricking my phone!!
I had to use PDA instead of PIT as you said previously!!
Thanks!! there is also a tuturial about how to do a jig here
http://www.youtube.com/watch?v=Rdn5GoRjhn0
i might follow that one, seems helpful too.
capo503 said:
I was using odin to update to 2.2.1 and ended up bricking my phone!!
I had to use PDA instead of PIT as you said previously!!
Click to expand...
Click to collapse
I personally never said anything about PDA or the PIT file. What carrier are you on? ATT, Rogers?
OOOPS SORRY!! your right it wasn't you. Yes AT&T.
capo503 said:
OOOPS SORRY!! your right it wasn't you. Yes AT&T.
Click to expand...
Click to collapse
Ok then there is no way Keis updated you to the 2.2 with the i9000 screen, that comes from a custom rom. Get a jig and boot into download mode, if all the other methods have failed and flash back to stock with odin. Oh and all the 2.2.1 roms are custom roms normally used with CWM flashes. Might need to do a little be of research and spend a few hours reading up to make sure this doesnt happen again.
Thank you SO MUCH!!! I really appreciate the time you spent helping me.
And yeah i will do that definitely, that's the moral of the story.
Again, THANK YOU!
Ok I was trying to flash new rom...so I flashed to stock...but after the process finished in Odin...and it showed Reset....my phone should have rebooted right? But it didnt reboot...just got dead...I removed everything and tried to start it no use...even used jig...but its no responsive...I am not panicked (as it was my experimentation phone)...but trying to find what to do in that case...battery was full too....
So I accidently bricked a build #1010 phone using oneclick to revert to stock, not realizing it wasn't compatible. I found this today on XDA:
http://forum.xda-developers.com/showthread.php?t=1127249&page=29
My phone currently is build 1009, got it through a warranty exchange, came with froyo pre-installed. Is it compatible or will I brick trying to run? I am also aware of the recovery and the "unsigned packages" thing...do I need to change the recovery first before I run? Thanks
You would brick if you went to 2.1, but that is totally compatible! Have fun and. After flashing that go look for. Stock KH3 and you have to flash KF1 then KH3. Just a min I will link you to everything.
KF1- http://forum.xda-developers.com/showthread.php?t=1127249
KH3 CWM kernel- http://forum.xda-developers.com/showthread.php?t=1242533
Stock KH- http://forum.xda-developers.com/showthread.php?t=1232703
Sent from my SAMSUNG-SGH-I897 using xda premium
Thanks for the quick response! Yes my previous phone was build #1008 and I ran oneclick several times on it with no issues. My wife made a warrenty claim on hers, and I thought i'd be nice and install cog on it, and I couldn't get the recovery to work so without even thinking about it I ran one-click on it, and I bricked it. Honestly I had no idea what build number my phone was back then, but after the brick I found out her new warranty exchanged phone was build #1010
Ever since I've been deathly afraid of running anything with bootloaders. When my speaker died on my original captivate I didn't run one-click, instead i used Odin3 and found a CWM flashable eclair rom, and ran that instead, and then used kies mini to go to froyo. I've had my newer captivate since July, and been running stock since, getting sick of all the issues it has, none of which i noticed in cognition. I actually logged on to get Froyo Cognition, but the links are all broke to it, so I figure I might as well try gingerbread out.
I'm on KH3 stock right now and its great! And it's the GB bootloaders that fix the 3button fix, no need for eclair bootloaders since they are backwards compatible!
Sent from my SAMSUNG-SGH-I897 using xda premium
Wait you hard bricked? with 2.1 stock 1 click? Ive heard of bootloops but never hard bricked.
He soft bricked probably, not lowly to hard brick on a 2.1 flash unless he did the3 button combo fix
Sent from my SAMSUNG-SGH-I897 using xda premium
Well I'm pretty sure it was hardbricked. It wouldn't do anything, no 3 button, no trick anyone suggested to try, it just stayed black and unresponsive. I don't have a jig but that was about the only thing I hadn't tried... So I gave up and made an insurance claim. And to be honest I haven't put a custom rom on since
Sent from my SAMSUNG-SGH-I897 using XDA App
Did anything happend if you pressed power? If it didn't then Odin might have failed while flashing a bootloader....
Nope nothing. Basically half way through it just stopped responding and i eventually gave up and unplugged. It wouldn't do anything. It happened to a friend of mine too but luckily for him when he pushed the power button he got the warning sign on the screen. My phone was completely dead and wouldn't respond at all
Sent from my SAMSUNG-SGH-I897 using XDA App
all you have to do use the odin one click to go back to stock which is jf6 then use odin 3 and you can goto kh3. no other flashes are needed. ive done it this way 10 times and no bricks.
Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
If you have flashed a custom ROM before, it won't work. Just wait on a Odin/Heimdall one click!
Sent from my SGH-I897 using xda premium
aicirt17 said:
Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
Click to expand...
Click to collapse
This worked for me, I tried this morning, I had the same issue while on CM9 ICS.
As mentioned flashing any rom your device's I'd might change. I've never had my imei change but read enough ppl to know it happens.
Sent from my SGH-I897 using Tapatalk
I don't know if this matters, but I've never installed a custom ROM, only a custom modem and kernel. Would that change the IMEI?
Have you messed with unlocking it?
Sent from my ICS powered i897
I'm pretty sure kies mini will detect kernel changes. I had stock froyo with a flashed kernel and it wouldn't let me update. I flashed everything back to stock, but was still rooted, and it still wouldn't let me update. I ended up doing a full flash back to stock kb2 and it finally let me upgrade.
I wonder if I flashed the stock kernel and unrooted if it would have worked. At the time I was too lazy to browse for everything and already had the heimdall package downloaded.
Sent from my SAMSUNG-SGH-I897 using XDA App
If your "About Phone" shows anything other than SGH_I897 kies mini will not recognize your device. I was running andromeda , wouldn't see it so I went back to stock, oneclicked jf6. After that kies immediatley recognized it. I probably didn't have to go back to jf6 but, I had nothing better to do for that next hour. If you do go back to jf6 you will have to kies mini twice to get GB, first time it will install froyo, when it's done close kies, unplug re-open kies, re-plug your phone kies will show update again, click and sit back and wait for it to finish. ...you now have GB.
Thank you all for your help. I finally got it. I ended up RE-flashing back to stock using this method: http://forum.xda-developers.com/showthread.php?t=1300843
Turns out that I did in fact have a custom modem and custom kernel, and when I flashed back to stock the first time (I used Clockwork Recovery), it didn't put back the original modem and kernel, thus making Kies Mini not recognizing my phone. So, after RE-flashing the ORIGINAL OFFICIAL Froy update using the above link, everything went smooth fronm there. Hope this helps somebody.