[SHW-m110s] Korean Anycall Galaxy S, Thread/FAQ/ReadMe/Discussion/Questions

Search This thread

appagom

Senior Member
Sep 18, 2010
670
45
I might be noticing this same problem as below. Didn't get the superuser pop-up a couple of times when expected to... needs more testing but the point makes perfect sense... now that I understand (from much digging) what jk-su is really up to. Anyway the solution is there and simple enough.

http://xdaforums.com/showthread.php?t=784938
 

appagom

Senior Member
Sep 18, 2010
670
45
shw-m110s root exploit and extras + BASIC guide to root ANYTHING.

Much of the info here is still educational and even useful at times... but I'm not supporting this anymore and the simple thing to do now is just use Tegrak kernels. They are rooted, lag fixed, and more. Look it up. It does void your warranty of course.

my safe journaling ext4 kernel page is here (now with root, busybox, voodoo sound and improved mount option congifuration). If you're willing to use odin, it will do almost everything in this post in one flash.

tegrak's kernel is also rooted. It uses less standard version of busybox for some reason. (1.13.something). I'm sure that's fine or he wouldn't use it.

Quick Guide


First Rynza has an app called z4root that does this without a usb cable and is one click ( Not presently working with SL28 phone update so keep reading). It works on this device in Froyo and probably also eclair. It also installs busybox. It's a market app, so just search the market on your phone.. download and do it.

Use z4mod for a lagfix if you don't know what to use. RyanZa (author of OneClick Lag fix) is co-dev on z4mod. There is an app available in xda
(sometimes in the market too). It's easy to use. It does flash a new kernel, but it's all pretty automated. If it complains about space on /system.. remove something from /system (like a big apk), but back it up.. you can put it back when it's done installing.

The older One click lag fix, OCLF V2.0+ is not ready yet for froyo on this device yet (breaks vibration). It might be fixed soon, especially if there's interest. V1+ (offered from the same app) also works very well.

lag fix disclaimer: 1) I feel stock keeps getting faster and smoother, maybe even with 2.2.1, so give stock a try first before lag-fixing. 2)Evidence is piling up that un-journaled (faster) lag fixes(as this is) may be less safe for data (app data, not sd card data) in an improper shutdown.(Note some people also strongly disagree, but this is my post) Many feel the performance is worth the risk especially since apps can be re-installed (from backups made from your corrupted data ;) or from the market ). I don't know of any confirmed problems outside of testing environments, I had filesytem corruption myself AFTER I wrote this, but I pulled the battery a few times; don't. Data corruption doesn't always produce easily confirmable or understandable problems. It's up to you. Voodoo is probably safer now but the only voodoo for this device has korean instructions and may or may not use the latest safe versions of voodoo. I am still using z4mod for now. If you don't know.. just buy life insurance and don't do your corporate accounting with your cell phone.
I have recently constructed a z4mod kernel with ext4 modules from tegrak on page 157
No repartition instructions exist yet so you're on your own with that for right now. If you don't even understand what it has to do with the above paragraph, you certainly aren't ready to mess with it.

You still may want to read below about the manual root method (just to understand) and about things like lag fix and busybox and titanium backup and un-rooting or just to understand how it all works so you don't need to ask silly questions.

Long old (but still good) guide:
root that doesn't need to be setup at boot, is simpler (than joeykrim), and doesn't interfere with OCLF or superuser or probably anything else)


Preface
I didn't exactly develop any of this(ok just a little). Mostly just (re)discovered it and collected it. Amazingly.. it's not really documented well.

Since I first wrote this I found quiet but older cyanogenmod page desribing this method for one of the cousins. Also another more recent page here at xda describes this working on the epic.

http://xdaforums.com/showthread.php?p=8406167#post8406167
and it should work for just about anything else running 2.1 or 2.2 (confirmed, thanks to koe1974 for testing/fixing for m110s froyo) with some tweaks (see special cases below including joeykrim/leshak cases).

And finally superoneclick which came out a little later basically uses this approach (and may well work on shw-m110s)


Thanks to
joeykrim for epic root method that inspired this one and for proofing this one, and thanks to the anonymous (I think) guy who found the exploit in the first place. Thanks to koe1974 for catching group/passwd file ommission and for testing, and to allovel83 for info about his fresh phone. Thanks to Wapu for first tries at OCLF that inspired much of this.

What is root.. really? (skip to "Howto root it" if you don't care how it works.)

The ONLY thing needed to have root access on any device is a working "su" command. Working means
1) it's in default executable path (ie /system/bin or /system/xbin)
2) The file is set as owned by root
3) It is executable by everyone
4) It has the set-user-id bit set which means it will run with root permissions when anyone runs it
5) /etc/passwd and /etc/group exist with definitions for the root user and group.
That's it. (I'm ignoring root kernels)
If this works, then root is permanent and requires no startup scripts, no playlogos1 trick.

su Installation options
There are 4 basic methodds used to copy these files (but they all have this same end goal).
1) Flash a whole new custom rom (wipes data.) including su. (very device specific obviously)
2) Use the phones update ability to add files from an update.zip file in recovery mode. (many one-clicks use this, not superoneclick but I think it's impossible on froyo stock bootloaders which require signed update.zips)
3) Flash a new kernel.. actually this more about the initramfs image that the kernel uses and which has su and related files.
http://xdaforums.com/showthread.php?t=788108
That one probably doesn't work on our device but who knows..
(Both 1 and 3 can brick your phone if you do the flash incorrectly)
4) Use an exploit to gain root access on a running system. Use that access to install the files. The most flexible method for working out root on new setups.
(It may not be impossible to fully brick this way.. but it would take serious skill, really, not in a sarcastic way)

