yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] almi88:
Ok... so I see that some of you who tried this fix ended up with a bricked phone... Now I have a question... How do I know if my phone is branded? I bought it from OrangeRO and it is locked on network... model number GT-I9000 firmware 2.1-update1 baseband I9000xxjm1 kernel 2.6.29root@SE-S603 #2 build number ECLAIR.XFJM1
[Galaxy S I9000 Android Development] Hemix:
Mine is gone now ;)
[Galaxy S I9000 Android Development] aboad20:
T-Mobile phones will Bricked if you use any way to fix the 3 combo issue
[Galaxy S I9000 Android Development] ashmodai:
:( Just talked to the shop and they indicated that the warranty roundtrip would take around 2 to 6 ... weeeeeekkkkkkkssssss..... arf .... let's see the positive side of things it could come back with froyo after such a period ......
[Galaxy S I9000 Android Development] mynimycu:
sal spunemi si mie ce inseamna "a bricked phone"
[Galaxy S I9000 Android Development] nayket:
HELLO , somebody tried the asian version with stock i9000dxjg4 ? i'm afraid to take risk since my phone has no warranty , any advices please ?
[Galaxy S I9000 Android Development] Richthofen:
For those who have bricked their phones:

Which was the original firmware version (shipping firmware, when you received it) of the phone?

Also which version you had installed when you updated the bootloader?

PDA / CSC / MODEM (e.g I9000XWJM2/I9000OXXJM1/I9000XXJM1)
[Galaxy S I9000 Android Development] tylerham:
Is the only difference in this to enable the 3-button recovery & download?

Or are there any other changes in this (perhaps quicker start up or something along those lines)?

Is there any point at all in using this if the 3-button combo works fine?
[Galaxy S I9000 Android Development] mengsuan:
Are the bricked phones only the T-mobile version so far?
[Galaxy S I9000 Android Development] s4int:
nope...only fixes 3-button combo
[Galaxy S I9000 Android Development] Richthofen:
Zero bricks reported so far with this method...
[Galaxy S I9000 Android Development] Moxen21:
Does this mean by now we know whether or not the problem is in the hardware or not?

If I bought now a phone and it has the 3br problem, should I return it or can I rest assured that once I fix it, it is permanently fixed?
[Galaxy S I9000 Android Development] BlueTorch1234:
is this new SBL permanent?
[Galaxy S I9000 Android Development] Richthofen:
No SBL is permanent if it is overwritten by a faulty one.
[Galaxy S I9000 Android Development] Richthofen:
Like said before, it has never been a hardware issue.

No matter if the phone had the proper bootloader from the factory (ie 3-button wake supported), the feature can be disabled by flashing in bootloaders which do not support the feature. Tried it with my own phone, and it got disabled.

The firmwares which will disable the 3-button wake feature can be counted with the fingers of single hand. The future "low" releases will also have a working bootloader in them.

Also I will include these bootloaders to all the future releases.
[Galaxy S I9000 Android Development] barach:
I have

PDA: I9000XWJM2

PHONE: I9000XXJM1

CSC: I9000OXXJM1

if someone can tell me what do I do?? is there any chance to have a download mode and recovery?
[Galaxy S I9000 Android Development] aelbali:
@ Richthofen

Has the device to be rooted to use the newest method

EDIT !!!!

Root is not required !
[Galaxy S I9000 Android Development] spark001uk:
@Richthofen:

Quick question- as most people here who apply this fix will probably go on to flash the official froyo using Kies when (finally) samsung release it, can you see that causing any problems?
[Galaxy S I9000 Android Development] georgehdd:
Hey,

Is the new method safe to use on Win7 64 ?

And is it permenant ? or my phone might be reverted back sometime and the 3 button recovery will be disabled again ?

Sorry for the noob Q. btw :)
[Galaxy S I9000 Android Development] Richthofen:
Unless Samsung releases the Froyos with broken bootloaders, nothing will happen.

In the worst case you have to apply the fix again, but it is highly unlikely.
[Galaxy S I9000 Android Development] Richthofen:
Start Odin3 with admin priviledges and you will be fine.
[Galaxy S I9000 Android Development] aelbali:
Guys never mind, I tried it even without a rooted device and it was a complete succes. For all other people who are still hesitating, I myself couldn't do it because I was realy scared in turning my sweet baby into a brick, but I was also really frustrated I couldn't flash any firmware because I had the old JM2 and really wanted a JM8. So I took the risk and tbh after all it seems less scary than you think. The flashing was taking about 3 seconds and it was ready and fixed... Everything is working fine now !!

Big thanks to Richthofen... I really appreciate your work for the community.

