[Q] soft-bricked SGS, undetected to kies/odin/heimdall - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi everyone!
I have been reading all the posts I can to see if there was anything similar to what has happened to me. So this is the issue. The phone model is Samsung Galaxy S I9000GT
Last night I flashed my phone to install CyanogenMod and did the following steps:
Got it into Download mode with the three buttons
installed the Samsung USB composite device driver
Ran zadig.exe of the Heimdall Suite
Launched Heimdall frontend
unzipped Hardcore SpeedMOD kernel
ran the zImage of the Hardcore SpeedMOD kernel on Heimdall frontend (it was supposed to show a blue bar transfer but it was the normal green one on win7) it went to 100% and rebooted. It was showing the normal boot loop screen and then I tried to get it onto recovery mode and it went nuts.
After this, the phone went soft-bricked with the pc (problem icon) cellphone icons, I am able to get it onto Download Mode but unable to put it on Recovery Mode, I would like to put it on CM7 if possible, the only thing the phone does now is to get on the soft-bricked screen and on Download Mode, I have tried pluging it onto different machines running ODIN, a win7 and win XP, both 32 bit and none of them is able to recognize it, it is recognized as Gadget Device on the win XP machine, on the win7 with kies it just loops on the connecting icon, on Heimdall it doesn't recognize it at all... any ideas of what to do?

Make sure Kies is off and dead (check task manager processes for all kies related). Then try Odin.
Try cleaning the USB ports (phone/computer cable) as sometimes when the device is almost recognized that helps.
Did you try to get into recovery before it had fully flashed (ie rebooted and then gotten all the way to the homescreen)? If you tried to go into recovery during the first boot sequence then I could see having issue.
That being said, if you can get into download mode you likely only have an issue with 1) Driver (I would remove and reinstall) 2)Ports/cables (Clean and then Clean again - really I helped someone this morning that cleaned once but still had issues and then cleaned again and got it done) 3)Kies is active when it shouldn't be (like most of the time IMHO).
Also try to remove the battery, go into recovery and then immediately connect to odin. Once in odin, I'd flash a complete rom with pit file (and make sure it has all the files or you'll get a mounting error). But the key is getting Odin or Heimdall to see the phone.
G

thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file

ospina said:
thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file
Click to expand...
Click to collapse
Samfirmware.com will have a stockfirmware that should have them (but make sure all the files that create the partitions are there if you re-pit - my stock firmware does not have db_data on samfirmware but its needed for flashing with a pit file) though they are usually all packed in one file for the PDA spot.
But stock is likely not what you want. Just flash darky anything and which will get you CWM recovery which is what you want for CM7 (which I had problem trying - write down you Imei and back up you efs folder...).
G

Hello!
So I have already installed about 3 firmwares succesfully to my phone, the problem is that none of them recognizes the SIM Card, therefore rendering it useless again, I have installed 2 9000T (latinamerica version) and the 9000B and 9000M just to check, currently on Eclair on the 9000T with no option for upgrading it through kies. I just want to go back to the old firmware but I can't get to the one that is the one for my region apparently correct. Does having the SIM card in while flashing it and such has any effect on it being unable to recognize it?

No sim shouldn't matter. Have you tried changing the csc so it's your region?
Sent from my GT-I9000M using XDA Premium App

As you may see, I am total noob on this, how can I get the CSC file for my region or how can I change it?
Thank you very much

Related

[HELP] Stucked at File Analysis ODIN...!