I only talk about option 4 here. Option 2 does not work for this device as of present 2.1 models. Option 1 does but with no custom roms, doesn't actually gain root. Option 3 is unexplored and again has no particular advantages. I have successfully rooted a kernel and can make one available for flashing if needed. This is more attractive now that lag fixes are using kernel mods anyway.

the exploit

To install these files on a running system... one needs root permissions already! Darn. Some anonymous guy found an exploit (rageagainstthecage) in adb that could get root permissions in the adb shell until the next reboot. That's enough to get things installed. (Update: the idea that this only works through a usb connection is a myth as proven by Ryanza's z4root. FYI, That means any app can get complete control over your device with this trick if your phone is in debug mode! This is real security threat , but we may as well use it until it's shut down)

The implementation
Here... nothing to it. Run rageagainstthe cage... copy the files in, set permissions. Reboot.. period.


HOWTO root it
I think this has all been tested essentially cut and paste now (by koe1974).

First get adb working for your device. Plenty of other FAQ's explain this, including the "Big FAQ" in i9000 general.

Download jk-su (or any other su) and rageagainstthegage-arm5.bin from
http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/

The link is broken.. sorry, search and you'll find it. Not sure I'm allowed to post such things here?

Get temporary root from the exploit
rageagainstthecage goes in /data/local/tmp because we have write permission there, because we can't execute things from the sdcard, and because that's where one puts temporary things.
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp
./rageagainstthecage-arm5.bin
exit

re-establish adb (may require reconnecting cable and/or adb kill-server possibly more than once (especially helpfule in froyo according to koe1974). I find it depends on which usb port I use, and this is also reported elsewhere.. my esata port on my laptop is by far best)
look for # prompt
If not... try temp root procedures again. It will work

Then make it permanent:
Code:
adb push jk-su /sdcard
adb shell
mount -o remount,rw -t rfs /dev/block/stl9 /system
cat /sdcard/jk-su  > /system/xbin/su
chmod 4755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
(the link to /system/bin/su might not be needed)

That's it. Some instructions use superuser.apk to install passwd and group files.
I'd rather get normal su working first, reboot and test it.

reboot.. check for root:

adb shell
su
# exit

The "#" should show up on its own. You don't type it. This "#" prompt is the indication that you have root. Well done.

NOTE for other devices:
Some devices may mount root somewhere other than /dev/block/stl9
Amusingly at the moment you can use "/dev/block/yomama" in the command and can also use any filesystem, and it will work!
I thin because it's a remount it actually ignores these parameters (may not be gauranteed behavior with future versions though)
Anyway, this should not be taken as a step by step guide for any non-similar device, but should basically show the right approach (even though it may work perfectly.. but may not). See "special cases" below for issues I'm aware of.



Highly Recommended
Install superuser.apk from market
Superuser.apk protects your root by popping up a prompt asking for permission whenever a new program wants to use root. To do this, it replaces the su file.
After installing this Titanium Backup may think you don't have root. More on this below.

Optionally: For galaxy relative owners ONLY, (as far I know):
Install RyanZa One Click Lag Fix 2.1 apk version (or any other probably) with no modifications. This is the only lag fix with english instructions that I know of that's tested on the korean device. I use the max image size with no problems. It works, makes the phone much faster, and its modifications are relatively un-invasive compared to other fixes (no kernel replacement or partition reformatting).

This copies the splash screen /system/bin/playlogos1 to /system/bin/playlogosnow and replaces it with a new playlogos1 which is just a script that calls /system/bin/userinit.sh to setup the lag fix, and then calls the original splash screen, playlogosnow.

Market Enabler can allow phones in restricted acess areas to get games using the Android Market. Use its backup feature. Then set your network to something like T-Mobile USA. It's temporary, for one internet session I think unless you buy the full version.

(legal disclaimerI don't know any details about Korean or other internet access control laws. That's your problem to worry about)

Install busybox. Probably very optional since most root tools provide their own (z4root installs it but without all the sym links). You can probably use the market installer if you do it ***BEFORE installing OCLF***. If you do it after.. it may remove OCLF's own copy and break OCLF and your apps installation (or anything else using its own copy of busybox.)

If you installed OCLF (or something else with busybox in it, like TiB), you can link its busybox into your system this way.

Code:
adb shell
su
mount -o remount,rw -t rfs /dev/block/stl9 /system
ln -s /data/oclf/busybox /system/bin/busybox
busybox --install -s /system/bin

And this version should be well tested and maintained for Samsung devices.
You can also install the market installer, run it, but don't click install and it will give you a new version you can link in the same way.
Or just try installing the market one BEFORE OCLF or anything else that might have its own.

Tintanium Backup also can install a busybox but it also does not become default and does NOT get it's commands sym-linked into /system/xbin. It is basically there for TB use unless you fully install in it instead of the OCLF or other version.
Funny story there (This seems no longer relevant with some versions of things. When I installed TB after superuser.. it said I didn't have root (superuser never asked for permission as it should) and won't work. When I clicked "problems" and install busybox.. it asked for root (tried to use su) and I said ok, and then it worked fine ever since. This has nothing to do with busybox probably, only to do with superuser acting flaky and/or TB checking for root in some funny or impatient way.

removing busybox
Isn't that simple as far as I can tell (until now)...
If you've installed all the symlinks then you might want to remove them all.
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/block/stl9 /system
busybox ls -al /system/bin |busybox grep busybox | busybox awk -F" " '{print "/system/bin/"$9}'| busybox xargs busybox ls
This just finds them. It's not heavily tested so I suggest you run it once as is. It should output many filenames in turquoise letters in /system/bin. It may also find busybox itself.
If you're happy, change the ls at the end of the long command to an "rm" and do it again to remove.

If your busybox is in /system/bin, this will remove it along with the links. If you used the instructions above for OCLF busybox it will remove the link and OCLF will remove busybox when it is uninstalled. If your busybox is somewhere else or linked to somewhere else, you got there it, you can delete it.

unrooting
Once you're root and used root apps the only way to make sure there's no trace of modified files on your phone is to reflash the ROM or diff your entire /system against a ROM image. But if you just want to disable root access and remove what we've done above...

First undo other things that need root of course.
Undo OCLF for example, but just use standard methods for those without modification.
Remove busybox.. see instructions above.
Then it should just go like this:
adb shell


Code:
adb shell
$ su
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# rm /etc/passwd 
# rm /etc/group 
# rm /system/bin/su
# rm /system/xbin/su
# rm /sdcard/jk-su
# rm /data/local/tmp/rageagainstthecage-arm5.bin
# reboot

Amusingly OCLF should work after unrooting if you reverse the order.

Special Cases(other devices)
Just to be thorough:
The primary exploit, rageagainstthecage (ratc), works on ANY 2.1 or 2.2 device, but there are some little dificulties

1)
Once upon a time (and probably still) the android system on the moment would undo set user id bit on files in /system on bootup. Root broke. Jeoeykrim (actually leshak I think) fixed this by copying su to a ramdisk during bootup. Set it's permissions, and soft linking back to /system/bin and /system/xbin

