[Q] I lost my SGS firmware by wrong wy of flashin .....please HELP - Galaxy S I9000 Q&A, Help & Troubleshooting

I tried to update my SGS to android 2.2 through kies wihtout puting my phone in to recovery mode. The firmware seems to be lost and the device cannot boot only give me a black screen with word samsung galaxy s GT I9000 wrote on it.
Iam very new in android devices please help me. I do not know what I should to do..

Mine did the same thing when I flashed with Kies.
Try this: Hold Volume UP, Home button and on/off button together until a screen with a few options appears. Select Wipe/factory reset from the list using the volume up/down button. Select ok and reboot. You will loose all your data but your phone will work again.

aviatorshar3an said:
I tried to update my SGS to android 2.2 through kies wihtout puting my phone in to recovery mode. The firmware seems to be lost and the device cannot boot only give me a black screen with word samsung galaxy s GT I9000 wrote on it.
Iam very new in android devices please help me. I do not know what I should to do..
Click to expand...
Click to collapse
BTW You did the upgrade the right way. With Kies you don't need to go into recovery or download mode before flashing. Follow the previous posters instructions and if that doesn't work you'll need to search around here more, for other flashing methods or just to find out if your internal sdcard is dead.

Related

[Q] Stucked on the samsung galaxy s screen.

Stucked on boot screen (the one that we usually see first with white letters). I did factory reset but I am still stucked on Galaxy S boot screen. I heard the default galaxy S sound but did not see the big 'S'. When I press Volume down + Home + Power , I just see a big triangle which says 'Downloading...do not turn off target'. This means that I can go into the download mode.
I installed odin3 and installed .512 PIT file as well as JH2 firmware from samsung-firmwares website. Inside the JH2 zip file I see a file with extension .tar (I think this goes in PDA section of ODIN).
After connecting my phone with my computer, I see 0:[COM6] in Odin. Plz guide me from hereon. Any help will be much appreciated.
NOTE: I was using gscript o change system fonts. Probably deleted system fonts. Then, I restored back to system and since then phone would not start. Well, it starts but I am stucked on this screen.
I am using Samsung galaxy S vibrant (Bell, canada [GT-I900M])
I will not help because you didn't ask the right question. Please change the title of your thread to something more intelligible or no one will bother.
Bec07 said:
I will not help because you didn't ask the right question. Please change the title of your thread to something more intelligible or no one will bother.
Click to expand...
Click to collapse
Sorry...I will change now
...
Try the same combo but with volume up. Why do you want to connect to kies?
Bec07 said:
...
Try the same combo but with volume up. Why do you want to connect to kies?
Click to expand...
Click to collapse
I am trying to connect to KIES because I think i can reflash using test mode.
Yes..I tried that? Did wipe/factory reset..then rebooted....got the same screen again.
Thanks for replying
EDIT: when I go to recovery menu (Volume up + home + power) and then connect with USB...I can see my device listed by using 'adb devices' command in the cmd prompt.
OK....When I connect my phone to my computer via USB, I can see 0:[COM6] in ODIN. I can go into download mode. I have downloaded JH2 firmware (zip file from samsung-firmwares website). I have Bell Samsung galaxy S vibrant. Can I flash with ODIN.
hay buddy i had exact same problem and this post saved my life... here it is hopfully it will help u out if it does let me know
http://forum.xda-developers.com/showthread.php?t=984140

[Q] Blind guide through Clockwork Recovery