Once again thank you !!!
[Galaxy S I9000 Android Development] barach:
i have

PDA: I9000XWJM2

PHONE: I9000XXJM1

CSC: I9000OXXJM1

so what can i do ? can i downgrade my firmware and apply your 3-button combo fix?
[Galaxy S I9000 Android Development] Richthofen:
http://xdaforums.com/showpost.php?p=8395140&postcount=752
[Galaxy S I9000 Android Development] gbohm:
I'm thinking about fixing it also but my sgs is my work phone so it has sensible data on it. ...

What do you think could an official build (custom roms or betas\rc are a no go on this one) brick my phone with an high propability?what is the more resonebal decission applY this fix so i can recover it if the official froyo update fails or just stay on the official road?( guess my n1 is my toy ;-) )
[Galaxy S I9000 Android Development] georgehdd:
@ Richthofen Thanks for the fast reply :) !!!

I forgot to ask though, will it work if my device is rooted ? are the requirements stated in the first thread the only requirements (+ the running of ODIN3 in admin mode) ? oh & which version of ODIN3 to use ;) - 1.00 or 1.30 ?
[Galaxy S I9000 Android Development] Blackbeer:
Hi,

I am new here and have read a lot of posts about the 3BF. My english is not my mothers language so I am not sure I understand everything correct, so please forgive me my question.

My german Ex-O2-branded phone has the following config after flashing with Kies to JM1 and then JPH:

I9000XXJPH/I9000OXAJPH/I9000XXJPH/I9000XXJPH

and ProductCode: GT-I9000HKDVIA (O2)

Is it ok to flash my phone like described by Richthofen today in post #752 or have I to change anything before.

Sorry for my bad english, I tried my very best, guys!

Thank you for help and Richthofen for his excellent work

Andreas
[Galaxy S I9000 Android Development] Moxen21:
is there any place with an explanation or a guide on how to use the riff box?

Thinking to buy one as a precaution but no idea if its simple enough to use..
[Galaxy S I9000 Android Development] =Oberon=:
Im sure this has been asked before but its a long thread so...:D

This 3 button fix update/ZIP worked for me.

(Optus

PDA: JG4

Phone: JG3

CSC: PSJG1)

What I wanna know is when the time comes we can update to official froyo through Kies wont the fix be over ridden and need to be applied again?
[Galaxy S I9000 Android Development] martyc0:
Has anyone tried and succeeded using Richthofen's fix with such a phone?
[Galaxy S I9000 Android Development] mengsuan:
I used Windows 7 x64. It's all good.
[Galaxy S I9000 Android Development] coradux:
Samsung Galaxy S Orange Romania locked

PDA: I9000XFJM1

PHONE: I9000XXJM1

CSC: I9000OXFJM1

Applied last method -- SUCCESS!!!

Big thanks, Richthofen!!!
[Galaxy S I9000 Android Development] valentine8381:
:D I tried and succeeded in fixing 3-button.

My phone is Australia Optus.

PDA:I9000DTJG4

PHONE:I9000DTJG3

CSC:I9000PSJG1

THANKS A LOT!!! You are my hero today, Richthofen !
[Galaxy S I9000 Android Development] gbohm:
Any results for an german unlocked unbranded sgs with android 2.1-update 1 (basic shipped software)(windows7 ultimate 64 host)

Push to my question above

Thank you
[Galaxy S I9000 Android Development] Indicative:
Any reports of bricks?
[Galaxy S I9000 Android Development] ijat91:
no brick yet..

for who cannot enter the recovery mode after the flash, you should try it back, mine actually don't work at first but actually i'm not hold it properly. My phone can enter the recovery mode with volume up+home+power but i have to released the power button completely after the galaxy s start up menu appeared, if not it will turn turn black and enter back the galaxy s start up menu, again and again...
[Galaxy S I9000 Android Development] manosv:
Sorry to tell but mine didn't go as planned.ITS a BRICK now.

PDA	I9000XWJM2

Phone I9000XXJM1

CSC	I9000OXXJM1

with u3 in the bml1

It happened with the latest method.
[Galaxy S I9000 Android Development] barach:
so Richthofen what should i do? i have same firmware as manosv. Can you check it out? there is any chance that it worked on this firmware without any downgrade or something?
[Galaxy S I9000 Android Development] spark001uk:
Sounds like there's definitely something funny going on with JM1 then. It seems to have featured in all the problems so far.
[Galaxy S I9000 Android Development] Stain33:
pda - xwjm2, phone - xxjm1

Richthofen pls tell me - my phone from germany

PDA - i9000xwjm2

phone - i9000xxjm1

сsс - i9000xxjm2