Later it worked on the epic and was adopted on all its cousins, maybe because nobody bothered to try the obvious simpler ways. It's since been found (by me and others) that although it worked, it's just not needed on these devices, at least not with present firmwares (maybe something changed). Furthermore the symlink interferes with superuser installation and the startup scripts interfere with installation of OCLF and who knows what else (because it uses the same playlogos1 file to install its startup scripts)

A few devices still may suffer from this issue. If you have su working, and it breaks after rebooting (test without superuser.apk first), then try the joeykrim/leshak method, but this problem seems very rare now.

http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/

If you then install superuser, you'll want to copy its file in correctly.. see link in post above. If you install OCLF you'll need to restore the playlogos file (an option on the apk).. install it, and then make a new playlogos file that calls both the OCLF script and the root setup script. Wapu has in this thread one working instruction set for that. I've contested that it should be do-able in a simpler way, but no cut and paste instructions exist for that.

2) A few devices are NAND locked meaning you can't copy in su. For those google around about NAND locks. There a trick to un nand lock first.
 
Last edited:

alovell83

Senior Member
Jun 29, 2010
731
33
Lippstadt
Can't lie, I didn't even skim your post but with 36-48 hours I plan on reading it in detail to decide which method I'll choose (I did like your intro, easy and no exploit sounded good...just there...). I'm posting just to say that if it is that good as it comes off from the first few lines of the intro I think you should post this in android development section for a few reasons:

First, better beta testers (assuming they have the same method avail, many of the methods have worked between devices, even before the joeykrim), maybe even just a slight tweak to get it to run on a diff model

Second, notoriety

Third, potential for some donations or code improvements that can help us all long-term.

Wish you the best and hope to test this out by Sunday, I have an eye check up in Seoul so I should've been a sleep at least two hours ago.
 

Technecium

Senior Member
Oct 6, 2007
1,570
716
The untested (even better) plan
Any takers to test from scratch?

Never gonna work ... su needs /etc/passwd or etc/groups

Began by factory resetting my phone.

Test for root

adb shell
$ su
#

still rooted after factory reset

Unroot phone

# mount -t rfs -o remount,rw /dev/block/stl9 /system
# rm /system/bin/userinit.sh
# rm /system/bin/joeykrim-root.sh
# rm /system/bin/jk-su
# rm /system/bin/playlogosnow
# rm /etc/passwd (created by previous root)
# rm /etc/group (created by previous root)
# mv /system/bin/playlogo-orig /system/bin/playlogos1
# chmod 755 /system/bin/playlogos1
# mount -t rfs -o remount,ro /dev/block/stl9 /system


Test for root
adb shell
$ su
su: not found
$

Get temp root

Try to install 'superuser'; installs, asks to update but fails

Factory reset
Get temp root
Push jk-su to /system/bin/su and /system/xbin/su
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 4755 /sytem/bin/su
chmod 4755 /system/bin/xbin
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system

adb shell
$ su
su: unknown user root
 
Last edited:

appagom

Senior Member
Sep 18, 2010
670
45
@allovel This still requires the temproot exploit.. frankly I'm not sure joeykrim is responsible for this part of things but he certainly brought it to light. When I say joeyscript is gone I mean the bootup script is gone. You still need to get temproot from the exploit to set things up..

edit: I've got alot just come up and things to catch up on. Spending too much time on this. I probably won't do any testing this week but I'll check in.
 
Last edited:

appagom

Senior Member
Sep 18, 2010
670
45
Never gonna work ... su needs /etc/passwd or etc/groups

edit: shorter answer:

Yep (depending how you interpret never) good catch. I think fooling with my unroot script made me forget this part. (no actually it's because my tested process did run joekrim-root.sh once, but only once.. on the first reboot)
See new instructions and try again.
If you don't want to start over just get temp root now and apply the echo commands from adb (don't forget write access first.. oh that's / write access, not /system.. going to add that command now) then reboot.

The fact that su gives you that error says it's fundamentally working. If it wasn't you'd get a different error.

The only thing is I don't know if /etc/ survives factory resets, but I don't know if anything does.
 
Last edited:

Technecium

Senior Member
Oct 6, 2007
1,570
716
edit: shorter answer:
The only thing is I don't know if /etc/ survives factory resets, but I don't know if anything does.

On the earlier attempt I started by doing a "Factory Reset" without uninstalling OCLF or root.

FYI: Root survives the reset. I had to manually remove previous root. Used the uninstall procedures from (joeykrim) root and (wapu) lagfix directions. Followed by what I posted earlier.
 
Last edited:

appagom

Senior Member
Sep 18, 2010
670
45
On the earlier attempt I started by going a "Factory Reset".

FYI: Root survives the reset. I had to manually remove previous root. Used the uninstall procedures from (joeykrim) root and (wapu) lagfix directions. Followed by what I posted earlier.

yeah.. I guessed maybe. So I just don't know if /etc also survives. This maybe SLIGHTLY less permanent than joeykrim permanent root, but I don't see that as a real downside, and we just don't know yet (or I don't).

