yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] coradux:
I am not sure but it is from Orange Romania (locked) and I think it was XXJM1 (Eclair 2.1-update1). I've upgraded to JPH via Kies. Same phones from Orange Romania without upgrade to JPH reported flashing successful.

I've just tried the last method (adb reboot recovery to update.zip) and was unsuccessful.

When I've tried to flash the phone reported this:

update media, please wait

update media, finished

# MANUAL MODE #

-- Appling Multi-CSC...

Installing Multi-CSC

multicsc : src /system/csc/KOR/system/ .

Install default apk-files, please wait

Install default apk-files, finished

-- Install from sdcard...

Finding update package...

Opening update package...

Verifying update package...

E:signature verification failed

Installation aborted.

I have also tried before to use the lagfix via adb reboot recovery and update.zip and I've received the same error.

"update media, please wait

update media, finished

# MANUAL MODE #

-- Appling Multi-CSC...

Installing Multi-CSC

multicsc : src /system/csc/KOR/system/ .

Install default apk-files, please wait

Install default apk-files, finished

-- Install from sdcard...

Finding update package...

Opening update package...

Verifying update package...

E:signature verification failed

Installation aborted."
[Galaxy S I9000 Android Development] Richthofen:
Yeah, you cannot apply update zips on new Froyo´s.
[Galaxy S I9000 Android Development] franklin01:
Copy the update.zip to the internal SD then reboot in download mode (using adb reboot download) and apply update.

Check you csc before, to see if it is compatible and post your pda/phone/csc (*#1234#).
[Galaxy S I9000 Android Development] yusuf_fee:
Will this work on the Following Phone

i9000 South Africa Vodacom.

PDA:I9000XWJM3

PHONE:I9000XXJM2

CSC:I9000XFVJM1
[Galaxy S I9000 Android Development] Richthofen:
Is there a quinea pig who would like to try out something?

A T-Mobile or SFR phone with JG3 firmware would be required.

It is just as risky as before, but it is the only way to tell if we got a working solution or not.

Again, I tested it on my own phone and it did survive.

So the fix alone is not a killer.

It will be a two part fix.

The primary bootloader will be fixed first, and then the secondary which will restore the "3-button combo" feature.

Please send me pm if you are interested.
[Galaxy S I9000 Android Development] brackis:
For french sfr phone there is only

JG1 on phone and JG2 on pda

JG3 doesn't exist yet for us
[Galaxy S I9000 Android Development] Richthofen:
Actually JM4 is the newest version for you ;)

But anyway JG2 would be fine too.
[Galaxy S I9000 Android Development] coradux:
Can I go back to original firmware then?
[Galaxy S I9000 Android Development] Richthofen:
Yes, any Eclair version will work.
[Galaxy S I9000 Android Development] brackis:
JM4 ?

Kies dont tell me about an official update in france for sfr :(
[Galaxy S I9000 Android Development] Richthofen:
It is not official.
[Galaxy S I9000 Android Development] brackis:
ho

this version need a flash with odin ?

or regedit modification and kies ?
[Galaxy S I9000 Android Development] Richthofen:
It is Odin flashable, and not available thru Kies.
[Galaxy S I9000 Android Development] coradux:
But how can I do that if I don't have the 3 button combo fix?
[Galaxy S I9000 Android Development] Richthofen:
Well, how did you update to Froyo?
[Galaxy S I9000 Android Development] uveX:
I got 1 tmobile phone left.

But i think the shop wont exchange 1 more :)
[Galaxy S I9000 Android Development] anarchyuk:
how strange my new tmobile replacement has recovery mode!!
[Galaxy S I9000 Android Development] ingvay2009:
Richthofen ,

Plz Help Which Fix should i use

PDA: I9000JPJG8

PHONE:I9000JXJG2

CSC:I9000JPJG9

