Database Users

Please Help. Can't get past white Samsung Vibrant Screen.

I followed the instructions from here ( http://forum.xda-developers.com/showthread.php?t=743769 ) up until flashing the actual zip and forgot I put the zip on my external sdcard rather than "internal" sdcard. Now my phone won't get past the initial white Samsung Vibrant screen. Also, I can only get into stock recovery. After clicking "reinstall packages" it just reboots and brings me back to stock recovery. Please help. Thank you.

You will need to flash back to stock then you will have access to your phone again.. you will have to start over to flash that rom. after you flash back to stock using odin
use this thread
http://forum.xda-developers.com/showthread.php?t=734475
You will need the right windows drivers so Odin will see your phone pick them up here.
Windows 64bit
Windows 32bit
Directions posted by setzer715
1. Put your phone in download mode by plugging it in and then holding Vol Up+Down and Power. As SOON as the screen goes black release power but NOT Vol Up+Down.
2. Launch Odin
3. Unplug your phone.
4. Load the pit and pda files into odin.
5. Plug your phone back in. You should now see one of the small blocks turn yellow and show you the com port. If not, something is wrong with your drivers.
6. Click start. If it flashes, great. If it hangs at File analasys then repeat 1-5.
6a. If Odin hangs at cache.rfs then move on to 6b.
6b. Unplug your phone (Odin will say it was removed) and remove the battery. DO NOT SHUT DOWN ODIN!!!!!!
6c. Put the battery back in and plug it back into your computer and put it back into download mode using step 1.
6d. Press start on Odin and it should now flash.
Also if you continue to hang at cache.rfs I found that if you delete s1_odin_20100512.pit then copy a new copy of the file over to your odin directory it seems to work fine after that.

Damn it.Thanks....

vol dn+up should get you to the stock recovery util right? the yellow and blue one?
edit: nvm, scare is over lol

On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.

bumpbumpbump

$iMoney said:
On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.
Click to expand...
Click to collapse
You need to delete your s1_odin_20100512.pit file and then extract a new copy to the odin folder then flash again. happened to me and that is all I did to fix it. step 6d did not work for me has well.

Hmmmm it's still not working. Would it help if i made a video showing what i'm doing then you can look it over and tell me if I'm doing something incorrectly? Also maybe I should be more clear. There is no way for me to start the flash again after removing my device as per step 6 without having to completely restart odin, thus restarting the process.

Update: Still not working. Really need a fix for this. Is there another way to un-brick my phone?

EDIT: To clarify, my problem was getting stuck as Cache.rfs and never going past that. I did try the previous steps listed in this article, as well as trying to reinstall all drivers and even using different Odin copies from other threads (even though they were all the same Odin 3). No .pit file seemed to work for me. Also, I'd like to point out that I have this issue with my netbook, but my work computer where I've done all my Odin flashing before did not have this issue, and I could use the .pit files perfectly fine.
First off, I'm not anyone special (I guess depends on the meaning of special), I don't dev... I play around. That's all. So take this all with a grain of salt.
I had the same issue, and have spent all night trying to fix it. Just now I didn't use the .pit file at all. Just the .tar in the PDA slot. Immediately went through and reflashed everything and I am fully up and running.
I can't guarantee that I don't have some kind of issues now but I am now back at my home screen and the phone seems to be operating fine.
The files I used are as follows:
Stock 2.1 firmware for the Vibrant: http://forum.xda-developers.com/showthread.php?t=739091
Samsung studio 7 (seemed to get Odin to recognize the phone without having to disconnect and reconnect, thought it might have something to do with the issue, though not sure): http://www.4shared.com/file/117435710/3d286573/Samsung_PC_Studio_72249.html
And the Samsung USB Drivers: http://forum.xda-developers.com/showthread.php?t=728929
Now, if a real dev can tell us what happens when you don't use the .pit file, we can know if there is any longterm repercussion from this. Short term though, working like a dream. I hope this helps, because being stuck without a working Vibrant sucks!

ODIN is a pain but I've found a way to get it work pretty consistently for me. Whenever you flash a ROM or back to stock, always make sure you enable USB debugging, and have adb working on your computer.
Open up your command console, plug in your device, open up ODIN, and type "adb reboot download". ODIN should recognize your phone when it restarts and a COM will light up.
From my experience, ODIN recognizes the devices better this way and hasn't hung for me so far (granted it's only 3 times). When I was booting into download manually and then plugging in the USB, it would hang at cache.rfs. If you don't have USB debugging enabled, then only thing you can do is keep retrying over and over. Took me like 15 tries once before it finally ran.

Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.

hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?

$iMoney said:
Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.
Click to expand...
Click to collapse
which firmware did you use? did you use the true stck 2.1 firmware?

tq745 said:
hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?
Click to expand...
Click to collapse
It should go right away. If it's hanging at cache.rfs, then it's not working. I really think its a drivers issue with ODIN. Just keep restarting your phone and ODIN and retrying.

I used the tar file that is linked to from the second post on this thread. I didn't even download what you linked me to, I just didn't use the pit file, like you told me and it worked with the files I already had.

My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?

ahhduy said:
My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?
Click to expand...
Click to collapse
how are you trying to get into download mode?

skater4690 said:
how are you trying to get into download mode?
Click to expand...
Click to collapse
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.

ahhduy said:
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.
Click to expand...
Click to collapse
ok try this...
1)plug into a usb with power
2)wait for the battery to show up
3)hold power and both volume buttons
4)wait for the vibrant screen to flash twice it will go once then seem like it turns off but then pops up agian
5)after it turns off the second time release the power button but still hold the volume buttons and you should be in download mode now
REMEMBER TO HAVE THE USB PLUGGED INTO THE COMPUTER AND YOUR PHONE!!!

People with hardware locked vibrants..

What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?

Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.

You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App

jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*

TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.

Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.

I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.

Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA

demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.

I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10

How do you know whether you have a hardware locked Vibrant or not?

No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).

johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk

Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?

finally from Samsung How to Solve the Black screen (death screen )

after mailing SAMSUNG by Mr.Alzubair
from ce4arab website
about the Death screen
this is the answer :
-----
Dear Alzubair ,
Thank you for contacting Samsung Electronics.
Reference number:2104286715
Regarding your case, kindly note that the image you have displayed on
the screen of your phone, indicates that the device has entered the
Recovery Mode. The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
In order to get out of the Recovery Mode, please follow the steps below:
Recovery Process
1.Remove the battery and reinstall it. Power On your Phone
- Phone display “Connection picture for Phone to PC”
2. Recovery Mode in Kies
If upgrade failed in upgrade step, you can see next Pop-Up
- Select "Yes”
Firmware Upgrade program progress to recovery mode.
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
5. Click “Next”
- Firmwareversion display
- Firmware file is downloaded to PC
6. Firmware update
- After Firmware downloaded, Click “Next”
- Firmware update start
Caution
- Never disconnect or turn off the
device in thisstep
- If so, recover the phone refer to
recovery section
7.Complete
- After Firmware update complete, the device reboot
automatically
- Click “Next” Button
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.​
I hope this has been of some assistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-4286715
reference number.
Kind Regards,
Aya Smith
Samsung Electronics UK
Customer Communication Centre
Tel.: 0845 726 7864 (All calls charged at Local Rate)
Homepage: samsung.com
[Product] GT-I9000

The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
Click to expand...
Click to collapse
Bwahahahhaahahahahh!!

cheetah2k said:
Bwahahahhaahahahahh!!
Click to expand...
Click to collapse
LOL XD
at least they help me
I just tried it ( by the Manual way ) and it Works

so this works on the semi-bricked, no 3-button combo enabled phones ??
.. let's say, after a bad/failed bootloader flash ?
someone please confirm ?
later edit:
from what I understand after reading this, Kies can force any (Phone--!--PC) SGS into recovery and/or download mode?
if so, can we "extract" this feature and make it into a stand alone solution for half-bricked phones?

That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.

franklin01 said:
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
Click to expand...
Click to collapse
Some SGSs can't access download mode from that screen because of the proper bootloader that's missing. (3 button combo fix needed, not so safe)

wish samsung also adds a feature to kies that fixes the IMEI =D

franklin01 said:
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
Click to expand...
Click to collapse
2day i triad it two times and it works
but from what i understand same thing happened to me today ..
i did the 3 times flashing way :
BE SURE THAT YOU disconnect THE CABLE!!
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
Then its work and downloading mode appear i installed an official Ver. by odin ( check on Re-Partition ) then it will work (work for me after the same thing that happened : No possibility to power on, no charging, nothing. )

Does this means that the phone has a secondary bootloader or what I dont get it, I already sent my phone to samsung so I cant try, I had my phone bricked stuck at a black screen after the S logo.