(eidt)BTW.. this is important.. it means that android assumes /system is read only and never changes and has no need to be backed up. It would appear that the working version probably IS the flashed copy. Anything you break on it is permanent, and if it breaks bootup badly enough that you can't get root adb, it will require a re-flash (with odin).
 
Last edited:

joeykrim

Inactive Recognized Developer
Jan 9, 2009
1,978
1,311
So I just don't know if /etc also survives.
maybe everybody has this sorted out, but i figured i'd throw in two cents with some hope it helps somebody. i've never seen the korean galaxy s, but had an epic were i tested this root method. all my experience is general with android and/or specific to the epic.
/etc is a symlink to /system/etc. as you know /system is permanent and is mounted as read only. w/o root access, all of /system is designed to never be modified. /etc is just a directory under /system.
also, if su binary isn't stripped of the setuid permissions, its obviously more efficient to keep it on /system instead of in the tmpfs.
off the top of my head, its 3am now, a thought occured to me. if in init.rc your /system is mounted as read/only and to not allow root setuid, it might attempt to strip the 4755 off the su binary. but in the end, if it works, it works!
glad to see the effort and appreciate the comments!
 

appagom

Senior Member
Sep 18, 2010
670
45
Hi joeykrim thinks for stopping in.
I should have checked for the sym link.. great, so it should be really permanent (for better or worse).

joeykrim:
if in init.rc your /system is mounted as read/only and to not allow root setuid,

Yeah.. I gathered something about like was the whole reason for all this tmpfs hiding. It seems to not be bothering us! (and now I know where to look to see if it should be). So we simply need to set it up once and leave it alone. Or so it seems so far. This helps alot because you playlogos thing was interfering with one click lag fix at least a little and also the links to tmpfs aparently confused superuser too.

Again thanks for looking over it.
 

appagom

Senior Member
Sep 18, 2010
670
45
@koe1974 I had a (relatively obvious) typo in one of the chmod commands.
I noticed you echoed it back to me. I was really not taking time to write an exact script as much as a procedure the first time around, but I've tried to improve it a little (cause I cut and paste too).
 
Last edited:

Technecium

Senior Member
Oct 6, 2007
1,570
716
SKT Admin Menu

What you do with this information is up to you.

From the dialer enter: 319712358
You will be prompted for a pasword: 774632
 

alovell83

Senior Member
Jun 29, 2010
731
33
Lippstadt
I'm not sure, but perhaps the network settings there could be helpful to overseas users who are having radio issues. Thanks for posting them, we haven't had access to most or all of these for over a month.
 

appagom

Senior Member
Sep 18, 2010
670
45
for what it's worth most, possibly all of the galaxy dial codes work on mine.

2.1-update1
M110S.DH09.2134.ST
ECLAIR.DH19
 

hongcafe

New member
Oct 3, 2010
2
0
souel
Pls help me now i update to use version 2.2 but i can use network

I use galaxy S ver korea and then i update by Odin to Version 2.2 but i can find network from T mobile..

1. How i can Use ver2.2
2. if i can't use i want to use offical rom (where I can download)
 

Technecium

Senior Member
Oct 6, 2007
1,570
716

Kr0c0

Member
Aug 17, 2010
18
0
Another site is

matpclub.com

click on the "voodoo m110s custom" banner.

that page is for installing voodoo and rooting but half way down that post is DI03_stock.tar for going back to stock.

Sent from my SHW-M110S using XDA App
 

appagom

Senior Member
Sep 18, 2010
670
45
Just found this:

http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Fascinate)