Ive been stucked at file analysis for the past half an hour in Odin. Is this normal?
All drivers installed already. But nothing happened. Im trying to flash JM2.
Ive put the Pit file in PIT, code file in the PDA, modem file in Phone and CSC file in CSC.
ANywhere that go wrong?
Start Odin with Adminstrator Rights.
midijunkie said:
Start Odin with Adminstrator Rights.
Click to expand...
Click to collapse
Done. im still there...at file analysis.. again. LOL.. Nothing's happening. How long does file analysis usually take?
it should take second only.. what os do you use? widows 7?
jd-omnia said:
it should take second only.. what os do you use? widows 7?
Click to expand...
Click to collapse
Yup win 7. ive been trying all the ports its still the same... =( code file shud go to PDA, modem to phone and csc to csc right? sigh
use 512 pit file and remove your sim card
mrassol said:
use 512 pit file and remove your sim card
Click to expand...
Click to collapse
Done that too
This happened to me as well, but I got through it. I rebooted the computer, changed the usb port used, I shut down the phone, took the battery out and put it back in, then brought it back into download mode (I couldn't get it back into download mode after shutting it down from download mode itself) and proceeded exactly as the instructions said. Also, I ticked the repartition checkbox in Odin. One of these things made the flash work, but I can't honestly say which. Either way, file analysis is supposed to last for just a few seconds - if it lasts more than that, then something went wrong.
Unplug it and reboot PC and phone then try again it should work.
Reboot your pc and shutdown kies if it autoruns, then fire up odin and connect your phone.
nonreviad said:
This happened to me as well, but I got through it. I rebooted the computer, changed the usb port used, I shut down the phone, took the battery out and put it back in, then brought it back into download mode (I couldn't get it back into download mode after shutting it down from download mode itself) and proceeded exactly as the instructions said. Also, I ticked the repartition checkbox in Odin. One of these things made the flash work, but I can't honestly say which. Either way, file analysis is supposed to last for just a few seconds - if it lasts more than that, then something went wrong.
Click to expand...
Click to collapse
Ok i'll try your way. But yea, ive ticked repartition too, but im always stuck there regardless of what port im using. hmm..
try booting into recovery and doing a hard reset first
I had the exact same problem, fixed by simply rebooting my Windows 7 64-bit PC.
Also try using the other PIT file (I first tried 513 which didn't work for me, but 512 then did).
I had the same problem today evening. Fortunately I had another PC to try Odin and it worked!
Had the exact same problem a couple of days ago, posted it in the FAQ thread. Computer reboot fixed it.
Had the same problem, changed language and locale settings in Windows to English and that fixed it for me.
for me.. it only was that i'Ve forgotten to remove the sim card...
did it.. and the file analysis took only a second ;-)
Some precautions to take when flashing with odin!
1. Remove SD and SIM card
2. On windows 7 run Odin as Administrator and in Windows XP SP3 compatibility mode! (the last part solved the file analysis for me!)
3. First start Odin and load all the files: PDA = Code, Modem = Phone, CSC = CSC
4. Use 512.pit
5. Then boot up phone in download mode with usb disconnected
6. Make sure kies is not running!
7. Plugin usb cable
8. Start flashing!
That should do the trick!
Thanks XDA
Same issue, thought I'd bricked it but thankfully the reboot worked
BackfireNL said:
6. Make sure kies is not running!
Click to expand...
Click to collapse
Correction...
6. Make sure kies is not installed!

Stuck at Galaxy S logo!

Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3
I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?
A friend of mine has the same issue on his SGS. Both recovery and download mode working.
Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.
gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks
thanks for the help i love you no homo !
Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks
This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?

[Q] Odin3 stuck on SetupConnection

Hi all
I stupidly upgraded to 2.2.1 the other night and for the last 2 days I have been trying to connect to the phone via Odin so I can apply the 2e Recovery and put Darky 8.0 on.
The problem I am having is that every time I try to apply the PDA file (from xda-devs), it just gets stuck on SetupConnection (I have booted the phone into Recovery mode). I have tried it on my Win7 x64 PC and I have tried it on my WinXP x86 laptop, same result. I have tried Odin 1.0, 1.3 and 1.7. I have uninstalled the Kies drivers, installed older ones, installed newer ones...nothing. I have tried removing the SD card, nothing.
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!".
I'm at my wits end! 2.2.1 has fixed nothing for what I use, GPS is still rubbish, OneClickLagFix doesn't work on this version and they've put in this ridiculous 3e Recovery. So basically Samsung will not only not give us (in the UK) a decent version of their ridiculous firmware, but they have taken away our ability to fix up their garbage firmwares!
If anyone could help me get around this Odin problem, I would be most grateful! Thanks
If not, I'm going to get shut of this pile of pants and get a proper Android phone (which I don't want, because I really can see the potential)
Cheers!
You could try Heimdall instead of Odin its on the forum .
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!"
Sounds like a duff file maybe .
I have flashed CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
at least twenty times in the last month without a problem .
jje
JJEgan said:
You could try Heimdall instead of Odin its on the forum .
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!"
Sounds like a duff file maybe .
I have flashed CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
at least twenty times in the last month without a problem .
jje
Click to expand...
Click to collapse
Hi
I have Heimdall, but I don't see which box to put the tar file in... There are several options under PDA/Code
Thanks for your reply
Edit: OK so my best guess is to put it under zImage. Done that, connected phone in Recovery for BML and the Start button stays greyed out.
Edit2: Do I need a .pit file? The instructions for CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1 don't mention one...
Edit3: Still with Heimdall, I unzipped the .tar so I have zImage unpacked, the Start button lit up, I click it:"Failed to detect a compatible device"
Edit4: Tried to downgrade to 2.1 Eclair using samfirmwares. Odin goes through md5 checks, they all pass and then....SetupConnection... What's going on?
Solved!
I used the Down Volume instead of Up Volume.
Yes! I solved too with this board. Thanks!

[Q] When flashing with BVJVC my phone became stuck on boot screen

Hi guys, since I had this problem I have flashed darkys rom because I know it works and needed a working phone but I still need help flashing BVJVC as I wish to have my stock orange rom back.
The problem is that when I download BVJVC from sammobile.com (formerly samfirmware.com) I then load up odin and load the JVC_JV6_JV3.tar file into PDA (it's just the one file) and put my phone (Galaxy s i9000) into download mode, plug it into my computer and click on start. It all seems to go well, no errors showing in odin and when complete my phone comes up with some kind of status 7 error (I can't remember the exact thing it said) and just sticks on the samsung galaxy s screen (the one the phone boots up from)
I have also tried using check fus downloader, selecting Orange UK and it downloaded the same rom, it too failed. And I'm not sure what to do with the zip.enc2 file as I just unzipped the normal zip file and used the .tar file within that. Not that it's important.
Please can you help as I really would like my stock rom back and to be able to update via kies again.
Thankyou in advance.

[Q] Phone won't boot after using KJ4 instead of KK1 while installing CF-Root

In order to root my Note to install ICS, I used the CF-Root 5.3 thread but made a mistake...
I put the KJ4 zimage into the InitialCFRootFlasher zimage folder instead of the KK1 zimage.
At the end of the installation, my note rebooted as it was supposed to, but after the Samgung logo I only have a black screen.
If can start in CWM Recovery but not in Download mode (black screen too).
If I connect it to my win7 laptop I can hear the windows sound and in Odin, it there's a connected port.
Tried many things but don't really know what to do and I'd rather not getting things worst.
I search for a thread explaining how to solve that issue but couldn't find one.
After many tries I successfully managed to have my phone in Download mode. But now, I don't know what to do.

Categories

Resources