Thx
[Galaxy S I9000 Android Development] coradux:
I've update via Kies, editing hostfiles.
[Galaxy S I9000 Android Development] Gelu1990:
What if after running the update.zip my phone won`t start?...

After the blue letters device didn`t reboot and now I can`t turn in on.
[Galaxy S I9000 Android Development] yusuf_fee:
Please advise guys.

Thanks
[Galaxy S I9000 Android Development] franklin01:
BSOD, the phone is bricked, send it to the shop.

What was your firmware/pda/csc?

Which method did you apply?
[Galaxy S I9000 Android Development] franklin01:
Yep it SHOULD work since your phone is not branded, but you cannot be sure, give it a try if your feeling lucky.
[Galaxy S I9000 Android Development] Gelu1990:
Xwjm7 2.1

GT-I9000_I9000XWJM7_I9000XXJM3_CODE-MODEM.7z

CSC_I9000OXXJM1.rar

via update.zip.

Will they fix it ?
[Galaxy S I9000 Android Development] franklin01:
Seems to be a branded phone, check post #124 to see if your csc is supported.
[Galaxy S I9000 Android Development] Richthofen:
Use update.zip.
[Galaxy S I9000 Android Development] franklin01:
Your phone is FULLY bricked, it wont turn on whatever they try, they will probably change it or change the ARM or something so they will not know what you did.
[Galaxy S I9000 Android Development] Gelu1990:
I just hope that they won`t send me back the same bricked model...