It is pretty much my root method. (except they only write to /system/xbin/su and not /system/bin/su... don't know if both are needed, but might as well for good measure. edit should probably just link from bin to xbin. Don't want two different su's floating around.

Also they don't setup the passwd and group files but do install superuser while they still have root (which probably does the same thing)

So I guess it's not the appagom method after all. (but I did say it was obvious) For other similar devices the update.zip is listed as the installation vehicle. I wonder if the Fascinate has the same broken recovery mode as us.

It occurred to me that this technique might give root access during for adb in recovery mode if that's worth anything. not sure though and don't have a cable right now.

I'm wondering about pushing a new recovery mode to this phone. I believe the relevant file is /sbin/recovery (not just because of the obvious name).
 
Last edited:

alovell83

Senior Member
Jun 29, 2010
731
33
Lippstadt
I'm wondering about pushing a new recovery mode to this phone. I believe the relevant file is /sbin/recovery (not just because of the obvious name).

I think the title is misleading for our purposes, it would require flashing a different firmware...i think :confused:. Still, if you haven't read it perhaps there is something here,
Release: 3-button combo fix for any firmware version, that can help get you thinking on the right track.

God I need to play around a bit more and just break my phone so I have more motivation to try to get a device where I can get to recovery (I think they exist in Korea, am I mistaken?). On that note, sorry I haven't tried your method yet, I'm thinking Wednesday, tomorrow I'll be a bit busy.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 48
    efs problems and solutions

    efs folder is found in your root of your Internal Phone memory, which contains encrypted information with regards to your phone identity, passwords, baseband etc

    This folder can get corrupted or deleted when we Flash a custom rom...as many have experienced causing them to experience any of this

    1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)

    2) No Network and Signal ( calls, sms and mobile Internet not working)

    3) No base Band or Unknown Baseband

    4) Sim card lock missing

    5) Undermentioned appearing in red on your desktop after phone boots up normally
    HW: Not Active
    BOOT: SHW-M110S Vj04.1944
    PDA:SHW-M110S Vj04.1944
    Phone: M110S.VI27.0941.ST


    6) Undermentioned appearing when you try to boot
    E: failed to mount /efs (invalid argument)
    E: check_selective_file:Can´t mount /efs


    7) Undermentioned appearing when you try to boot
    E: failed to mount /efs (invalid argument)
    install_application_for_customer:Can´t mount /efs
    copy application failed.


    8) Undermentioned appearing when you try to boot
    E: failed to mount /efs (invalid argument)
    E: multi_csc: Can´t mount /efs
    Multi-csc applied failed.


    9) Undermentioned appearing when you try to boot
    E: failed to mount /dev/block/stl3 or
    E: failed to mount /dev/block/bml3 corrupted



    Hence DO YOU WANT TO RISK IT? by not making a backup of this important file , which can cause any of the above problems?

    You guessed it, the solution is to backup BEFORE flashing anything .

    How ?

    Number of ways

    1) S2 repair or Nitrility or GPS AIDS apps from google or all this

    2) You can use an application Like EFS Pro developed by an XDA member lyriquidperfection

    3) Or use a Root Explorer or any file manger with root permissions, to Zip it and save it in another location

    4) Use ADB to copy to your SD card than move it to a safe location in your PC.

    adb shell
    su
    cp -r /efs /sdcard/efs
    exit
    exit


    Remedies for those who have a efs backup

    If you Have a Backup and you want to restore it, this is one method

    1) Download Root Explorer, or Xplore, or any root browser from Play Store and use it to
    2) Search you internal SD card for sdcard/backup/efs or any other backup you have for your efs
    3) Copy nv_data.bin, nv_data.bin.md5 paste them (means overwrite existing files) into /efs in your Internal Phone memory
    4) Fix permissions by Click on efs folder and keep it pressed to open the menu and click on permissions and set them to rw_r_r_ ( Owner = read & write - Group = read only and Others = Read only), after this Save using menu and exit using menu
    5) Power down phone and reboot into recovery and wipe cache before rebooting phone to get back your original IMEI

    Another method Here or you can use the restore function in the app that you used to back it up

    If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.

    In the event you have Failed to SAVE it and now would like to solve these problems

    Following remedies available for those who DO NOT have a Backup,

    Download EFS Folders for modification and restoration My Android Collection

    These methods had worked for some but not for others.

    1) Flash a stable stock ROM preferably an earliest version
    i9000 use JVU without repartition or JVZ or JPU ( Froyo)
    M110S use Eclair DG 23
    or
    2) In recovery mode , wipe data/factory reset and wipe cache partition. Then reboot
    or
    3) Delete efs folder (by using root explorer), clear EFS (using Odin) and flashing a new ROM.
    or
    4) Replacing keystr file ( If missing) in efs > imei folder
    or
    5) For Unknown Baseband just install KIES and then connect Phone to it...
    and now Baseband will be correctly detected


    Other methods deleted by Mod
    [highlight]Mod Edit: While I understand that the purpose of this guide is to help those who have lost their IMEI's while flashing ROMS, this opens up a whole new can of worms as far as what can be done with it. The outcome is illegal in most countries in fact. Sorry.[/highlight]
    Last edited by egzthunder1; 28th August 2012 at 09:05 PM.
    Final Solution:-

    When NOTHING works and its going to drive you nuts, just walk down to your nearest Phone repair shop, find out how much they will charge for using their Riffbox/z3x/spt/octopus box to fix the IMEI, and it can be resolved in a few minutes when the problem is software related.

    IF it is Hardware related than it could be due to base-band problem and may need an IC replacement to resolve.

    to verify do the following test

    type *#06# , and IF you get message "imei null" or imei starts by 0049XXXX or 00000 it should be resolved by software .
    but IF nothing is shown when you type *#06#, that is a hardware problem or look at attached picture below.
    .


    You can do a search on this forum to see the rest of the problems and remedies associated with EFS, but seriously .....
    .DO YOU WANT THIS PROBLEM?:(

    SO BACKUP and STORE your IDENTITY :)

    ALWAYS BACKUP YOUR EFS FOLDER BEFORE FLASHING

    Check this out!You , YES! you are an " Android ". Not your phone but U.

    You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone

    How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
    thanks.jpg

    If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
    Its easier to give "Feedback" in this manner than make an additional post.​

    This file will be updated and linked to Pit Stop
    39
    [Noob Guide] Flashing and Recovery using Repair Kit on M110S

    Flashing can brick your phone but is needed to upgrade your phone or root your phone.
    So beware of the consequences arising out of using wrong firmware or incorrect flashing procedures or failing to observe requirements.


    Requirements :-

    1) PC or Laptop installed with samsung usb drivers

    2) Use Only Odin3 version 1.70 (attached below) on your PC/Laptop
    (later versions works but seem to have problem flashing Bootloader and gets stuck)

    3) The latest Stock ROM (WF07) or custom ROM (only M110S ROMS) of your choosing

    4) The Korean Galaxy S (SHW M110S) Note:- NOT OTHER MODELS OF GALAXY S

    (you can download your software requirements from Pit Stop)

    First and foremost you must UNDO any lagFix or partition you had made in your phone. Never wipe data if you had enabled Onenand Mode before! or you will end up in serious problems.

    Second in order to Save your important files like efs folder /backups/Images/ downloaded game content etc, use a file manager and copy paste them to your external SD card and remove your external SD card for safe keeping or use USB Mass Storage mode to save them to your PC/Laptop and remove external SD card

    Third you need to Format your Internal SD card by:- Touch Menu> settings> storage> unmount Internal SD card> Format and
    you need to Factory reset the phone as well by:- Touch menu> settings> Privacy> factory reset + wipe SD card

    Lastly Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>, You need to shutdown phone , boot-up into 3e recovery (press and hold Volume down + Home + Power) Here you need to wipe device as well as wipe partition and reboot.

    Make sure you have more than 50% Battery Charge and Never interrupt Flashing process and also Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
    Again check battery Level every-time before you start​

    Above are REQUIREMENTS , you MUST and HAVE to fulfill them for a clean and safe flashing process


    Flashing Procedure :-

    1) Shut down your phone and remove battery, press and hold power button for a minute than reinsert battery

    2) Put your phone into download mode Like this (press home + power buttons)

    3) run Odin, select the file (rom or kernel you wish to flash) under PDA
    (do not tick or click any other button, restart odin if you made mistakes)

    4) Connect USB cable to PC and wait for Odin com port to turn yellow Like this
    (your phone should and must be recognized)

    5) Press start and wait for the green PASS signal from ODIN Like this
    (on a successful flash, to disconnect the USB cable)

    Its all over in five seconds for a kernel and a few minutes for a Rom, IF there were no problems

    attachment.php

    6) Once your phone has rebooted and you are full of joy, shut down the phone again insert your external SD card and reboot by recovery mode (Volume down + Home + Power) Here you need to wipe device as well as wipe partition and reboot for the phone to function without complications.

    Thats it, you are on the new firmware


    But.. in download mode it may get stuck or fail to complete, thats when you need to


    1) remove battery and reinsert

    2) you may notice your phone going into upgrade mode Like this or BSOD Like this and cannot go into download mode

    3) just run Odin (when you connect phone, Odin will recognize and turn yellow)
    If not press Home + Power to enter download mode

    4) Re-Flash again after making sure you had followed above procedure No. 3 to 6 , it should pass


    In the event It failed again and again, you may need to use the repair kit to resolve this problem you can download Recovery guide or attached below

    Using Repair Kit to Unbrick M110S​
    First stage :- For every Stage of Flashing RESTART ODIN and always use Fresh ODIN

    1) download repair kit and unzip it (you will have 6 tar files)

    2) put phone into download mode after battery pull

    2) run odin and select m110s.pit under PIT (Re-partion option will be automatically ticked)

    3) select M110S-PDA-PHONE-MOVI-REV03-DG23-1409-USER.tar.md5 under PDA

    4) connect phone and Press start (within 10 min your phone will reboot into Eclair Firmware)

    attachment.php

    you will have a fully working phone after this, only needs further updates, so continue to stage 2

    Second stage:-

    1) put phone into download mode after battery pull

    2) run odin select S1_KOR_DE09.pit under PIT (make sure you UNTICK the re-partition option in Odin)

    3) select M110S-BOOT-DG23-1409.tar.md5 under CSC

    4) connect phone and press start (within a few min phone will reboot)


    attachment.php


    Third Stage:-

    1) put phone into download mode after battery pull

    2) run Odin select M110S-NPS-IMAGE-REV03-DG23-1409-USER.tar.md5 under PDA

    3) selct M110S-PHONE-REV00-DG24.0151_Develop.tar.md5 under PHONE

    4) Connect Phone and select start ( within few min phone will reboot )

    attachment.php

    Fourth Stage:-

    Your Phone is currently running its FIRST out of the box Firmware used in 2010 , so now you need to upgrade to the latest 2012 Stock ROM or Custom ROM of your choice so repeat Flashing Procedure to upgrade to Latest Firmware

    IF unable to complete repair procedure

    Final Solution:-

    After receiving many requests for help, concerning stage 2 of the repair procedure, Failing or unable to complete as it gets stuck on Boot-loader upgrade or similar

    My advice is to proceed to stage 4, meaning you Flash a Latest stock or custom after the Eclair ROM, this will solve the issue and you would be able to USE the phone .

    so if it get stuck after stage 1 ( meaning phone functions using the oldest ROM ) , just continue to stage 4 and flash the latest ROM

    You , YES! you are an " Android ". Not your phone but U.

    You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone

    How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
    thanks.jpg

    If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
    Its easier to give "Feedback" in this manner than make an additional post.​


    This Post is linked to the Pit Stop Page
    29
    Pit Stop for Anycall SHW M110S Korean Galaxy S

    Welcome to Pit Stop
    Everything for and about the Korean Anycall Galaxy S from Samsung
    Comments, Suggestion, Errors and Omissions are welcome.
    Just register at XDA and post on Anycall forum

    Be Advised that Most Mobile Phones have their own WIKI page on XDA Forum providing compiled knowledge about that particular phone and using them can provide many details that you may not be aware of, so always do a search first on the Wiki page for your unit.

    Whatever you have done or may do with your phone because someone said so, is still your responsibility ...so take your time READ carefully to avoid making mistakes in haste, be calm and recheck the details.

    Need a Guide? visit Your BEST Friend and Helper

    Need some solutions? visit Android Quick Fixes and Solutions

    Need Some Tools, Drivers and Utilities visit My Android Collection

    Did anyone help you in this Forum visit How to say Thank you


    This POST is moved to its NEW Thread at http://xdaforums.com/showthread.php?t=1856992 as it is getting Big
    20
    MediaFire downloads

    Due to increasing Help requests via private messaging for other download links, had to setup mediafire links.

    Problem in MediaFire is that you cannot upload large files, as such had to be split up

    Hence the need for HJ split http://www.mediafire.com/download.php?tltdt45u4lt9ik4 to join split files

    WF07 Stock ROM http://filerio.in/ujyx3ytggozz

    GFAN WF07 SP 8 XDA VERSION Updated 8/27/12 http://filerio.in/2wfk1uk0pv5u New or here
    GFAN WF07 SP6 XDA VERSION Updated 7/31/12 http://www.mediafire.com/?8jn5vazlezn6jal
    GFAN WF07 SP6 XDA VERSION http://www.mediafire.com/download.php?w5ccr3a68vzaba5

    GFAN SP8 Chinese Version http://www.4shared.com/rar/-qlFF49T/GFAN_M110S_FTE9K_WF07_ODEX_SP8.html?refurl=d1url


    WC13 Stock ROM
    http://www.mediafire.com/download.php?ob1pe0mgdgd9xtv
    http://www.mediafire.com/download.php?5bay0km4figi5n3
    http://www.mediafire.com/download.php?3ip8xj3aqb8u8d3
    http://www.mediafire.com/download.php?96a35txcoe31w37

    WC13 Stock Kernel http://www.mediafire.com/download.php?3oxf9xzka0zwmz3

    WC13 Rooting Kernel http://www.mediafire.com/download.php?im11dma9irrromc

    I9000 Technician Manual http://www.mediafire.com/view/?or3hgpu1bvjf103


    Repair Kit :-
    Recovery Procedure http://www.mediafire.com/?vrxqjq64ng98687 must follow step by step
    http://www.mediafire.com/download.php?l2c9fvwwbawek23
    http://www.mediafire.com/download.php?1e8u1cza9cec5nc
    http://www.mediafire.com/download.php?e08hh74b6sf9uu5
    http://www.mediafire.com/download.php?swye55u1283qh2s
    http://www.mediafire.com/download.php?pn8zhr6q3235v45
    http://www.mediafire.com/download.php?zj22z2y4esw7t5o
    http://www.mediafire.com/download.php?lcn4vsz41idac8w


    This post will be updated and Linked to Pit Stop post
    13
    Hi All,

    I'm going to put this upfront, because it's more important than the FAQ. Though there names get repeated a bit in this post, a major credit goes to Koe & Appagom for providing a lot of know-how, testing, information sharing and answers to questions users have posted here. This thread wouldn't be half as valuable without them. They should probably consider getting donate links, as it's the popular thing to do around here anyways, and I'd surely give them a few 원 for some soju or their beverage/food of choice for enhancing my phone experience. If they do decide to do something like that, I'd encourage you to do the same if you've used their methods or have even delayed taking action until you saw and read about their successes, trials & tribulations before proceeding with anything risky.

    Next important thing, please don't try to flash i9000 or any other SGS variant's firmware unless you are really prepared to experiment and fix your own problems.


    I'm writing this because perhaps it will help us SHW-m110s users spread information and have a point of reference, perhaps even bookmark, to spread information specific to our phone. Many of our questions just get posted in the most recently replied to thread with the word "Korean" in it. Part of my goal will also be to provide an area that Korean users who speak little English will be able to post and have a discussion. I will start that process on my own and enlist help from others I know. Please feel free to contribute in any way you can in any of these areas.

    With the Froyo update, I'd like to link to one of the more newsworthy and relevant development's due to increased system functionality we have at our disposal. Koe's guide on HowTo OpenVPN on the SHW-M110S (via StrongVPN and maybe others) can be found here Thanks KOE

    Tested on FroYo firmware versions DI29 and SK05

    Prerequisites:
    rooted (I also recommend SuperUser)
    busybox installed
    You understand the benefits of being able to connect to a stateside OpenVPN server.
    openVPN server account


    By request, other links to other guides or important topics available on XDA (or elsewhere) for the Galaxy S series if you haven't already come across them or just need a point in the right direction will be posted here. So, please let me know if you feel there is some other required reading before the test :p:

    [REF] BIG FAQ! {Flash/Root HOWTO} {ADB&Tutorials} {T&T} {FW-Guide} [MUST READ!]

    So, on with the FAQ/guide:

    *please note, this is a highly work-in-progress thread and is meant to be supplemental to, not in place of, better, more refined guides featured in the I9000 board. I started to plan this about 24 hours ago but there continue to be questions asked out of place so I'm rushing this a bit


    1. Where can I find ROM "(insert name)"?
    2. How do I update my phone?
    3. Can I put a ROM from the i9000 or another SGS family on this device?
    4. What frequencies does the cellular radio operate on?
    5. Does that make this a world phone?
    6. What limited functionality have users experienced overseas?
    7. How do I use Voice search in Korean?
    8. What else is different from the I9000 and other versions of the SGS?
    9. How do I root my phone?
    10. Where is Samsung Apps/Samsung Apps store?
    11. Are there any other ways to download games in Korea?
    12. Does SK Telecom support OTA updates?
    13. How do I work the DMB tuner?
    14. Why aren't the Secret Codes aren't working?
    15. Can I change the SMS character limit from 80 to 160 characters?
    16. Can we get Social Hub on the phone?
    17. I want the boot animation, do you have it?
    18. This FAQ is terrible, but I have a question...

    1. Where can I find ROM "(insert name)"?
      Koe seems to have kept a good list, here.
    2. How do I update my phone?
      Download Kies 2.0 here > click on the magnifying glass to the right of "Kies" > click on the white button "Kies 다운로드" > run the file > install > important set your location (left box) to Korea (I assume this to be the default) and your language (right box) can be the language of your choosing.
    3. Can I put a ROM from the i9000 or another SGS family on this device?
      This is one of those, 'if you have to ask...stay far far away questions'. Essentially you can come in here if you want a suggestion on what ROMs we might be using at the time, but no, for the love of God don't ask about i9000 or other device ROMs. If you know how to get yourself out of a pickle you wouldn't even need to ask, and if you try and fail you'll be asking us to get you out.

      Right now most users are content with z4mod, though there are some Korean ROMs that will be brought up from time to time.

    4. What frequencies does the cellular radio operate on?
      *To be updated*
    5. Does that make this a world phone?
      XDA users have reported some phone functionality in Russia and the Philippines. And know specific carriers in the US that the phone may/may not be compatible with, and if this will work for users in the EU. It seems that most people, if they have the right APN information, have gotten working this in a variety of countries though there will be at least some U.S. carriers that aren't available and potentially other non-standard frequency users. Still, if I were living in another country I'd probably only get this from a distributor who I'd be able to get a refund from if I couldn't get it working - anything else and you're doing so at your own risk.
    6. What limited functionality have users experienced overseas?
      User ulrauko has reported no data functionality on his device in Russia.
      It is recommended to work with a local carrier to get APN information to enter into your settings in order to maximize phone functionality. Some users may continue to have 3G problems after this, it might be possible to check setting "data roaming" in wireless & network > Mobile networks, but it'd be wise to check with your carrier to see what happens if you end up roaming onto another carriers towers.
      Users precious_mew has reported that he can't use MMS due to his carrier while chester_go has reported an inability for his phone to see his phone number requiring him to edit his phone number (to any number, not necessarily his actual number) to send SMS without any problems receiving SMS. Since then, Chester has been able to "program" his SIM by using the following method:
      -Removing the SIM card
      -Placing it in another phone that has the "My Number" option (I used an iPhone, heard that older Sony Ericssons work too.)
      -Entering my own number in international format (+63917~) (Prior to this, "Unknown" was also shown in the iPhone.)
      -Inserting the SIM back to the M110s.

    7. How do I use Voice search in Korean?
      Voice Search can be changed in settings>voice & input>voice recognition settings>lanugage...
    8. What else is different from the I9000 and other versions of the SGS?
      For now, I assume that we have different cellular radios. Also, we have a T-DMB tuner. We were given different stock software, originally missing Swype and a few other things, since then we have received Swpye through a firmware upgrade. We do utilize different firmware for our SHW-m110s than the typical international versions.
    9. How do I root my phone?


      Appagom's Evolving, and well well-supported, Post.

    10. Where is Samsung Apps/Samsung Apps store?
      The Samsung Apps store in Korea is a subset of SK Telecom's store, I highly doubt this would be accessible overseas as I think it's SIM card dependent. There you will find a full version of Asphalt for a free download. Please note, some games, even western games such as Farm Frenzy only have Korean language menu, while Asphalt has both English and Korean. I'd also guess there is no 24 hour return policy, but any confirmation would be great, and I have to presume that charges will be added to your monthly phone bill. *As of Froyo SK has partially, and poorly, integrated part of their(?) app store into the marketplace in a separate tab called "SKT"
    11. Are there any other ways to download games in Korea?
      Being rooted will allow you to run MarketEnabler and fake a SIM code to be in one of a few countries. I don't think anyone on this thread knows the legality of such actions, so do so at your own risk.

      *Note, as of Nov 15th, the Froyo update fast web installer is not functional. Will update if there is a change and I remember. Also, see Koe's guide to getting VPN working which can give you access to location restricted apps.
      I hold out hope that fast web installer for AppBrain will be updated to work on the SGS, there are reports that some items such as GoogleEarth can be installed in this manner where users can't find the app in the marketplace.
      There are also always "other ways" amongst them there are 3rd party sites such as slideme.org where you can find both paid and free games (some of which might not be available in the marketplace due to developer preference and/or marketplace restrictions). Slideme will work direct on the phone and you can also use it on your PC to download and sideload apps. As a matter of fact, games can be found by developers here at XDA which can be sideloaded. If you root your phone you will, hopefully, be able to use market enabler to sign as though you aren't in Korea (use wifi + airplane mode) and be able to download games directly from the marketplace. Additionally there are always the less legitimate ways.
    12. Does SK Telecom support OTA updates?
      User akbk84 reported to me in August that he did receive an OTA udpate. However, this was weeks after I had received my first, and I was perhaps on my 3rd or 4th update by then. He She (my apologies :D) did, however, receive the most current update. I do not know what SK/Samsung plan going forward, perhaps just critical updates will be OTA. I personally have, and I kind of recall reading someone else might've, received an OTA camera update.

      Update: In the t-store there is an app called T-Upgrade, we believe it is supposed to give OTA updates to the phone. After downloading it didn't help me get the newest FW, so I'll post further information when I hear of a success story.

    13. How do I work the DMB tuner? The DMB tuner works best with the DMB antenna extended. Extend the DMB tuner, located on the top right of the phone above the power button.
    14. The secret codes were changed, or removed from, or broken during, an August firmware update. For now, we will keep a running list of working secrete codes here:

      TouchKey F/W Info - *#86824#
      - Has an "F/W Update" Button
      - Can set the "Menu" and "Back" key sensitivity

      SKT Admin menu (general settings, such as: network, system, sms, etc.)
      From the dialer enter: 319712358
      You will be prompted for a pasword: 774632

      thanks koe1974
    15. Can I change the SMS character limit from 80 to 160 characters?
      This seems to be a common question posed from people living outside of Korea. Handcent defaults to 160 characters before changing the message to an MMS, how this will affect your message setting and carrier costs have never been verified so please do some sort of conclusive test and update us. Within Korea, MMS/SMS have the same pricing and free allotment, so it doesn't seem to be necessary to have the 160 character difference, also I haven't heard anything about how this might affect the messages and how SKT would deal with and treat extra long SMS messages.
    16. Can we get Social Hub on the phone?
      As far as I know, no one has successfully extracted and loaded Social Hub onto our phones.
    17. I want the boot animation, do you have it?
      Yes, please go to this post for more information.
    18. This FAQ is terrible, but I have a question...
      Please ask, provide better answers, do whatever to help us improve our SHW-m110s experience.
    Thanks all!