my phone unlock this patch?

there is phone no. two

first is bricked - but unlock from KIES

i'm realy affraid but in my country serice cetres is no recover bricked...
[Galaxy S I9000 Android Development] distortedloop:
I hope you'll include releases that don't touch pbl and sbl as well. No sense in messing with those if they're already a working version, right...?

Thank you for your continued support to we lowly users! ;)

Now, if only you had a pbl sbl combo for the US Vibrant model, my mate would be in here thanking you as well! LOL.
[Galaxy S I9000 Android Development] manosv:
DONT do it my friend.Enjoy your phone as it is for now.Wait a liitle longer
[Galaxy S I9000 Android Development] MarkVibrant:
Battery died, and now phone goes black after S logo

Hey guys, I've got the Bell Vibrant and went through the process of getting it onto the Rogers network.

Today the battery on the phone died completely. I recharged the phone to a full charge (The green battery meter works fine) but when I go to turn the phone on, it gets as far as the swirling S logo but then goes black - sometimes the to soft keys stay lit white. The phone is unresponsive at this point... Only battery pull seems to get it back to at least showing the battery symbol when plugged in.

The problem is: Kies won't recognise the phone. It detects it for a moment but disconnects with a dialog saying: "Reconnect the device on Samsung Keis(PC Studio) mode. Kies does not support this connect mode."

Because it's a Bell Vibrant, I have not been able to find ANY combination of a three finger salute hat will work, and have tried many variants of holding various combinations of buttons. Nothing works. And I'm not willing to put it in the oven and cook it (like one post on a forum somewhere suggested).

adb does not seem to want to connect either.

Any ideas of how I can at least get that far, so that I can follow the instructions from this post to get the three finger salute working?

Any help is greatly appreciated. I'm kind of worried, as it's a Bell phone, but I'm not with Bell, and now that I can't get it "back to factory standard" I doubt they will take it back.
[Galaxy S I9000 Android Development] Indicative:
Tried the fix with no success. In cmd the used adb and typed the download mode command, nothing happened and the phones screen went black. So I unplugged the usb cable and battery then tried turning the phone on. Luckily it said download mode so I plugged it back in and flashed bootloader with odin. The phone functions as normal but I still can't enter recovery mode.

<ID:0/008> Initialzation..

<ID:0/008> Get PIT for mapping..

<ID:0/008> Firmware update start..

<ID:0/008> boot.bin

<ID:0/008> Sbl.bin

<ID:0/008> Removed!!

<ID:0/008> Completed..

<ID:0/007> Removed!!

Is there anything wrong with that?

EDIT: Ok now it boots into recovery, seems like I have to let go of the power button. Thanks Richthofen you're a genius.
[Galaxy S I9000 Android Development] Stain33:
manosv

thanks for advice, in my country this phone - start sale 25 sept - support = 0,

and i by this phone from another country, with recovery the bricked experience = 0. service center unaware what do with bricked! i hope what problem be solved!
[Galaxy S I9000 Android Development] barach:
I have the same firmware as monsov and i took the risk. fix worked for me :) thank U Richthofen!
[Galaxy S I9000 Android Development] Stain33:
pls tell what firmware you have?
[Galaxy S I9000 Android Development] barach:
post # 793
[Galaxy S I9000 Android Development] TNStrangelove:
I'm sure this has been asked before but this is a long thread. Following the Guide in the OP what connection mode should the USB use? i.e. Kies, Mass Storage etc.
[Galaxy S I9000 Android Development] distortedloop:
None of the above.

You'll want the phone in DOWNLOAD MODE, which means the connection mode options you're talking about aren't available to you. Check instruction #6 (6. Type "adb reboot download" to the command prompt and press enter.).

You'll recognize download mode by the large yellow android exclamation point screen that says "Download Mode" and "don't turn off target" or something along those lines. ;)
[Galaxy S I9000 Android Development] TNStrangelove:
Thanks, so this mode overrides whatever mode the USB is in when connected in step 4? and can be done over any mode?
[Galaxy S I9000 Android Development] georgehdd:
which version of ODIN3 did you guys use ? 1.00 or 1.30 ?

Any bricks so far with the new way ?
[Galaxy S I9000 Android Development] distortedloop:
Ah, yes, I see your confusion now!

Yeah, for the first four steps, just make sure debugging mode is on (I actually never turn it off on my androids), and don't worry about the other usb modes unless you're usb storage is mounted as readable by the computer, in which case I'd turn it off. You probably don't want your phone's usb storage mounted to the computer when you do the reboot just to make sure you get a clean shutdown of the filesystem on it, although reboot should do it right, why take the chance?