I`m a little afraid that they might :/
[Galaxy S I9000 Android Development] davidke:
If you have a branded phone I dont think this "fix" is worth the risk...

Read this:

http://xdaforums.com/showthread.php?t=787638
[Galaxy S I9000 Android Development] Richthofen:
Where did you get the information that this would be a hardware issue?
[Galaxy S I9000 Android Development] franklin01:
We need to run some tests, anyone who success with the fix wanna brieck his phone to check?
[Galaxy S I9000 Android Development] Casio1987:
That was my first hypothetis when Samsung released the fix.

That's why I asked technical details and get some after contacting Samsung technical department, to finally speak with a tech, instead of those clueless helpdesk first and secondline helpdesk coworkers. But he couldn't give me more pointers, other than the original working 3br devices do not use the spl at all.

My hypothetis seems right if the bootloader gets overwritten by other firmware who's using spl on the respective partition.

My assumption, like I said before in this thread, is that the original 3br working devices gets triggered via the pcb, which loads the pbl with the safemode, if not on a dedicated module, maybe... That way, the users of such device can always be assured they can flash every firmware. This is how it's done with other many devices too. And that's exactly why I don't buy the story of 'not'-controlled batches by another guy here on the forums in another thread. I can understand why and that's why I'm so disappointed they continue to ship the phone with Android.

If you are like me, you need to test new firmware releases in order to test your own written code in Eclipse. Plus, I want the latest releases...

That's why I suggested to get your mobo replaced now you have the change, before Samsung goes with the spl fix as a standard procedure for future bricked phones.

But, for now, we will not know, unless somebody is disassembling a working 3br and a non working 3br device and have the electronic skills to confirm this.
[Galaxy S I9000 Android Development] dave1977nj:
I would like to know this as well
[Galaxy S I9000 Android Development] patpatci:
Hi,

my phone is:

PDA: I9000JVJH1

PHONE : I9000JXJG

PDA : I9000TRCJH2

can I apply the new fix ?

@Turkish users

Is there anyone that applied the new safest method on a Turkcell-branded phone ? (from Turkey) ?

best regards,
[Galaxy S I9000 Android Development] kstou2001:
@richthofen:

i notice you want a dump of jg3 firmware but my phone is in jm1 after update by kies. Before i was in jg2.

Sorry.
[Galaxy S I9000 Android Development] deastr:
Here's my dump:

http://www.mediafire.com/?dbbjak63eur2gg5

Using a branded phone, branded by Turkcell, Turkey.

PDA: I9000JVJH1

PHONE: I9000JXJG2

CSC: I9000TRCJH2

I'm dying to fix this 3 button problem. Could you please tell me if I can use your fix?
[Galaxy S I9000 Android Development] Wiseon3:
Thanks for this wonderful fix.

My phone is Romania Orange Branded (new, didn't root, unblock or install any application).

PDA: I9000XFJM1

PHONE: I9000XXJM1

CSC: I9000XFJM1

I used "adb reboot recovery" with the update.zip fix.
[Galaxy S I9000 Android Development] twitch93:
@ Richthofen

May it help, here is enclosed archive with BML 1 to 5 from my device.

Bouygues Telecom (aka bytel ?) branded, software versions :

PDA : I9000POJM2

PHONE : I9000XXJM2

CSC : I9000BOGJG4
[Galaxy S I9000 Android Development] franklin01:
Ok, dunno if this can help but I think, from what I saw from dumps, that a recovery.rfs is missing, replaced with a zImage. So if there is a way to include the recovery.rfs to the zImage, then it should fix every phones whatever the model/firmware/brand.
[Galaxy S I9000 Android Development] Richthofen:
This does not have anything to do with the kernel.
[Galaxy S I9000 Android Development] Db14:
I Rich

i give you my Bml1.dump if its can help you

branded sfr french :

PDA I9000BUJG2

Phone I9000BUJG1

CSC I9000GSFRJG2
[Galaxy S I9000 Android Development] Richthofen:
Yeah, the primary bootloader is completely different from what I have seen on another phones.

I have a way to update it, but there is a risk of bricking the phone.
[Galaxy S I9000 Android Development] yusuf_fee:
It has worked woohooo

Thanks to op
[Galaxy S I9000 Android Development] Db14:
I ave already brick a phone and return it, so I m not sure to test if there are a risk, because If i brick another one I payed the next one, i have a question, more people send you the Bml files , All this files is different or there are common ?
[Galaxy S I9000 Android Development] Richthofen:
All the SFR and T-Mobile seem to have the same, odd primary bootloader.

Which is different to everything else I have seen.
[Galaxy S I9000 Android Development] Merken_:
Worked flawlessly !

PDA I9000XWJM2

Phone I9000XXJM2

CSC I9000XENJM1

Belgian phone, unbranded, rooted
[Galaxy S I9000 Android Development] mengsuan:
Could there be a way for us, the end user, to identify if our phones have the odd primary bootloader? Hash check perhaps?
[Galaxy S I9000 Android Development] deastr:
How about mine?
[Galaxy S I9000 Android Development] brackis:
hi

this is my bml1.dump

for the story :

Originally i have a french sfr

with

PDA I9000BUJG2

Phone I9000BUJG1

CSC I9000GSFRJG2

then i update via kies in jm1

then in jm2

If it could help you
[Galaxy S I9000 Android Development] Richthofen:
Same story here.

The PBL is different.
[Galaxy S I9000 Android Development] kstou2001:
@Richthofen,

what kind of software are you using to edit the dump?

Is it a hexa editor?

thanks
[Galaxy S I9000 Android Development] Richthofen:
I´m not editing them, I just check the contents.
[Galaxy S I9000 Android Development] kstou2001:
And how do you do?
[Galaxy S I9000 Android Development] Richthofen:
Hex editor will work for the purpose.
[Galaxy S I9000 Android Development] kstou2001:
ok, it's what i've already done but i was thinking you're using an another software to really see the content of the file.

thanks
[Galaxy S I9000 Android Development] mavicafoto:
i can't open (unzip/unrar/....) the GT-I9000_SBL_RCVDL_FIX_REDBEND.7z file. i'm using 7-zip but it tells me it isn't a archive.
[Galaxy S I9000 Android Development] Richthofen:
Probably corrupted, download again.
[Galaxy S I9000 Android Development] bakakensai:
Hi Richthofen. Could you please check mine too tell me if it's suitable for the fix?

Thank you.
[Galaxy S I9000 Android Development] Richthofen:
BML1 dump would be the one, thanks.
[Galaxy S I9000 Android Development] kstou2001:
I have the same file.

What about your bml1?
[Galaxy S I9000 Android Development] bakakensai:
Here it is
[Galaxy S I9000 Android Development] spark001uk:
@Richthofen: How about if you had bml dumps from a previously branded t-mobile handset that's already had the 3br fix applied? Or would that not help?
[Galaxy S I9000 Android Development] Richthofen:
That is a normal bootloader.

Should be ok to use update.zip.

The factory firmware of your phone is JM1 or newer, correct?
[Galaxy S I9000 Android Development] kstou2001:
i will say jm1.

I have the same file and i am in jm1
[Galaxy S I9000 Android Development] bakakensai:
Thanks a lot.

pda is JVJH1 and phone is JXJG2.
[Galaxy S I9000 Android Development] kstou2001:
If you apply the fix give us the result.

thanks
[Galaxy S I9000 Android Development] Richthofen:
JVJH1 is never than the official XXJM1 :)
[Galaxy S I9000 Android Development] Richthofen:
For some reason I´ll bet it would work.
[Galaxy S I9000 Android Development] depp1999:
Is the bootloader in the attached file suitable for the fix?

Stock Firmware, Swisscom branded

PDA : I9000XXJM1

PHONE: I9000XXJM1

CSC : I9000SWCJM1
[Galaxy S I9000 Android Development] bakakensai:
It did. Both combinations work now. I can't thank you enough.

Your is the same as mine, mine did work I guess yours will too.
[Galaxy S I9000 Android Development] Richthofen:
I would not try it.

It is the weird bootloader again.

If you want to try the new trick, send me pm.
[Galaxy S I9000 Android Development] Richthofen:
Please provide the dump :)
[Galaxy S I9000 Android Development] spark001uk:
Ok, could you tell me how to produce the dumps, and which ones you would like?

I know i need root, whose method should i use for that? There's so many different explanations! :)
[Galaxy S I9000 Android Development] maitokeul:
@Richthofen

Here's what i have :

PDA : I9000BVJG2

PHONE : I9000BVJF3

CSC : I9000FTMJG2

and the dump

Many thanks
[Galaxy S I9000 Android Development] Richthofen:
I would not recommend using the fix.
[Galaxy S I9000 Android Development] Richthofen:
"It can be dumped by using adb.

The phone needs to be rooted.

Open a new command prompt and type:

1. adb shell

2. su (a superuser request will be displayed on the phone screen, accept it).

3. dd if=/dev/block/bml1 of=/sdcard/bml1.dump

The dump will be copied to the root of the internal SD card.

The size is 256KB."
[Galaxy S I9000 Android Development] spark001uk:
Having a slight problem rooting, i'm on Froyo JPH ?
[Galaxy S I9000 Android Development] manosv:
@Richthofen

PDA	I9000XWJM2

Phone I9000XXJM1

CSC	I9000OXXJM1

Original Firmware bought in greece (simfree) Can you please tell me if the update will work for me.
[Galaxy S I9000 Android Development] bigl666:
ok so far i have seen 3 different bml1.dump files here

All attached:

Post #489 by bakakensai - confirmed working

Post #497 by depp1999 - not recommended yet

Post #423 by kstou - not recommended yet

and mine? im even too scared to root :)
[Galaxy S I9000 Android Development] spark001uk:
Same here, i want to provide a bml dump, but i've just read up on rooting froyo, and it involves downgrading the actual recovery mode, applying update, then re-upgrading recovery again. I'm not too sure i fancy that, i've only just got recovery working!!

Or am i wrong? I fixed my 3br whilst on eclair, will i still have an eclair recovery even though i've flashed to froyo? Afraid this is the point where it loses me! :)
[Galaxy S I9000 Android Development] Richthofen:
You should be fine.

But for Christ sake, remove that attachment NOW!

It contains BML3 block too...
[Galaxy S I9000 Android Development] manosv:
Thank You i didn't know it was bad to do so.I will update how it went.
[Galaxy S I9000 Android Development] Gelu1990:
@Richthofen

If my phone got brickek during update.zip, what are the chances that warranty will include that ? Do u know what are the chances to fix or get new one ?
[Galaxy S I9000 Android Development] Richthofen:
In my opinion: None.

Even this whole thing is Samsung´s own fault, I would not send it to warranty as you knew the risks.
[Galaxy S I9000 Android Development] Gelu1990:
So the only solution for me is to get myself a whole new phone ?

That sounds bad :/ But I took the risk.
[Galaxy S I9000 Android Development] spark001uk:
@richthofen:

Just a thought, is update.zip taken down? Seems that new readers are getting to that page in the thread and then going ahead with it, not realising that further on people are reporting bricks?
[Galaxy S I9000 Android Development] Casio1987:
You are good to go. You must indeed flash firmware, due to new protection scheme in 2.2. But downgrading, nor going back doesn't overwrite your fix.

@Richthofen

Excellent work, very very dedicated, you should have a "Buy me a beer" in your signature ;)
[Galaxy S I9000 Android Development] ashmodai:
:) I think it is worth a try lol

More seriously in order not to have a second brick if I feal brave enougth to try a second time, what do you check in the bml to see that it is "special" ?
[Galaxy S I9000 Android Development] ashmodai:
I am sure that the Samsung support centers will receive a lot more bricks than usual :D
[Galaxy S I9000 Android Development] bigl666:
@ashmodai: its easy to check if the primary bootloader bml1 is equal to the good one or not - you can do a compare by content with ie total commander
[Galaxy S I9000 Android Development] spark001uk:
Just to clarify, odin cannot possibly flash any bootloader files unless you tick the update bootloader option, is that correct?
[Galaxy S I9000 Android Development] Richthofen:
As far as I know, nope.
[Galaxy S I9000 Android Development] franklin01:
So if BML is the problem, cant we just overwrite faulty BML with patched BML, some kind of all in one patch?
[Galaxy S I9000 Android Development] Richthofen:
At the moment it seems that some phones contain a faulty or incompatible PBL (primary or primitive bootloader as Samsung calls it).

When a new SBL is being flashed to these phones, the PBL becomes the issue.

It will result a bricked phones.

Judging from the dumps, this is the actual problem.

It can be easily fixed by updating the PBL at the same time with SBL, but someone would have to test it first. I have the fix ready, but I cannot test it myself since I don´t have a phone with faulty bootloader or a faulty bootloader to flash in my phone.
[Galaxy S I9000 Android Development] franklin01:
So we just need to dump a PBL and an SBL working, then push these into a faulty phone and everything will be fine :)

So we need testers...
[Galaxy S I9000 Android Development] mengsuan:
Oh my. I'm fortunate to have waited to identify my phone's BML1 before updating. While many have reported success with their Singapore Singtel i9000, mine happened to be the one with weird e-fused.

PDA: I9000DXJG4

Phone: I9000DXJG4

CSC: I9000OLBJG4

This phone should be of the latest batch. I just got it several days (less than a week).

I could have tried Richthofen's PBL+SBL fix but it would be too risky to brick my phone now. I'm almost a thousand miles away from its home country.
[Galaxy S I9000 Android Development] Gaili:
Then why did I full bricked my SGS? I flashed my phone with a full flash "without" ticking "update bootloader" in odin.

my original firmware was:

PDA: I9000NEJG3

Phone:I9000NEJG1

CSC:I9000DREJH2

after kies reg. flash

PDA:I9000XXJM1

Phone:I9000XXJM1

CSC:I9000OXAJM1

i made the flash with:

PDA : CODE_I9000XXJM1-SBL.tar.md5

Phone : MODEM_I9000XXJM4.tar.md5

CSC : CSC_I9000XAJM1.tar.md5

PIT : s1_odin_20100512.pit

Thanks
[Galaxy S I9000 Android Development] aideno:
I have Aussie phone, and I have updated using Kies to Canadian JH2 to get 3BR. Now im not satisfied with the firmware, and looking to reflash.

First - Will I lose the 3br if I flash another with Odin? There used to be a guide in post 1, now its changed to the update.zip method only.

Second - My phone now displays i9000m at boot, instead of just i9000. Would that always stay that way now?
[Galaxy S I9000 Android Development] coradux:
Can you tell me what is your ProductCode? I'm stucked with Froyo JPH and no 3 buttons combo and I want to upgrade to official Froyo release when it will be available. I've upgraded to Froyo JPH via Kies registry hack and changed my ProductCode.
[Galaxy S I9000 Android Development] puiuflorinel:
It worked for you?

Can you post your bml1 dump?

thanks
[Galaxy S I9000 Android Development] patpatci:
My friend,

you were right,it worked ! thank you for encouraging me.

@Richthofen

You are the man ! you saved me.I hope I never lose this.
[Galaxy S I9000 Android Development] FarligOpptreden:
So is there a fix yet for the "bad" boot loader that reads e-fused in the last line of the BML1 dump, as mine does...? :(
[Galaxy S I9000 Android Development] D@rk_4ngel:
I also have an e-fused phone..
[Galaxy S I9000 Android Development] yusuf_fee:
I tried this last night and my phone did not Brick.

i checked my BML1 now and have a look at the last line.

Its E-Fused

WTF!?

http://www.dropbox.com/link/17.X6uArl4evx?k=5746a334027b080d10fdebf6103018f4
[Galaxy S I9000 Android Development] Hartsig2000:
German tutorial

In a german galaxy-forum called "Android-Hilfe" there is a thread from "dadonali" about fixing the 3br-issue by flashing ANY firmware (even branded) first to XWJM5 (from samsung-firmwares) and after that applying the SBL-fix by Richthofen - he assures that 100% of fixes made according to his tut succeeded. Perhaps there is no need for changing the PBL? Or no guarantee, that this won't brick some phones?!
[Galaxy S I9000 Android Development] FarligOpptreden:
Ok, so yusuf_fee has an e-fused phone and it worked... A friend of mine's SGS was U3" and it worked... Let's do a bit of a tally here:

FarligOpptreden: CSC I9000XFVJM1, e-fused, untested

FarligOpptreden's friend: CSC I9000XFVJM1, U3", worked

yusuf_fee: CSC I9000XFVJM1, e-fused, worked

D@rk_4ngel: CSC I9000XFVJM1, e-fused, untested

xrayA4T: CSC I9000XFVJM1, e-fused, untested (?)

So, D@rk_4ngel, should we take the plunge and see what happens?
[Galaxy S I9000 Android Development] mislead:
I am on CSC i9000VIAJM1 ( Stock ) here.

Also E-Fused.

Untested till now.

I am thinking about flashing to JM5 and then applying the fix.

But i am uncertain if i am willing to take the risk of a brick.
[Galaxy S I9000 Android Development] xrayA4T:
My Vodacom SGS also has e-fused.
[Galaxy S I9000 Android Development] FarligOpptreden:
Have you tried applying the fix or not? Results?
[Galaxy S I9000 Android Development] D@rk_4ngel:
The above results is still 50/50 for me.. Would really want to try but just want to make 100% sure first that it would not get bricked because of the e-fused. And what do i do if it does get bricked!!

Oh and mine is rooted and OCLF lagfix applied. Would that affect this in anyway?
[Galaxy S I9000 Android Development] FarligOpptreden:
Both my and my friend's phones are rooted with OCLF applied. Again, it worked for him with U3" in the BML1 dump. Would also like some better odds for applying it before I attempt it myself.
[Galaxy S I9000 Android Development] xrayA4T:
No, at the momment I don't want to risk it. I will wait for the Froyo update which will hopefully include this fix. If Vodacom does not give us Froyo soon after the international release I may consider the 3br fix.
[Galaxy S I9000 Android Development] akex054:
Where did you see the Froyo release will fix it ? It's really uncertain ...
[Galaxy S I9000 Android Development] yusuf_fee:
Its not 50/50

its a 100% test rate as only 1 phone was tested and it worked.
[Galaxy S I9000 Android Development] ashmodai:
Starts to be fun :-) I would love to tell you if my brick was e-fused or not before I killed it but that's a bit late for me ;-)
[Galaxy S I9000 Android Development] kyokeniclai:
3 combo fix.

the method is working,but not stick to the inside of hardware. if you want to enter download mode again,you have to recovery again to apply the update.but is really safe and good.the fix is from samsung. thanks a lot.all of you from xda dev.
[Galaxy S I9000 Android Development] FarligOpptreden:
What was your phone's CSC? Branded firmware or not? If branded, which carrier?

Hmmm... will see if my friend's SGS enters download mode every time though. He can now successfully enter recovery mode on every restart.
[Galaxy S I9000 Android Development] ashmodai:
My phone was one of the firsts bricked at the very early stage of this thread. I could not resist the trial :-) It was still the the Odin technique ... It was a T-Mobile german branded phone. JM1 firmware with OXX CSC (set to swiss)