Bricked phone after updating to JH7 through Mini Kies - Captivate Q&A, Help & Troubleshooting

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

Related

[Q] Help! Woke up this morning and phone won't turn on!

I woke up this morning and my phone won't turn on! I hold down power and see the Samsung splash screen... then the display goes off and nothing happens. I can't launch into recovery mode... I can launch into Download Mode, but can't do anything from there... (no response to any buttons)
I tried pulling out the battery and SIM - to no avail...
I am running a rooted Bell phone with the lag fix.
Please give me suggestions! What do I need to do to recover this using my PC and adb?
Time to recharge your SGS?
Before i give you the bad news
try Flashing the phone with Odin, see if you can complete a successful flash
However you'll most likely see an Odin error concerning mounting the drive, your Internal SD drive is most likely dead, and it'll need to be replaced by Samsung/Bell service center.
there are many known cases like this related to the lag fix
slaman said:
I woke up this morning and my phone won't turn on! I hold down power and see the Samsung splash screen... then the display goes off and nothing happens. I can't launch into recovery mode... I can launch into Download Mode, but can't do anything from there... (no response to any buttons)
I tried pulling out the battery and SIM - to no avail...
I am running a rooted Bell phone with the lag fix.
Please give me suggestions! What do I need to do to recover this using my PC and adb?
Click to expand...
Click to collapse
atan.ismail said:
Time to recharge your SGS?
Click to expand...
Click to collapse
It's fully charged... it was charging all night. What's weird is that I've plugged it in and it's flashing the battery symbol.... I can't turn off the screen - it keeps flashing this symbol
slaman said:
It's fully charged... it was charging all night. What's weird is that I've plugged it in and it's flashing the battery symbol.... I can't turn off the screen - it keeps flashing this symbol
Click to expand...
Click to collapse
if you hold the power button, does it turn on at all?
how far does it go into the boot process?
does it get stuck after the pretty Galaxy S swirling logo?
AllGamer said:
if you hold the power button, does it turn on at all?
how far does it go into the boot process?
does it get stuck after the pretty Galaxy S swirling logo?
Click to expand...
Click to collapse
I don't get the swirling logo... I just get the static splash page "Samsung Galaxy S" - it stays for about a second, then the screen goes black.
I'm trying to figure out what to do once I'm in download mode... I have Samsung Kies (which won't detect it...) and Odin (which won't detect it)
slaman said:
I don't get the swirling logo... I just get the static splash page "Samsung Galaxy S" - it stays for about a second, then the screen goes black.
I'm trying to figure out what to do once I'm in download mode... I have Samsung Kies (which won't detect it...) and Odin (which won't detect it)
Click to expand...
Click to collapse
that doesn't sounds right
try installing Odin on another machine
seems like the PC you are trying to use has the USB port locked up.
i've had that happen on mine before
if you turn off the PC, remove the power cord
power it on, then put the power cord
and power it on again
that should reset it
Ok, Odin seems to recognize the phone (it installed all the drivers when it was in Download Mode) - I clicked "start" and got the following:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> Removed!!
then the phone went back into the flashing battery symbol... I need to grab the official Bell Samsung Galaxy S .pit file I guess.
Samsung Kies just sat there trying to connect when the phone was in Download Mode...
Okay, so I've downloaded the 0803.pit file... I just need to know which firmware to flash it with under PHONE, PDA, CSC, and DUMP...
Would really appreciate the help!
JH2 firmware for all 3 and flash with correct pit file and click partition (but will wipe all data).
rmanaudio said:
JH2 firmware for all 3 and flash with correct pit file and click partition (but will wipe all data).
Click to expand...
Click to collapse
I found the thread for JH2, but none of the links in it work!
http://forum.xda-developers.com/showthread.php?t=755063
Got one that you can spare?
Also, 0803.pit works for JH2 right?
Really appreciate your help!
I'm just going to try to find JG9 and upgrade via Samsung Kies... that's if I can find JG9 - these are so hard to find!
Hi Mate,
I just had the same problem - could not reboot from normal recovery, could not reboot from clockworkmod recovery. I had to launch nandroid recovery.
On my unit, it seems that the problem was caused by a conflict between setcpu profiles and the alter minfree settings from ryanza's oclf.
If you have clockworkmod installed and have backed up your rom, you should be able to use nandroid recovery.
I have now changed setcpu not to run on boot, and have not used alter minfree - prob seems to be sorted.
Hope this helps (you or somebody else).
Regards, Paul.
Go here to download firmware: http://www.samfirmware.com/firmwares.htm
rmanaudio said:
Go here to download firmware: http://www.samfirmware.com/firmwares.htm
Click to expand...
Click to collapse
Saw that.. but there's no I-Series... I can't see any firmwares for Samsung Galaxy S there - am I blind?
EDIT: Found it - thanks.
This JH2 on his site is the "updated" version of JH2 that fixes the 3-button recovery as per the Facebook page right?
http://www.facebook.com/note.php?note_id=10150262535205538&id=260085296049
or is this the "earlier" version of JH2?
http://www.multiupload.com/ZNBT2RY5Y0
Use 512 pit file.
http://samfirmware.webs.com/samsungandroid.htm
Top left, just had to click on "android phones" to get here... good luck!
slaman said:
Saw that.. but there's no I-Series... I can't see any firmwares for Samsung Galaxy S there - am I blind?
Click to expand...
Click to collapse
It is there...dont look for I series...click on Android. Then grey area for america files.
Got the file... tried to update through Odin... and it's stuck on the following for 15 minutes...
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
The phone still shows Download mode.
Do I need Odin v1.3 or is Odin v1.0 sufficient? Using PIT0512
EDIT: Pulled out battery... tried again... now see blue status bar moving along the bottom... fingers crossed that this works!
It completed... and same thing is happening. Can't start it up...