Once you do step 6, the other modes are irrelevant, as they're not available to the phone at that point to the best of my knowledge.

Good luck.
[Galaxy S I9000 Android Development] varunkumars:
Type cd to change the directory. I didn't know this. This is only for dumbs like me. I did google to figure this out.

C:\Users\MUNNI>cd C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools

C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools>adb reboot download

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools>

C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools>adb reboot download

C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools>

C:\SDK\android-sdk_r07-windows\android-sdk-windows\tools>
[Galaxy S I9000 Android Development] Kel Ghu:
Followed the instructions and it worked!

Unlocked GT-I9000 Swisscom branded (Switzerland) with stock I9000XXJM1 firmware.
[Galaxy S I9000 Android Development] dave1977nj:
Any chance of this getting worked on for the captivate?

Thank You.
[Galaxy S I9000 Android Development] Stain33:
Guys please specify the version of firmware without depending on that successful or unsuccessful was an attempt.

& great thanks that who did it already!
[Galaxy S I9000 Android Development] aesaez:
Hello. On Friday, my phone died with this method. No brick, dead.
[Galaxy S I9000 Android Development] manosv:
Mine too.It only shows the phone and computer icon with the excalamation mark.Its on service now
[Galaxy S I9000 Android Development] davor175:
Hey guys, I need some info:

- What is adb and how to make it available?

- How to access command prompt?

Thanx! :D
[Galaxy S I9000 Android Development] flaneur:
Hi there!

Yeap, tried it one week ago and got a nice brick. The phone was not network unlocked at the time I tried it, I kind of assumed that was the reason, but I found no evidence of it. I have a new one (branded, unlocked, gt-i9000, XXJM3 & XWJM6)... and don't know if it is safe to retry, even now that there is a new version of the bootloader and with the phone unlocked.

Anyone else from TMN around? Any help on this?

Cheers
[Galaxy S I9000 Android Development] danchappers:
Worked wonders, first attemps (thats after I realised I needed the SDK oops)

Thanks a bunch I feel happier now :)
[Galaxy S I9000 Android Development] spark001uk:
Looks like JM5 method still the only safe bet then?
[Galaxy S I9000 Android Development] georgehdd:
whats JM5 method ?
[Galaxy S I9000 Android Development] spark001uk:
Look for Dadonali guide in this thread.
[Galaxy S I9000 Android Development] Moxen21:
there were no bricks with it?
[Galaxy S I9000 Android Development] shisux:
Just installed this. Everything seemed fine. The phone bootet up ok after the installation.

I booted into download mode once to check the fix worked. It did. Rebooted again to make a phone call:

I get the boot animation, but no sound. I don't think much of it, until 5 minutes later, the screen still shows the galaxy s logo with the pulsing "S". I figure I'll give it a minute, come back in ten minutes but nothings changed. At about 15 minutes the phone shuts down by itself.

So the phone's not bricked, but I can't boot it up.

EDIT: I'm rooted and have RyanZA's one-click-lagfix installed, I'm guessing something with the new bootloader and the lagfix makes the phone unbootable.
[Galaxy S I9000 Android Development] tatobrutto:
Everything OK. Removed SIM and SD card

Used updated method of 10/02/2010.

T-Mobile branded. Operator: Orange Switzerland

My SGS is:

PDA: I9000BOJG3

PHONE: I9000BOJF1

CSC:I9000GDTMJH2

A big thanks Richthofen and Dadonali
[Galaxy S I9000 Android Development] Wesie:
Does someone has try it on a Vibrant?

Kies shoes me only JFD as SW.

The code *#1234# does not work :(

Its a T-Mo branded one...
[Galaxy S I9000 Android Development] gehzumteufel:
I am afraid to. I don't want a brick. There have been enough bricks on here already.
[Galaxy S I9000 Android Development] distortedloop:
f

OCLF causes more problems for people than it solves in the long run, imo.

Most of the lag fix methods should probably be removed before trying things such as flashing new boot loaders, if for no other reason than to make sure you have the least complicated system running before doing major surgery on it.

You don't get far enough into the boot process with that S showing to have adb active? A lot of times you might get that far.

I wouldn't try this on the Vibrant with the files provided in this thread. The concept will probably work, but we'd need a known good working and compatible pair of pbl and sbl images to flash.
[Galaxy S I9000 Android Development] Indicative:
Click Galaxy S I9000 Android Development and look for the sticky topic

[REF] BIG FAQ! {Flash/Root HOWTO} {ADB&Tutorials} {T&T} {FW-Guide} [MUST READ!]
[Galaxy S I9000 Android Development] Damia_:
I have

PDA: I9000XXJM1

