Database Develop

[Q] HELP!!!! i Just screwed up my galaxy s

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....

HELP ME!!!!!

Hey guys...I need help. I used odin one click to restore back to stock JF6 and tried to use Kies to get to stock 2.2 just b/c I decided I liked stock 2.2. Well, for the first time ever, Kies says "unregistered device", now I have never had this problem. What should I do, to get it to work?
I'm on AT&T. I uninstalled and reinstalled the drivers and kies. I tried reflashing to stock JF6 and Master Clear several times, and I am still getting the same thing.

Use Odin and flash Froyo from Download mode.
http://www.techpetals.com/how-to-in...d-2.2-froyo-for-samsung-captivate-leaked-2295

This is leaked froyo. I want the official build from kies.

Is it possible your nv_data.bin got changed? You might look into that and read up on how to fix it. Just a thought. I think that might have happened if you ever flashed Gingerbread. But I don't remember the exact details, so look into it youself.
Edit: After looking around a little bit, I found that you might try using the Odin 3 one-click tool to do a master clear. Then try kies mini and see what happens. Oh, and did you use kies or kies-mini?

Please use more descriptive thread titles.

Help on analyzing brick

Hey guys I hard bricked my captivate and need help evaluating what I did wrong so I can prevent it from happening in the future. I just received the device in the mail (it was a replacement device) and tried to use odin one click JF6 to flash it to eclair. I've done this process 100's of time with my previous captivate but with my new one I saw that it was hanging at sbl.bin and my device turned off. I unplugged the usb, did a battery pull, and used my jig and the phone went into download. PHEW... Thinking that my JF6 odin was corrupt or something I decided to use Odin One click JI6 and the odin hung again but this time I wasn't so lucky. The phone wasn't showing any thing and the jig was infective. The phone hard bricked. My question is how did I brick it and why did it hang when I tried odin one click,. (Odin one click has always worked flawlessly for me in the past). Also are froyo and eclair bootloaders the same? If were to flash JF6 2.1 eclair using odin3 over Rogers Froyo should that work?l (BTW my device is 10.11 build)
edit: I understand that odin one click always has a risk involved because your flashing boot loaders but I just want to distinguish whether it was just an unlucky odin flash or something to do with the build number. Thanks

thats a good question. As far as I know Froyo and Eclair have the same bootloaders, but as far as the Odin problem- im sorry I have no idea.

A lot of people on here have bricked their captivates by using OneClick Odin. What happened was that your replacement captivate came with stock froyo which does not work with OneClickOdin. You were on the right track by going to stock JF6. Not sure why it failed for you but if you would have tried it again I'm betting money it would have successfully flashed. Sorry to hear about your troubles.

duuhdave said:
A lot of people on here have bricked their captivates by using OneClick Odin. What happened was that your replacement captivate came with stock froyo which does not work with OneClickOdin. You were on the right track by going to stock JF6. Not sure why it failed for you but if you would have tried it again I'm betting money it would have successfully flashed. Sorry to hear about your troubles.
Click to expand...
Click to collapse
Lol.. now I'm even more confused. You start out by saying the reason it wont work is because his phone came with stock froyo...then you finish by saying your on the right track, it should have worked. ..wtf??
Sent from my SGH-I897 using XDA Premium App

Coreym said:
Lol.. now I'm even more confused. You start out by saying the reason it wont work is because his phone came with stock froyo...then you finish by saying your on the right track, it should have worked. ..wtf??
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Yes search for other threads about oneclick NOT being cooperative with newer model captivate sthat came with stock froyo. I said he was on the right track because the correct method to go back to stock is JF6. Which can be found in Icezar1's continuum thread which requires odin 1.3, the pda file, etc. If he would have simply tried the JF6 process again it would have completed rather than using 1 click odin and messing up everything. Read the second post of this thread where ZELENDEL says that newer captivates with froyo don't work with oneclick
http://forum.xda-developers.com/showthread.php?t=1093926

