Database Develop

Bricked phone after updating to JH7 through Mini Kies

I recently found out I could update my captivate with Kies Mini. I updated and everything went smoothly. Kies told me update was successful and I unplugged my captivate. It was booting up fine until it reached the Galaxy S logo. It kept going through the logo animation for about 2 minutes before it shut off. I took the battery out and tried again. Same result. my soft buttons are lighted up. When I touch them It responds with a blink, but no haptic feedback. What is going on??How can I fix this? I tried using Odin to flash it back to stock but it won't recognize it. Mt phone was stock 2.1 with the Voodoo Lag Fix installed and everything ran fine and then after the JH7 update the phone messed up. I read that Launcher Pro causes problems with this update and you have to select the Touch Wiz UI when doing it which I forgot to do.
Please help, thank you.

this post is just as dumb/wrong as your post in atinm's thread
a) you can't be stock if you have voodoo, voodoo replaces a kernel
b) you aren't bricked because you can get to the galaxy s screen, brick means your phone won't even turn on
c) this isn't development related, general or Q&A
d) if you don't know how to use odin one-click, I'm not going to help you, you put yourself in this situation

Kaik541 said:
this post is just as dumb/wrong as your post in atinm's thread
a) you can't be stock if you have voodoo, voodoo replaces a kernel
b) you aren't bricked because you can get to the galaxy s screen, brick means your phone won't even turn on
c) this isn't development related, general or Q&A
d) if you don't know how to use odin one-click, I'm not going to help you, you put yourself in this situation
Click to expand...
Click to collapse
You rock man! Thanks for the help

I also just noticed something in your post about having LauncherPro turned on.
Kies to my knowledge won't even recognize the phone unless you're on TouchWiz UI.

teranoid said:
I also just noticed something in your post about having LauncherPro turned on.
Kies to my knowledge won't even recognize the phone unless you're on TouchWiz UI.
Click to expand...
Click to collapse
It recognized it and said it said completed. Now I am trying to use Odin and I can get the phone to recognize the phone and I click Start and it says fail and this at the bottom:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)

what does this have to do with development, again?

jatkins09 said:
what does this have to do with development, again?
Click to expand...
Click to collapse
Ok, I put it in the Captivate Q/A section...let's see if someone can help me fix the issue.

i have had the same problem in the past and i was able to fix this by wiping the cache partition

[Q] Galaxy S i9000 won't boot anymore! NEED HELP!

So I had rooted my Galaxy S, installed LauncherPro and Ryanza's OCLF. I changed some settings on LauncherPro and rebooted the phone. Trying to reboot but it won't go past the Samsung logo. The logo disappears, and there becomes this vibrate pattern of one vibrate, pause, then 3 fast vibrates, pause, one vibrate, pause, then 3 again etc...
I have tried hard reset (vol up+menu and power up) and cleared cache and deleted internal sd. No solution for this machine not booting. The phone gets to download mode (vol down+menu and power up) so I don't think it's a completely lost fight... I just don't know what to do now!
What should I do now to make this piece of s**t work again? A step-by-step -instruction is needed, or a forum link to solution. I'm in debt for life if someone will help me!

Same here!
Except I rooted and downloaded a lagfix from the market and when it said it was going to reboot, it never did!
I'm looking around, but if I find what to do I'll post it here.

Try re-applying the update or whatever firmware you have