PHONE: I9000XXJM1

CSC: I9000OXAJM1

Its save to apply this fix?
[Galaxy S I9000 Android Development] daneysim:
Hi, I am experiencing a very scary trouble. I wanted to fix the 3 button issue described here but the operation of Odin got stucked (at least it seemed - diasabled buttons, no action) and after one hour I didn't see any other chance than to unplug the usb cable. Since this my phone can not start at all. If I switch it on I see two flashing yellow icons illustrating a handset - pc connection. It disappears only when removing battery. I tried lot of things, every key combinations + removing the battery for longer time, but no luck. What could damaged in such situation? Is the any chance to repair it somehow? One friend called Samsung and got the answer that such actions violate the varranty and can cost even up to EUR 200...:-(
[Galaxy S I9000 Android Development] OttomanFD3S:
New member here,

here's my story:

bought the phone yesterday..(OEM non branded retail phone phone)

discovered the 3 button mode doesn't work.. Gutted that I couldn't update to 2.2 I decided at least I can lag fix it

using this site: tiagoespinha.net/2010/08/samsung-galaxy-s-lag-issue-and-how-to-fix-it/

I sucessfully rooted it using the update.zip patch

I then installed the 2nd patch.. and when I ran the script and all hell broke loose..

started getting all kindsa force close errors when running apps..

the phone kept getting worse and worse till it was unusable a couple hours later

rebooting the phone then bricked it..

without a restore/downloading functions possible my hands were Tied :(

so this morning I took it to Samsung, they flashed it for me.. strange thing is, it's not the same firmware that I got outta the box... I think it's an older one?

outta the box:

PDA:I9000JPJG8

Phone:I9000JXJG2

CSC:I9000JPJG9

Now:

PDA:I9000JPJG1

Phone:I9000JXJF3

CSC:I9000JPJG1

KIES tells me there's no update available for my phone :S

I really don't want to be back to a doorstop for a phone (my iphone is currently bricked at the moment as well the day i was selling it to buy the galaxy too DOH)

are my versions genuinely older as I suspected?

is it safe for me to apply this patch and then start tinkering with Froyo?

Thank you
[Galaxy S I9000 Android Development] s4int:
Don't tell Samsung what you really did! Send the phone back to Samsung for repair. If they wanna know what happend you tell them that kies crashed while flashing the phone or something like that. It's not uncommon that you get a brick while flashing with kies. I'm pretty sure that they don't even try to figure out what really happened.
[Galaxy S I9000 Android Development] [Ramad]:
Try this: http://xdaforums.com/showthread.php?t=784704&page=4

Do as post #34 and you will have the 3-buttons working and then you can flash to whatever ROM you want, just make sure that you don't flash back to an old firmware as some of them will re-disable the 3-buttons download/recovery, this is what I used on my phone.
[Galaxy S I9000 Android Development] daneysim:
you mean "firmware upgrade" option of Kies as flashing. The problem is that in my case it displayed something that "new newer version to upgrade to" as already had the latest 2.1. So they can easily reject my argument saying that this happened due to firmware upgrade.

I bought in Internet, I already contacted a Samsung service point and they told me that it must have caused due to inproper pc - handset usage by me meaning it is outside the varranty scope. I assume "sending back to Samsung" means submitting it at an official service point of Samsung - or is there something direct channel?

How long is such procedure to get it back from Samsung and how much if I have to pay it myself? I still don't see what could I have damaged with this action....
[Galaxy S I9000 Android Development] mash3an:
Works like a charm!

you're the SGS KING :)
[Galaxy S I9000 Android Development] Damia_:
BUMP

Help pelease I would like to kwon if its save to apply this fix, I dont wanna brick my phone.

Thanks
[Galaxy S I9000 Android Development] Cyclomatix:
this works great

Thanks
[Galaxy S I9000 Android Development] DaOldMan:
I have used this fix, and it works like a charm.

1. What firmwares are the ones that will destroy this fix again - how do I recognise them ?

2. What are "low" firmwares.

Sorry, but I am a total android nuuub - good I am a computer veteran :)
[Galaxy S I9000 Android Development] yanzisf:
Hi,

Thanks, it works fine with my Orange branded.

PDA : I9000BVJG2

PHONE : I9000BVJF3

CSC : I9000FTMJG2

recovery et download modes are now available, they aren't before.
[Galaxy S I9000 Android Development] coxpete:
what firmwares are you two on? it would be great if we could build a definitive list because i was all set to try the latest method when mine is back from repairs but reports like yours scare me a little after having a brick myself trying the method previous to the current 10/02/10 one, btw way i dont my firmware details till i get it back