Hello guys,
I think my SGS is screwed, but maybe with a factory reset I can get it atleast to work...
Atm the phone is in a bootloop after trying to update my light'ning rom. It starts up with the normal "Galaxy S GT-1000" and below "Samsung" screen, after which I only see a messy pixelated screen instead of the usual animation. Shortly after it goes back to the previous screen. This repeats itselfs endlessly.
The phone does go into download mode, using the 3 buuton combo, but my pc does not recognize it. I tried everything, reinstalling drivers, kies, etc, on several pc's/laptops. After some messing around witn battery in and out I do get it into recovery mode, but it is onreadable. The first galaxy S screen is still visable and the recovery menu is in a different resolution then normal above that, making it impossible to read and go through the menu.
I was hoping anyone could give me some step by step guideness through it, so I can try if a factory reset does anything.
dont know if it will help but boot into recovery
volume down button 2 times
power button once
volume up button 5 times
power button once
that will do a factory reset and see if it fixes ya
This is a galaxy i9000 forum!
Sent from gt i9000 insanity 8.5/fugumod
slaphead20 said:
This is a galaxy i9000 forum!
Sent from gt i9000 insanity 8.5/fugumod
Click to expand...
Click to collapse
what do you mean by that ?
The OP has got an i9000
Galaxy S GT-1000
But its probably his tipping or smel checker .
jje
If you got USB-debugging enabled, you can try to force it to recovery using adb:
Code:
adb reboot recovery
If not you will have to reflash your ROM using odin (a ton of guides for that)
Odin will only work if I get the USB bug fixed, wich I can't. Specially since I cant even start up android. No debugging there...
I can get into download mode, so that leaves me with some hope the phone is still fixable...
Ayone else tips?
azzledazzle said:
dont know if it will help but boot into recovery
volume down button 2 times
power button once
volume up button 5 times
power button once
that will do a factory reset and see if it fixes ya
Click to expand...
Click to collapse
Thanx, it seemed to do the reset (there did happen things that looked like one, haha) but sadly no succes so far....
all I can do now is try to get to my download folder blind and reinstall the rom that is in the download folder... I have no clue wich nr folder the download folder is, but that is just a matter of endless trying ...
so have you managed to get the phone recognised by the PC ?
if not, try heimdall, i hear that works for issues like yours - something about installing a custom driver for the USB ??? i dont know ive never had to use it luckily
SGS usb drivers
For the drivers you could try http://forum.xda-developers.com/showthread.php?t=961956
there is also a link in samfirmware.com
http://www.samfirmware.com/WEBPROTECT-programandroid.htm
with drivers.
I had a similar problem yesterday ( Broken boot, no recovery mode, only download mode with no USB recognition,) but after trying to reinstall some drivers it worked and now my phone is back online thanks to odin and samfirmware.

[Q] Samsung Galaxy Ace S5830D - Semi-bricked - Need Help!

Hey All,
So I'm in the process of helping a friend with his Galaxy Ace from Koodo. As it turns out the phone looks like it's semi-bricked but we may be mistaken all together so here goes:
My buddy tried using SuperOneClick to root his device however half way through the process, it froze and when he restarted his device, it hangs at the Samsung logo during the startup boot sequence.
1. When using a combination of UP Arrow + Home button + Power, he receives a message stating:
"RAMDUMP Mode
(ARM9 mode)"
In this mode he cannot do very much however his PC does recognize the device. Odin does not work in this mode.
2. When using a combination of DOWN arrow + Home button + Power, he received 2 different screens. The first is a bright pink colored screen that states:
"Warning!
A custom OS can cause critical problem in phone and installed applications. If you want to download a custom OS, press Volume UP key. Otherwise, press Volume DOWN key to cancel."
Pressing the down arrow brings him back to the frozen Samsung logo on startup however when pressing the UP arrow, the phone goes into "Downloading..." mode. In this mode, Odin DOES work.
-----------------------------------------------------------------------------
Now for the troubleshooting we've done. We managed to find a few articles online that asked us to use the Odin tool. We downloaded a few different sets of the files needs (Cooper.ops, CODE, MODEM, CSC & BOOT). Odin then detects the phone in 'Downloading..." mode and proceeds to installing the rom. It completes successfully however it does not reboot. The screen simply flashes with the Samsung logo again.
The original firmware build before the device stopped working ended with TLKI4.
-----------------------------------------------------------------------------
1. Can anyone suggest anything else we can try?
2. Do you know if the bootloader needs to be flashed first and if so, how?
Note: We can not take the device back to Koodo as it was purchased on Kijiji and no receipt was provided. It's the GT-S5830D.
Thanks in advance,
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
madman_amit said:
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
Click to expand...
Click to collapse
Can you point me to a certain rom/boot loader to download from sammobile? I was there earlier this morning however I didn't see any mention of Canada anywhere and I left before I messed things up further.
Even if you could just tell me which one it is I have to download, I'll do the rest myself.
Thanks a bunch!
an0nym0us_ said:
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
Click to expand...
Click to collapse
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
merrybob said:
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
Click to expand...
Click to collapse
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
madman_amit said:
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
Click to expand...
Click to collapse
Thanks buddy! I tried that exact ROM however it didn't seem to work either. I used the 'Coopers_V1.0.ops" file under the "OPS" option in Odin and the "S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5" file under the "One Package" option. Like I said before, the flash went through in "Downloading..." mode, and Odin said "PASS" however, when it came time for the phone to reboot itself, the screen started flashing and did nothing new. Same Samsung logo appears and it seems to hang right there.
Also I dont think the device has a same recovery menu anymore because even though I hold down the Home + Power buttons, it does nothing. It simply flases the screen at the Samsung logo screen.
Any other tips for me to try? Thanks again!
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
an0nym0us_ said:
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
Click to expand...
Click to collapse
I held it down for more than a minute just to make sure. As soon as I put the battery back in and try and restart the phone, it goes into an infinite loop at the Samsung screen.
Even I find it odd that the phone will go into Downloading mode but not recovery.
Any other suggestions?
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
an0nym0us_ said:
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
Click to expand...
Click to collapse
As far as I can tell QtADB isn't even detecting the phone. I have tried to complete the procedure over and over however no show. I may not have installed ADB correctly though so I'll give it a shot again a little later.
Thanks!
edited due to same soloution already posted.
tengo uno en las misma ay solucion

