[Samsung Galaxy SL i9003] chongns:
Hi Member :fingers-crossed:

Again, the wave of lost of imei seen coming back.

there are still have alot of SL lost the imei and baseband.

Tried hard to find away to repair it, but since....that's not way without the back up still....

At the mean time wait for the beta of CM10.1 or maybe CM10.2, i go back to GB again. Yeah.. it is boring.. so i playing with EFS partition again.

HAH. this time, i get a new info...it is been along time trying to find our what is BML3 about and what is the relationship with STL3, our EFS partition.

i get to know that from I9000 thread, that seen BML3 is about the "mother" of STL3. (sorry for the bad english, i'm not cursing)

why i said that ? cause i do a test on it.

My Test on BML3

1. dd out the BML3 partition. i read the image using Hex Editor, i found the word of nv_data.bin and nv.log inside it.

2. (do not know why i did this), than i dd back the image into the BML3 partition. than my STL3 corrupted, or it can said as it is gone from partition list.

3. so, it cant be mount by the phone.

4. so, you have not imei and baseband

So, if you still haven't doing any flashing of the STL3 or EFS folder from the blank tar templet using odin or any why to put the image in, it is still have possibility that the nv_data.bin or .nv_data.bak still usable. so dd it out and keep safe.

Still remember? i have backup my stl3 partition, so i flash back it using Heimdall-frontend. (Odin not able to flash the dd image, you have to tar it in linux into Odin flash able.)

why i using flashing instead of dd it back, cause i tried, but it fail, cause the STL3 is not mounted.

So, i suspect the lost of imei is not STL3 or EFS folder corrupted, it is the BML3 some how lost link or bad block.

I attach my generic imei of the BML3 and STL3 image

you can try as below method.

AGAIN....STANDARD DISCLAIMER....

** YOU HAVE TO KNOW WHAT YOU ARE DOING.
** THERE ARE RISK TO YOUR PHONE WHAT EVER YOU TRYING TO FLASH WHAT EVER IN IT.
** IF YOUR POINTING THE FINGER AT ME BECAUSE YOU CHOOSE TO DO IT
** I WILL LOLLLLLLLLLLLLLLLL AT YOU

OK, the instruction

i'm using Ubuntu as OS and Heimdall and Heimdall-Frontend to flash.
install Heimdall command, and install Heimdall-Frontend for the UI

Download the attachment, and rename it.

1. in adb shell, dd out the BML3 and STL3 for backup

dd if=/dev/block/bml3 of=/sdcard/bml3.img

dd if=/dev/blcok/stl3 of=/sdcard/stl3.img

2. using my copy of BML3.img, dd it back

dd if=/sdcard/bml3.img of=/dev/block/bml3

than reboot

3. after the reboot, reboot into download mode, flashing my STL3.img using heimdall-frontend

a. open terminal, key heimdall-frontend

b. in the UI, go to Utilities tab, click Detact Device, makesure the device is detacted.

c. go to Flash tab, in pit, put in the Pit File, untick the repartition

d. Partition, click add than at the Partition Detail, Partition name, choose EFS

e. in File, put in the STL3.img file

f. than Start, wait few min, the phone will reboot it self.

4. after that, you will get generic imei.(atleast i get it)

So now, tried to flash you own STL3 image from just now you dd out.

if you are lucky, you will get back the imei, and if you are very lucky, you will have my imei.(but i think the possibility is very low)

Have fun tying..

~~Old Post~~

CORRECTION

Actually the EFS Pro work great for the Restoring the EFS image, :good:

it is just the stl3 or efs partition did not mounted so the app show error

the correct step to use EFS Pro as follow

1. flash to stock with RFS file system.

2. flash CF-ROOT kernel to root the phone (optional, due to odin flash not need rooted)

3. flash the efs.tar to mount back efs folder

You get back the efs partitional and generic imei

Ahh.. by the way, after flashing the efs.tar, the bluethoot and wifi mac will changed follow the original phone which output the efs.rfs

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Guys, today I was so boring, so I get my phone efs partition corrupted. YES, I corrupted it purposely.

few item need to prepare

1. your efs backup (nv_data.bak or original nv_data.bin)

2. odin 1.85 only, odin 3.04 got problem

3. stock Froyo and Gb

4. CF-root kernel (i use Bam kernel, thanks to XDA_BAM)

5. efs.tar download herethanks to celica7

6. EFS Pro

Of Couse I have the efs backup.

That’s how I corrupted. I mean the efs folder...:D

* Flash a stock firmware with EFS clear tick! (Odin 1.85) DXKE1 * everything goes normally.

* Still I having the IMEI. Due to the backup still there

* So, continue to screw it up, flash to GB 2.3.4 DXKP9 and root it with Bam kernel 14fix. Use RE to delete all efs file.

* Still get the generic imei

* still not enough corrupted, continue to screw it, flash again stock firmware dxkp9 with efs clear, but generic imei still there

* flash again bam kernel to root.

* Than do dd if=/sdcard/efs_backup.img of=/dev/block/stl3 to restore the backup efs image.

* Still get the generic imei

* try corrupt it with EFS Pro (sorry dude), just due to the tool having function of format efs folder. But it format efs fail

* chown the efs folder to root, and reboot

* still the system changes it back to radio. (ogh, so hard to corrupt it)

* ok, flash back to stock froyo, and see.

* All right, now I have blank imei or unknown imei

* due to lazy to fine root procedure for Froyo base, I continue to flash GB

* Odin flash pass, but phone boot into 3e recovery and show;

E: failed to mount /efs (invalid argument)

E: check_selective_file:Can't mount /efs

Multi-csc applied failed (NICE:victory:!!)

OK, now time to restore imei :fingers-crossed:

* flash bam kernel to root.

* after flash bam kernel, imei show 004999010640000, it supposed to show unknown imei, due to efs partition is not mounted. :confused:

* who care. continue to restore imei using EFS Pro (failed) :eek:

* try restore imei with backup img by EFS Pro (FAILED!!):crying:

* NOW, try others method from XDA

* flash efs.tar with ODIN to get back efs mounted

* delete every in the efs folder.(the generic imei file)

* copy your nv_data.bak to efs folder and rename to nv_data.bin

* chmod 700 nv_data.bin

* chown radio nv_data.bin

* chgrp radio nv_data.bin

* reboot

* Guess what next ? I get the imei back