[Galaxy S I9000 General] beamzuk1:
hi all thought i would share my experience with SGS semi brick in the hope that some of you would find it usefull.

firstly i would like to thank everyone in the dev community for all the information and hardwork going on out there.

secondly thanks ryanaz for the great software Z4Root and oclf they worked great (once i used them properly my own fault)

thirdly if im repeating information thats already been covered elsewhere then i apologise in advance but i couldnt find it

back to topic: stock SGS with 2.1 on tmobile uk connected to windows 7 pc

last night i managed to semi brick my phone in the following way:

1. updated to froyo using official method via kies

2. ran z4root and executed temporary root

3. ran oclf seemed to work ok but following oclf reboot i ended up with black screen and occasional vibrate with glowing softkeys if touched and nearly crapped myself as i broke my phone:eek:

from research it seems that this problem indicates a fooked partition screwing up the internal sd and logically it is probably because i used temporary root as the root is removed following a reboot so during oclf reboot memory may have been corrupted.

i have since used permananent root and oclf and it worked really well no problems

my phone does not have the 3 button recovery mode and i was gettin a bit concerned after hours trawling the net it seemed i was going to have to go for the 301k resistor jig which i didnt really fancy.

fear not i figured out a method of getting into download mode

without

3 button method or 301k jig using odin and adb commands.

its a combination of different methods for different things and it may not work for everyone but it worked for me. maybe some of the more experienced dev's can shed some light on it or refine the process.

required:

odin

pit file

rom files

adb

slight dos command knowledge (easy to find on net if you dont have it)

its important to say at this point that the phone wasnt fully bricked as the fault indicated the bootloader was intact and if the following works for you then the procedure should work.

quick check to see if it may work connect phone via usb with battery out, boot up odin, put battery into phone and switch on. if its recoverable then it will show a connection in odin in yellow with a com# (# will be a number indicating a com port. the number isnt important so long as theres one there)

if you try and flash the phone it will fail no matter what pit or rom you use as you cannot get into recovery or dowload mode.

to get into download i had a play with adb (search adb for how to use it. i hadnt heard of it before yesterday it requires knowledge of command line use in dos mainly just to navagate to the adb folder and execute adb. search dos commands if you cant figure it out and look for CD for change directory and dir for dir list)

important bit:

follow the procedure earlier to get phone communicating with odin then start adb. once in adb i used the command:

adb reboot recovery

and hey presto my phone went into download mode i was then able to reflash the phone using the normal Odin methods.

now i have my lovely phone with a faster operating system, streamlined rom and root access happy days.

just as footnote i had never messed with android before yesterday as i had always been on windows mobile so with a bit of research its amazing what you can learn. and i know this guide isnt very n00b freindly but its how i best remember it from last night after searching various things for 5 hours(ive slept since then) if any of it is incorrect then i apologise in advance but ive left it intentionally vague as the experienced dev's will know what im talking about and the n00bs(like me yesterday) it wont hurt you to go and research the topic and you might learn something instead of just posting questions all the time

peace out

p.s. forgot to mention ensure that you kill any kies processes running on your pc before attempting this and ensure you have internet connection so windows 7 can obtain drivers if required. xp or vista may require drivers to be manually installed though not sure