[Q] Samsung Galaxy S I9000M Boot Screen Loop

Hi there, I am new to this forum as I am trying to fix my gf's Samsung Galaxy S i9000M on Bell.
I tried to search up boot loop and have tried a few different ideas on the board but it doesn't seem to work.
Would like to know if anyone can help.
Here are the specs: Samsung Galaxy S i9000M - unrooted / stock.
Problem: The phone when turned on will only show the "Samsung Galaxy S I9000M" screen. It will turn black and then reloop itself. I have tried the 3 button boot to "download mode" and have successfully connected to ODIN.
I have tried to download PDA/Phone/CSC from one of the pages on this forum containing North American firmware files.
However, the problem still persists! I cannot check the OS version as I can't get the phone to boot into the OS. Is this a bootloader corruption problem? What should I do to try to fix this issue?
Any help would be greatly appreciated! THANK YOU in advance.
I assume you want Gingerbread?
If so, you want the UGKG3 download from Bell (it's the only GB ROM from Bell to date).
Go here and search for UGKG3.
The file is in 7Zip format. If you do not have anything to unpack it with, download IZArc.
Thanks for responding so quickly.
I did try the GB firmware - flashed it with ODIN - the software says successful.
But once the phone boots - it goes back into the loop - it does not know to unpack the OS to try to install and boot into it....
Any other ideas? Thanks again!
Did you flash it as a single file or 3 files?
You need to unpack the 7Zip file so you end up with 3 files:
Select PDA_UGKG3_Sbl.tar.md5 for PDA
Select CSC_BMCKG3.tar.md5 for CSC
Select PHONE_UGKG3.tar.md5 PHONE
Then flash with Odin. That should get the phone up and running again.
---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------
How long has she had the phone? I wonder if she was on Froyo or GB.
Can you get into the recovery menu?
Thanks for your response.
I have unpacked all three files and loaded it into ODIN as per the firmware upgrade instructions on the thread you provided me.
I have also tried loading in both both the GB and the Froyo versions (UGKG3, UGJK3). After the "successful" message on ODIN, the phone boots up - shows the Samsung Galaxy GT I9000M screen and then goes black and keeps looping again.
I have a feeling this made me a problem with the bootloader. If the phone is completely stock, which one should i try flashing?
As the phone is stock there isn't a recovery (CWM) that i know of.... Or am I incorrect?
thanks again for your help!
OK, thanks for the clarification.
There should be the stock recovery from Samsung (2e or 3e).
Yes, it does sound like a bootloader problem.
Is it still under warranty?
EDIT: What is the build date for the phone? There will be a number in YY.MM format under the battery.
See if you can get into the recovery and try to clear the cache. That may give an indication as to what is going on.
We've had the phone for a year and a few months, so no more warranty.
In fact, we brought it back to bell store and they said there is "no way" the phone can be fixed. (yea right).
So I see a bunch of bootloaders in the forum here. Are there specific ones that work for the GT i9000M on bell? Or since I've tried flashing gb on the phone, do I need to download one that is specific to the OS? sorry as I am quite a n00b at this.
thanks!
The 3 file ROMs include a boot loader.
The GB one for Bell only includes the secondary bootloader (sbl.bin).
Bell no longer sells the i9000m, so they are hoping you'll simply buy a new one.
Your GFs phone is a couple of months older than ours. I bet the phone is one of the ones that has the issue where the internal storage is known to fail (builds prior to 11.03).
If that's the case, I think Samsung may repair/replace it, since it's a known issue with the early i9000m phones.
Did the phone get updated via Kies recently?
thanks again for following up.
How do I test if the phone's internal storage failed?
No I have not tried to update the phone via KIES. How does this work and what will it do?
Thanks!
Going into recovery and clearing the cache might show it.
If you see an error message that it can't mount something, that would be an indication.
EDIT: What's the build code?
I can't get into a recovery mode because the phone doesn't have CWM nor can I get by even the Samsung screen when it first turns on.
How do you flash via KIES? All I can do is get the phone into download mode. Can't do anything more.
Thanks.
Boot loop on stock Bell GT-I9000M
I have the same issue and still trying to find a solution.
Can't get into recovery. From most of what I read it's the boot loader. But I may be wrong, I 'm very new to this. I flashed with I9000UGKG3-homebinary with no luck. I did not however try the Sbl.bin file yet. I can still get to the Download mode and don't want to loose that ability.
Any help would be greatly appreciated.
galaxy s vibrant GT-I9000M
Bell mobility
Stock unrooted
GB
although you do not have CWM you should have a stock recovery... I know you have probably already tried.. but try again.
Menu+Power+Volume up...release only the power button as soon as the initial screen disappears.
if you do get into this screen you can do full wipes...
--pm me if you live in the Toronto area
It also might be a boot loader problem depending on what version of of android you were on and what you tried to do with odin and if you had the right version with the bootloaders etc.....
viperm5 said:
I can't get into a recovery mode because the phone doesn't have CWM nor can I get by even the Samsung screen when it first turns on.
How do you flash via KIES? All I can do is get the phone into download mode. Can't do anything more.
Thanks.
Click to expand...
Click to collapse
As dlockhart said, you should have the stock recovery on the phone.
Since you can get into download mode, you should be able to get into recovery mode by pressing volume up+home+power button.
Flashing through Kies only works if your phone will actually boot.
Since the phone is constantly boot looping, i tried to go into the stock recovery mode multiple times with the volume up + menu + power combination. Tried releasing the power button when the words are on the screen, when it is blank, and other permutations - but i cannot get into the stock recovery.
Once i press the volume down button instead though, i can quickly jump into download mode.
Is this normal? or am i doing something completely wrong?
Is there another way to get into stock recovery mode?
Don't release the power button until you see the recovery screen.
maybe also try flashing another kernel?
Boot loop on stock Bell GT-I9000M
I have tried to get to the recovery screen also with varied timing on button presses and releases, but no luck. Vol down and power gets me to download screen every time though.
I would keep trying the volume up power and home and as soon as you see the black background with galaxy showing let go of all buttons but wait until you see it restart again. So you'll hold vol. up + power + home and your phone will restart and you'll see the galaxy words keep holding the buttons until it restarts again and when you see the words let go of all three buttons. Now if your willing to switch kernels I would go to www.darkyrom.com and follow the directions there for flashing darkyrom 10.4.2 its just as smooth as stock but its not stock and voids your waranty, but since you dont have a waranty go for it. Good luck if you need any extra help you can pm me as well. I have had my phone since Oct. 2010 and flashed atleast a hundred roms and thought i broke my phone a few times but these thing are damn near impossible to totally mess up.
Sent from my GT-I9000 using Tapatalk
Is there a minimum remaining battery-life requirement for the device to enter Recovery?
Does the 3-button Recovery require power cable to be attached or not?
For what its worth, my I9000m has a Build Date of 11.04 and came with Froyo 2.2, so unless he already updated he's definitely not on 2.3.3
Downloading Kies to your PC and updating to 2.3.3 that way, just might work. Thats what I did.

Rooted Note 1 in bootloop after update

Hi everyone. I have a rooted Galaxy Note 1. I accidentally tried to update something (the phone said there was an Android update or something) and now my phone in stuck in a bootloop showing the Android logo. When I try to reset it (volume+home+power buttons) it goes to an Odin "Downloading..." screen and gets stuck on that.
I've seen some stuff about unbricking the phone using Odin to return to the original stock rom. But from what I can tell, there are different stock roms available depending on your Country Sales Code (CSC). So apparently I need to look in Kies for my CSC to know which rom to download, but Kies doesn't recognise the phone, I guess because it's bricked. I know the phone is from the UK, but I don't know what network it came from (I bought it second hand). All I know is that it is unlocked now.
I have CWM.zip, CWM-SuperSU-v0.87.zip, and franco.Kernel-r5.zip on the micro SD card from when I was rooting it ages ago. Do these have anything to do with fixing it?
Any ideas on where I go from here? Thanks for your help.
Which volume button did you press ? You need volume up + home + power to get into recovery.
You can flash any rom from any region using odin.
Same problem
Hey,
Thanks for helping me in advance...
I used the Custom ROM (( http://forum.xda-developers.com/showthread.php?t=1970626 )) Ultimate N7000 for a long time. However this build became more and more unstable the longer I used my phone.
So I decided to go back to STOCK.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1424997
And everything went well (Odin didnt give any errors)
However after reboot... the problem began... I cant turn my phone on anymore.... It seems to be stuck in a bootloop....
How can I fix this?? please help me
Which rom did you flash? If you flashed JB, boot into recovery and wipe data. Then reboot.

Categories

Resources