duuhdave said:
Yes search for other threads about oneclick NOT being cooperative with newer model captivate sthat came with stock froyo. I said he was on the right track because the correct method to go back to stock is JF6. Which can be found in Icezar1's continuum thread which requires odin 1.3, the pda file, etc. If he would have simply tried the JF6 process again it would have completed rather than using 1 click odin and messing up everything. Read the second post of this thread where ZELENDEL says that newer captivates with froyo don't work with oneclick
http://forum.xda-developers.com/showthread.php?t=1093926
Click to expand...
Click to collapse
First of all JF6 is NOT a "method" of going back to stock. JF6 is stock firmware. And I could be wrong but I thought icezars program gave you
Stock firmware 'JI6'? I'm not next to my computer so I do t really know off the top of my head.
*EDIT* Your right, icezars1 program is JF6 firmware. However it is only given as an alternative. Even states in his OP the only reason why Odin3 Oneclickdownload would not work would be because of an unreliable USB driver. So this is indeed a safer way to get back to stock JF6. Odin3 one click should work too. It's unfortunate that it doesn't "always" work.
Sent from my SGH-I897 using XDA Premium App

Coreym said:
First of all JF6 is NOT a "method" of going back to stock. JF6 is stock firmware. And I could be wrong but I thought icezars program gave you
Stock firmware 'JI6'? I'm not next to my computer so I do t really know off the top of my head.
*EDIT* Your right, icezars1 program is JF6 firmware. However it is only given as an alternative. Even states in his OP the only reason why Odin3 Oneclickdownload would not work would be because of an unreliable USB driver. So this is indeed a safer way to get back to stock JF6. Odin3 one click should work too. It's unfortunate that it doesn't "always" work.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I'm sure you understood what I meant when I said JF6. It is certainly a rom and the process mentioned in Icezar's thread is one of the preferred methods of downgrading a newer model captivate that is on stock froyo. Let's hope that we have answered and clarified all questions for the OP.

duuhdave said:
I'm sure you understood what I meant when I said JF6. It is certainly a rom and the process mentioned in Icezar's thread is one of the preferred methods of downgrading a newer model captivate that is on stock froyo. Let's hope that we have answered and clarified all questions for the OP.
Click to expand...
Click to collapse
i actually didn't understand what you meant. You make 2 refrencses to using JF6 as a method. First you said the correct method to go back to stock is "JF6", then you said the JF6 process. Again...both refrences to a single JF6 method, when that is not the case. Both methods used to get back to JF6 stock firmware use Odin. One is a one click program, the other a manual flash using .tar.md5 file.

Duuhdave, if im on stock froyo (im in canada btw, so rogers) and use cezars method of flashing stock firmware through full blown odin, should I be flashing jf6(i897 2.1) or rogers 2.1? I ask this because ussualy they want you to on jf6 before flashing.
Sent from my SAMSUNG-SGH-I897 using XDA App

As far as flashing to stock with Odin 1click from stock Froyo, it has worked fine for me MANY times. Bricking using the odin 1click may be related to build number. I went from a 1007 (with stock 2.1) to a warranty repacement 1008 with froyo stock. I flashed 2.1 without a problem, and have several other times.

Using Odin 3 one-click, and icezar1's stock rom will both take you to I-897 AT&T stock JF6. If you want to return to Rogers stock 2.1 without flashing bootloaders, use TRusselo's Rogers Captivate Stock ROMS no ATT logo!.

Thanks for the help!
Sent from my SAMSUNG-SGH-I897 using XDA App

its the build number that caused it

More than likely it was something about the phone having stock froyo with the 3e recovery. I have never had the issue with any of my 2 captivates 1007's and wife's 1010 build but they came with stock eclair. I know many people have had issues due to the stock froyo with 3e recovery as why there is a modded 3e recovery how to somewhere on this forum. Since he laready had froyo boot loaders it has nothing to do with that, and either was a fubar flash due to 3e recovery, bad USB cable, etc that messed things up.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted

[Q] Keep getting "Unregistered device" while updating to Gingerbread

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.

help with flashing back to stock!