[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

Suddenly cant boot my phone, or get into recovery

Hello gentlement. I have an Galaxy S I9000, and i have used a custom rom for about 2-3 months, unfortunately i can't remember which one, and as i cant boot my phone, im not sure how i can find out. I flashed it using Odin and Clockwork mod, both of which worked great. The problem now started out with me not being able to start my phone while charging, didn't pay much attention to it and just waited until it was charged, or unplugged it, started it, then charged it while it was on.
Now im having a different problem. I cant start my phone, the startscreen just says "Samsung galaxy S" etc, and it tries to reboot again and again.
I can start the phone into "download mode", but recovery mode doesnt seem to work.
Since the rom has been working flawlessly in the past, im not sure its the roms "fault"; might just be my phone singing on it's last verse.
Does anybody know what can cause this, or have a fix i can do in download mode?
I think i have read all the necesarry stickies, if i've missed something i apologize.
Thanks for all responses, regards - superegge
When this happens on ICS I reflash a kernel through odin in download mode and then reflash the ROM.
If your ROM is non wipe you could try this, otherwise I'd just try flashing a kernel and see if it boots.
superegge said:
Does anybody know what can cause this, or have a fix i can do in download mode?
Click to expand...
Click to collapse
First power down, remove battery, remove sim card and EXT SD card, preess power button for a min, reinsert battery and power it....
If still the same, flash a pit file as per guide given in Quick Fixes link below
xsenman said:
First power down, remove battery, remove sim card and EXT SD card, preess power button for a min, reinsert battery and power it....
If still the same, flash a pit file as per guide given in Quick Fixes link below
Click to expand...
Click to collapse
Thank you both for responses. I've tried following your guide many times now, installed odin etc. But everytime i try to flash my phone, this happens:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> Removed!
Sometimes it gets to some zImage thing, but my device is still "removed" shortly after. Is it maybe a faulty cable?
Will check back in tomorrow, need to sleep now. Again, thanks for your help
superegge said:
Sometimes it gets to some zImage thing, but my device is still "removed" shortly after. Is it maybe a faulty cable?
Will check back in tomorrow, need to sleep now. Again, thanks for your help
Click to expand...
Click to collapse
yep, it could be due to cable or mostly the PC, try on lap top or another PC, added concerning this to Quick fixes, take a rest first,
ive had the same problem with Odin. But that had to do with rooting, and the oneclick superuser program.
Hopefully it will work when you try on a new pc. Good luck superegge!

[Q] Help overcome brick

hi fellow devs. from the galaxy tab community,
i have come to a very difficult situation for flashing and this just went completely wrong. let me describe:
i wanted to flash a cm10 nightly to my galaxy tab p1000n, i didnt realize i had flashed the wrong version which was cm10 nightly for p1000.
at this point the touchscreen had no response over the software. blue cwm was installed correctly.
so i tried to reflash the correct p1000n cm10 nightly, but i was unable to do it, the android kept dying, and installation never happened.
tried PA ROM same problem, the android kept dying not being able to update from zip.
so i tried to bring back to stock.
used the overcome method listed in q&a thread
flashed wrong files apparently once again thinking that these was going to help.
everyting in ODIN went well got the GREEN PASS!
after that my tab didnt reboot. all i get is the lights on touch capactive buttons, black screen.
ODIN still recognizes the TAB i get the yellow box 0:[COM5]
although whatever I try to flash i get this message:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
after this msj, nothing happens.
this has been very frustrating, I never thought it would get to ths point, ive been reading for about 4 hours, and nothing seems to be clear enough, to the point that I dont know If theres a solution to my problem. I would appreciate help from you guys.
i think Heimdall could be the best bet although its still not very clear ho to fix this problem. my question to you guys if theres a specific series of steps to really fix this problem? without getting to point to completely kiling it, this TAB is not mine thats the worse of it. i have experience using both flashing methods, heimdall super one click and ODIN with my infuse 4g. if anyone could provide me with the necessary files to repair the P1000N, that would be much appreciated, if anyone could guide me would me much better, thanks in advance, i just hope to find a solution to this mess.:crying:

Categories

Resources