hang on... so it sounds like samsung is saying that phones that dont go into download mode straight away from vol-down, home and power need to keep holding the power button until the power cycles 2 times, then let go on the third?
i cant test it now because after i bricked my phone (black screen no power on or charge) i sent it back and i got a new motherboard with 3-button enabled... but this does make sense because when i had a 3-button disabled phone previously i did manage to get it into download mode from the phone-!-computer screen by trying different timings. it took a long time but eventually worked.
so it would seem if this is the case, that it is just a different boot loader and a different key combination to access download mode, but working nevertheless?
can someone test this?

Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App

stephengoo said:
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
We already knew it had a secondary boot-loader...
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions
This is what is patched to hotfix the 3BR in disabled phones.

3 times flashing way wont work for me, and at Recovery in Kies i cant see my Device!
Absolutly no USB!!!!
Sorry Guys!

So this forced download mode can be possible...
This guy here tried hard to explain same thing:
http://forum.xda-developers.com/showthread.php?t=812933

do you think it will work with korean version galaxy s?

No-Exit said:
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.​
[Product] GT-I9000
Click to expand...
Click to collapse
"all information has bee verified" means put phone in download mode and connect it to PC (can't do it without working 3 buttons combo).
"manually instead of using Kies" = same thing, doesn't work without 3 buttons combo.

This doesn't works if you didn't have 3 buttons combo enabled. I used heat trick instead and then patch aires P-SBL.

I sent my phone back because of this black screen of death. I could get into Download mode, and the other (vol-up) mode too, but no upgrading or changing firmwares worked to fix it. And Kies didn't see it, though Odin eventually did.
Wondering now if the Black Screen of Death was fixable after all, but then would Kies have to recognize it first?

I have a phone ! pc bricked phone right in front of me, I've tried this and a million other combinations, nothing works. I'm not being super pessimistic or anything it really doesn't work. I've left it with a phone repair store overnight and they couldn't fix it either. Im going to visit samsung/optus tomorrow.
edit:
I also want to point out that that message contains some horrible english supposedly from samsung UK

d47:
I am exactly in your shoes. Even with the overnight leave at a GSM repair booth-thingy. Im also considering handing it back to the retailer, but havent tried the heating up trick yet... Maybe its worth a try ?

[HELP] SGH-I337M Boots first into D/L Mode

I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!

shroomun said:
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
Click to expand...
Click to collapse
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.

Jdiesel87 said:
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Click to expand...
Click to collapse
So did you go into settings, more, developer mode to check usb/debug?

USB debugging isn't required to flash the Odin MD5. One thing I did notice is that you should boot into Odin download mode before connecting your USB cable. I was having issues with Odin not detecting my phone and waiting to connect the USB cable solved that.
Sent from my Nexus 7 using xda app-developers app

sloanster said:
So did you go into settings, more, developer mode to check usb/debug?
Click to expand...
Click to collapse
Duh...
I was referring going to adb fastboot

see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging

shroomun said:
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
Click to expand...
Click to collapse
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..

TheAxman said:
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
Click to expand...
Click to collapse
Nothing is wrong with the pins, USB is working fine and can be used in any other mode. I got ADB finally, I guess it was just not playing nice with me before. However, still anything I try the bloody thing still insists on booting first into download mode.

Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?

shroomun said:
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
Click to expand...
Click to collapse
I have seen this elsewhere, one guy suggested, using Keis, and it took him 2-3 times to get the stock to stick.
As far as checking those items in odin, could brick the phone. he also said, he got nowhere using odin in this situation.
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
I can imagine your frustration here...good luck.

I did try Kies and it would keep getting stuck at 10% (I let it sit overnight) so I had no luck with that...
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
Click to expand...
Click to collapse
Yes, I have gone from stock recovery to CMW and back to Stock and still nothing. As for you other question, yes, I can boot into Android. The downside is I can't turn the phone off unless the battery is pulled out. This is why I bought an HTC One and not an S4 lol .. thank god this isn't my phone, but it is frustrating because of all the things I've tried to do to fix it.

Odin flash failed, stuck in Emergency Recovery screen, cannot turn off.

I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.

fastzombies said:
I was going along ok until I made the fatal error of transferring the Magisk patched file to PC via MTP instead of taking the time to re-learn adb, which must have corrupted it. Thus predictably Odin hung and I am in trouble.
Where I am stuck is being unable to turn the phone off to come back in download mode to start over with stock firmware. I have been unable to find any secret button presses, and the battery doesn't seem to want to die leaving me with an $800 paperweight.
I did search around for this first and didn't find any real answers. Has anyone found an effective solution to this problem? Thanks.
Click to expand...
Click to collapse
If Odin recognizes you device, you can flash firmware in emergency recovery.

Cindysmith0994 said:
If Odin recognizes you device, you can flash firmware in emergency recovery.
Click to expand...
Click to collapse
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.

fastzombies said:
Thank you, but the PC won't recognize the device. What does happen is the emergency recorevy screen tries to come up. I tried starting in download mode with bixby+vol down then USB. I did get the battery low enough where I don't get the teal screen of death anymore, perhaps it is too low for USB to work? What I was hoping for was the charging animation but no luck. Surely this is just a software problem and there is a way out.
Click to expand...
Click to collapse
Did you try getting into recovery and perform a data factory reset and then see what happens?

Just load the stock firmware BL, Ap, cp and home csc into Odin if you see emergency teal screen. The emergency screen will start loading
Black screen ....Perhaps your battery is dead?

Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.

fastzombies said:
Thank you all for the replies. I had let the battery get low in a misguided attempt (based on advice elsewhere) to get it to shut off. I had to let it charge a while for it to wake up enough for PC to see it. Then I was able to flash in Emergency Recovery mode.
Thank you for the help.
Click to expand...
Click to collapse
Glad you got your device up and running ?

Maybe someone can help me. I seemed to have borked my phone. I kept getting "Google is Stopping" with no way to fix it, so I tried reflashing my firmware in odin. After I loaded all the files and hit start, I realized I didn't untick auto reboot, so I tried aborting the installation and ended up with screen (I've had it before and got out of it by still flashing in Odin, but now, if I try to reflash firmware while in this screen, it's stuck on SYSTEM in odin.
Any help appreciated!

Try this
That is where I got stuck. Are you trying to flash stock or patched firmware? I had to start over with stock as I copied the patched via MTP instead of adb and it got corrupted.
I think what I did was unplug and reset Odin. Wait for screen to turn off, then make sure it is at least 80% charged. Then Bixby + Vol Down + plug in and you will go back to this screen. Then I was able to flash stock. I had to go so far as to re-lock bootloader and flash stock again since my "OEM Unlocking" was not just greyed out but missing. Since then I've had no time to try again, but at least I have a working phone.
This is my anecdotal procedure, can't say if it is the right or best one.

Hi All,
I was trying to flash the latest firmware for my device (G9750ZCU2ASG4) and during the odin process, my computer restarted which failed the update halfway through. I rebooted the computer, tried again, and it was trying to establish a connection for a really long time, so I disconnected my phone from the USB port on my computer, and held Power and Volume Down to try and force reboot the phone. I was going to try and go back into download mode to restart the process. My phone mentioned something about needing to do an emergency recovery, but I continued to hold down the power and volume down keys and then everything went black on the phone.
I've tried multiple USB cords, all of the button commands known for the device, and have even tried to perform the emergency mode recovery on my device, but it seems like it's in some sort of locked state; What I mean is the phone is stuck on a black screen. I can't "boot" into recovery or into download mode. The phone doesn't even vibrate when I hold the power button or power and down to try and force reboot it. Odin doesn't recognize the phone when I plug it into the computer nor does the device manager on my windows computer.
Does anyone have any experience with this sort of issue or any idea of what else I can do to try and get into download mode to flash my firmware again? All help, suggestions, or comments regarding this are much appreciated.

Sounds like the battery is dead

Hi Dude, I am struggling with the same problem, read this post and it came to me, had to come back and give you the solution.
Press bixby+volume down, IMMEDIATELY after the screen goes off, hold volume up and down while connecting the USB cable super fast.
You have got like 10ms to do it
Otherwise it just goes back to the AVB FAIL screen

Ran into this issue, none of the above worked for me.
This is how I resolved:
1) Placed phone on wireless charging mat and let it boot to emergency recovery screen
2) Load TWRP into AP slot of Odin and leave the window open on your computer ready to flash
3) Connect phone to computer whilst it's on the mat and press start in Odin as soon as your device appears
It may fail a few times but if your quick you can install TWRP.
4) Now boot into recovery and let your phone charge to a reasonable level (above 20%)
5) Boot into Download mode and flash your desired rim via Odin