hey guys have the rogers captivate 896. I have a jig for download mode. Ok so I was on miui gingerbread. I wanted to try with weUI ics. So I followed their procedure correctly. Install completed but like another user I got it hanging at the MI boot screen. So having to flash to stock before I felt comfortable. So I've always used odin 1.32. I set the pit file that came with it and downloaded the rogers. 2.2 stock files. I get in d/l mode, run odin does some things, and it gets halfway through the factoryrs file and fails. I'm freaking lost here. Any ideas on how to get this back to stock?

If its the same files you used before I'm willing to bet its a funky usb cable. But before you go buy another (unless you have a spare) Try rebooting machine running as admin re-downloading the firmware. Also probably not the issue Odin 1.35 is kinda older version, but thats just my personal thing.

on both of those and still no factoryrs pass. switched new usb cable, switched all ports. so if the ics files installed, would I be able to go back to 2.2 stock rom? can anyone walk me through this as I think I'm doing this write. I even tried clicking reset bootloaders and that didn't work. So here's what I'm doing.
have jig, go into d/l mode
start odin 1.82. check repart, and leave the other two checked. load 512 pit, phone tar file and start.
this seems insanely easy. did this before but even after 10 attempts it fails. could ics be messing this up?

Don't check repartition and try it.

shouldn't you always repartition it though?

going to try flashing from a different pc. so i'm able to get in d/l mode which I know is good. I don't know what took on my phone, I'm thinkin ics installed, so can anyone point out the proper procedure to go back to 2.2 on a rogers captivate? is it merely odin, 2.2 stock, check repartition, set pit and tar, then flash?

Search for a member that goes by trusselo he has done some good stuff for the Rogers captivate
Here is his xda page. look in his signature
http://forum.xda-developers.com/member.php?u=3531712

hey I tried 3 different cords, 2 computers and multiple usb slots. All fail on factoryrs.rfs. So even in unchecking re-partition this tanks. I have a jig so getting into d/l mode is easy, I just can't get this darn thing back to stock. so i'm guessing (big guess here) I have ics files on my phone, how would I get back to 2.2. Be gentle I'm still slightly new at this!

xtracrispy69 said:
shouldn't you always repartition it though?
Click to expand...
Click to collapse
I've used Odin to get out of ICS and I never checked repartition or use pit file. But I use I897's firmware. Never used i896.
Sent from my ICS powered Captivate using Tapatalk

prbassplayer said:
I've used Odin to get out of ICS and I never checked repartition or use pit file. But I use I897's firmware. Never used i896.
Sent from my ICS powered Captivate using Tapatalk
Click to expand...
Click to collapse
what did you flash? I tried flash 2.1 and 2.2 both fail factoryrs.rfs. even tried odin 1.81. so it has to be something with the 2.2 and 2.1 rom. Just want to get this darn thing back to stock. any ideas?

Any GB firmware I had laying around. KH4, KJ3, KF1. I don't usually use GB anymore but I've needed to go back a few times to try things out.

see most posts i've read say you must repartition with 2.2 and below and can't use a pit file with 2.3. I'm wondering what'll happen if I just flash a gb 2.3.

xtracrispy69 said:
see most posts i've read say you must repartition with 2.2 and below and can't use a pit file with 2.3. I'm wondering what'll happen if I just flash a gb 2.3.
Click to expand...
Click to collapse
Go for it 10char

xtracrispy69 said:
hey guys have the rogers captivate 896. I have a jig for download mode. Ok so I was on miui gingerbread. I wanted to try with weUI ics. So I followed their procedure correctly. Install completed but like another user I got it hanging at the MI boot screen. So having to flash to stock before I felt comfortable. So I've always used odin 1.32. I set the pit file that came with it and downloaded the rogers. 2.2 stock files. I get in d/l mode, run odin does some things, and it gets halfway through the factoryrs file and fails. I'm freaking lost here. Any ideas on how to get this back to stock?
Click to expand...
Click to collapse
Are you using 2.1 and 2.2 packages that have bootloaders on them?