utsmaster18 said:
Try re-applying the update or whatever firmware you have
Click to expand...
Click to collapse
What do you mean? I have the latest Scandinavia Froyo on it which was applied somewhere around 5th of December 2010... I dl'd this custom rom from xda, Darkys_v6.0_Gingerbread_Edition_Voodoo_signed, but as it's installation procedure is written for a booting phone, I don't know what to do. I would be pleased if I'd even get a stock Froyo in the phone so it would work again.
I just bought that LauncherPro also.
So here is what I remember of what I did before the "maybe-semi-brick";
1. First state was a regular Froyo 2.2 Scandinavia (Finland) can't remember which version exactly, but it's the latest from Samsung (updated with KIES).
2. Then I wanted to root the phone for OCLF. Root went fine, OCLF installed, serious boost of performance etc... SuperUser and busybox was installed fine. Worked for several days without problems. Installed SGSTools from market.
3. Installed LauncherPro. Installed also HandCentSMS and GoSMS to try them out. Installed also ADWLauncher and some other minor launcher from market which was supposed to look like an Gingerbread. I didn't like either of them so I uninstalled them using uninstaller.
4. Also uninstalled some other programs which I didn't use or they weren't useful/were crappy. Applied some settings in LauncherPro, and I can't remember if this was actually intentional or not, but I might have accidentally clicked the reboot icon on my first desk which was created with my agreement by SGSTools.
5. So I thought "no problem, it has to be booted sometime anyway". Then "kaboom!", won't load to TwLauncher nor will to LauncherPro.
I have Odin 1.7 on my laptop already and this CustomROM .rar-file which I would like to flash on my device. Again, the phone goes well into download mode, but I don't know how to flash it. And with some minor googling, I didn't find a noob-friendly directions either (all I did get was sites related to Final Fantasy VIII because it had Odin as a GF in it, lol... brings back memories).
Yeap. Almost ANY rom will do fine. I don't know how to check which version of Froyo it has/had (does it matter?). Now I just need some step by step instructions so I won't brick this quite expensive toy!
Oh and just for a reminder! As my little brick had OCLF installed and applied (Ryanza's), can I just flash the phone without care? Or is it even possible to flash without bricking the phone?
Solution! Re-flashed with Odin 1.7, updated to the newest fw available and works now fine. Only my Scandinavian keyboard got fu*ked up, there's no more ä's and ö's which are needed to communicate with other people... Maybe the market app Scandinavian keyboard will fix it... Thanks to all who helped in any way!
Still in need of help, look below.

So I updated to the latest fw (I9000XXJPY) and it worked fine. It was quite fast and reliable. The only thing was that it didn't allow me to update the phone in KIES. This must be because the I9000XXJPY is leaked, right?
SO, I put an earlier Froyo (I9000XXJPM)in with Odin, installed fine, tried to update with KIES. It says that this device can't be updated and shows PDA:JPM/PHONE:JPM/CSC:JPM.
The reason why I would like to update is because of those letters ä and ö. I installed the scandinavian keyboard from the market but it sucks compared to the Samsung keyboard or Swype. What should I do to or which fw should I flash the phone with to have this Finnish keyboard layout with Samsung keyboard?
Lucky me! Tried to flash with Odin to I9000XXJP1 and the phone-!-PC screen ended up. I then press the vol up+vol down+power button combination, then screen flashes phone-pc, blank, phone-pc, blank (in this point release the power button), phone-pc. Then restart, volume down+home+power, enters into download mode. Tried to flash the newest because for some unclear reason I think it's time for me to stop fooling around with this... So I tried to flash, but Odin says this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> modem.bin
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do. I'm so good at this!
F**k yes! Booted up phone once again, restarted Odin. Thank heavens, at least the JPM is going in now. I think I won't play anymore with my i9000, **** those ä's and ö's..

[Q] I think I just bricked my phone?

Beat with me guys, I am very very new to this board, and I apologize if I post this in the wrong area.
Lemme start from scratch.
My phone is not rooted or anything like that. BUT I wanted to update my software for the Captivate to 2.2 using samsung Kies.
Not sure what happened, I though I had the correct drivers installed and what not, but it gave me the screen with the phone, exlamation mark, and computer.
I can put my phone into download mode, and I installed odin3 one click downloader. The problem is, when it gets to the part 'file analysis' it gets stuck there.
I watched a video on youtube and his went automatically, so I'm not sure at ALL what to do. If I can fix this myself, I'd love to. If not, I will go through AT&T and see if I can get it replaced.
Any help would be greatly appreciated.

Not sure how to fix it, but if you have to send it into samsung say it got screwed up somehow while trying to update to KB1, in truth that is what happened, plus if you say that they will try to fix it fast

If you have access to another computer, download ODIN and try it on that one. Odin works on my laptop but not on my desktop.
CM7 Inspire 4G

What you have is a soft brick. Keep trying to get into download (try both 2 and 3 button methods) and then retry Odin. Look in Dev subforum for the "How to flash a ROM" sticky as there is good info on how to do this.

Samsung was absolutely no help lol.
Well.. I guess I can try this on another desktop.
Jeez I regret trying to upgrade man. Shoulda waited and learned more.
Has anyone had odin3 get stuck at file analysis before?

What model is your Cappy? You can find the model number underneath the battery (on the phone itself). It should have a number like 1006,1007,1008,1009,1010,etc.
Also, it'll be a good idea to try this alternate method in the mean time:
Make sure you know how to go to Download Mode, and that you have the drivers installed properly.
Windows 64bit
Windows 32bit
This is the manual (or "full") Odin, it's taken from a post by icezar1 in the Development Forum:
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Do not use this if you know you flashed a -LOW- ODIN package (when opening the PDA***.tar or CODE***.tar you will find inside boot.bin or sbl.bin)
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
Download the package from here
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot your phone in Download Mode
Run Odin3 v1.3.exe
Plug in your phone via USB
Click on the button PDA
Choose JF6_secure.tar.md5
Click start
Wait and do not unplug cable until it is finished

venomio said:
What model is your Cappy? You can find the model number underneath the battery (on the phone itself). It should have a number like 1006,1007,1008,1009,1010,etc.
Click to expand...
Click to collapse
Just for clarity sake, those are not the model numbers, they are build date (first two are year, second two are month). The model number of the Captivate is i896 or i897.

I know, I keep saying that they're model number though for some reason. Thanks anyway I guess.

Thank you venomio this 1.3 is working much better.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Check MD5.. Do not unplug the cable..
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
That's where I'm at right now. Fingers crossed!!

aftermaz said:
Beat with me guys, I am very very new to this board, and I apologize if I post this in the wrong area.
Lemme start from scratch.
My phone is not rooted or anything like that. BUT I wanted to update my software for the Captivate to 2.2 using samsung Kies.
Not sure what happened, I though I had the correct drivers installed and what not, but it gave me the screen with the phone, exlamation mark, and computer.
I can put my phone into download mode, and I installed odin3 one click downloader. The problem is, when it gets to the part 'file analysis' it gets stuck there.
I watched a video on youtube and his went automatically, so I'm not sure at ALL what to do. If I can fix this myself, I'd love to. If not, I will go through AT&T and see if I can get it replaced.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm in the same exact situation as the OP. I'll try the instructions posted below and report my findings.

check your build number first before you flash using odin. certain build may not work with odin one-click.
an usb jig will help you out if you cannot get into the download mode or just in case:
http://cgi.ebay.com/ws/eBayISAPI.dl...84198&ssPageName=STRK:MESELX:IT#ht_782wt_1139

[Q] stuck in odin

<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
does nothing else... Don't know what to do. I mean, I can't plug it out or turn off, right?
I tried to get back to the stock rom... and yes, i did an factory reset and cache wipe etc before..
Anyone who can help me?

NP, this thing happened to me... Is it because you clicked on re-partition...?
I cant guarantee, but i unplugged it, and it was soft bricked, i then flashed it without repartition checked.
Hopefully works for you
GL

you can indeed uplug it in this situation. Pull the battery and let it sit, go back into download mode and reflash the stock firmware.
If you check re-partition, make sure you have a pit 512 file that you are flashing. If you do not have a pit file, then make sure re-partition is unchecked.

Thanks both.
I did not check re-partition. I am not experienced with all this and i'm fairly new.
I just tried to flash the stock rom, because I couldn't boot up properly.
Ok. I'm trying to flash it again. It's actually doing more then it did before. I'll let you know
EDIT
OK.
I tried again but it was stuck again. Now at like 95% of the completion -.-

I tried for the third time. It keeps failing ....
anyone who can help me with this?
btw, i just noticed i posted this in the Galaxy S forum accidently. I have a SGSII instead. But I think it doesn't make any difference?
edit:
After the fourth time it worked..

sebas156 said:
btw, i just noticed i posted this in the Galaxy S forum accidently. I have a SGSII instead. But I think it doesn't make any difference?
edit:
After the fourth time it worked..
Click to expand...
Click to collapse
Lol fourth time...
SGSII your using the correct firmware then right? The link i gave shouldn't apply to you it could brick your phone...
Yh, Odin can be annoying sometimes, you can either wait a while and try again later, restart and try again, or use heimdall. Or you could flash a zip through recovery (not sure if that last one works if you cant get past boot)

Talon26 said:
Lol fourth time...
SGSII your using the correct firmware then right? The link i gave shouldn't apply to you it could brick your phone...
Yh, Odin can be annoying sometimes, you can either wait a while and try again later, restart and try again, or use heimdall. Or you could flash a zip through recovery (not sure if that last one works if you cant get past boot)
Click to expand...
Click to collapse
Umm no I used the right SGSII firmware. You didn't even gave me a link.
I'm sure I used the right firmware.
the first time I tried (when I posted), it got stuck before it even really started. second time and third time at 90-100%. the last time it worked.
I have no clue why it wasn't working, but this was the only solution for me (no, I couldn't boot, so I couldn't put anything on my SD and use CWM).

odin hangs often for the simplest of reasons, especially a loose usb connection -- test this by plugging into you pc or laptop and see if it stays linked or unlinks after a short duration or if the cable is jiggled -- you then know to hold the cable when using odin, or better still, get a replacement usb cable

Need Help with Samsung Brick Issue

Hi,
I am from UK and am a complete and utter noob and not very technical at all.
I bought an SGS GT i9000 and it already had 'Darkys ROM' installed. (I just thought that was normal). The phone worked well etc and a few days later since the phone was second hand I came across a 'factory reset' option and then the phone never worked again.
Got stuck in a boot loop so I read.
Also my phone will not enter download or recovery mode using the 3 button procedure so I purchased a 'jig' off ebay. It will now go into download mode upon inserting the jib.
I tried to recover the phone by following: http://forum.xda-developers.com/showthread.php?t=1802778
I completed all the steps but it made no difference to the phone. It still gets stuck in the boot loop.
Can anyone recommend a guide for me? I have seen others but cannot follow them as they often use too much jargon.
Furthermore, if possible I would like to just put my phone back on to a stock ROM. But I will do anything just to get it back working again and cross such bridges once it is up and running!
All help is really appreciated.
cheers

Furthermore,
Odin output (from following the xda guide linked above):
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Removed!!
Odin resets the phone after the firmware update start and then it gets stuck in the same loop again. The four colours coming together to form an x-shape (red, yellow, green and blue).
After which the phone starts up and gets stuck in the boot loop where it was getting stuck previously.
Can anyone point this noob in the right direction please?
thanks

sbow1 said:
Can anyone point this noob in the right direction please?
thanks
Click to expand...
Click to collapse
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due tio differnt versions of Galaxy S
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card...make sure you have more than 50% battery charge before you attempt any sort of flashing.
Odin will get stuck for two reasons 1) KIES is running in the background of your PC or 2) the files you downloaded are corrupted
Look at the solutions thread for answers and collections thread for rescue kits
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions

Hey
try to upgrade to 2.3.6 (link below) after applying the JIG..plus make sure that u have the SGS drivers installed and KIES IS NOT RUNNING...

checkout video guide for bricked sgs gti9000 on youtube puggereduk.com

here try this i made it myself just read the readme and follow. works for me everytime
http://www.mediafire.com/download.php?34oxweahfpy53dj

I agree with the recent posts, you need to follow a guide on how to flash a stock rom through Odin. Good luck flashing!