Database Develop

[REF] [Repost] Back up your EFS. Everyone needs to do this.

First things first, I did NOT write this; however I am reposting this here because I think it's extremely important everyone do this. Find OP here, guide was originally written by Candanga. Please hit thanks on his post and show him love for the write up.
-----------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone (my case).
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centers.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
Please don’t ask how to recover your IMEI if you have previously messed your SGS without backing up this folder. I’m not familiar with such methods plus it is UNRELATED to this thread.
What you will need:
Rooted SGS to get permissions as a SU (Super User) and perform the backup
I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile.<- Busybox Commands(or Google them)
Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
--------------------------------------
Backup commands
--------------------------------------
Depending on the type of root, you might have to use “busybox” at the beginning of the sting or just the string:
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS during this process, because it will request SU permissions; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS. Once you are finished with the files, you need to turn it off so you can get the files.
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs or
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
In another forum I also saw a recommendation to back up the st13 under /dev/block which can support greatly to recoveryour IMEI in case of a screw-up:
Code:
su
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img or
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Same thing, the target is the INTERNAL SDCARD, so go ahead and copy the file.
----------------------------
nv_data.bin - Restore
----------------------------
In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC
You may want to upload your fresh copy of this file back to the phone. Use this commands:
(thanks to Methyldioxide method to recover the product code http://forum.xda-developers.com/showthread.php?t=780509 )
Copy the file from your backup (efs-backup.tar.gz) and paste it in the INTERNAL SDCARD:
Code:
cp /sdcard/nv_data.bin /efs/nv_data.bin
rm -rf /efs/nv_data.bin.md5
Reboot your SGS
The md5 hash/signature is removed (rm) as the system will generate a new one.
**Most likely your SIM code won’t work after this and you won’t be able to log into the phone**
Pop off your SIM card, boot your SGS and execute the following commands to change ownership of the file under ADB or Terminal as well:
Code:
su
busybox chown 1001:1001 /efs/nv_data.bin or
chown 1001:1001 /efs/nv_data.bin
Hope this can help anyone with doubts. Cheers!

I use SGS Toolbox to back up my efs; is that sufficient?
It's on the market for less than $2, and has a ton of other features so well worth the money regardless.
Sent from my rough sketch of a Vibrant on a brick.

Droidificator said:
I use SGS Toolbox to back up my efs; is that sufficient?
It's on the market for less than $2, and has a ton of other features so well worth the money regardless.
Sent from my rough sketch of a Vibrant on a brick.
Click to expand...
Click to collapse
yeah that should do it, but it never hurts to do it again

I read this from the original op, back then when I was trying to change the IMEI. But good you posted this, easier to find.

[Solved] LGMobile Support Tool Issue (won't install)

Everytime I try to install the LGMobile Support Tool it won't go any further on the progress bar than just above the 'ob' of LGMobile.
Has anyone else had this issue and managed to resolve it - i know there was a thread back in may but nothing since then
I've tried both on a windows7 x64 and windows xp sp3 machines
regards
this is just a quick update and may help others who end up having same issues - the reason the app freeses during install is because it accesses the internet on port 9002 - once you allow this port outbound on your router/firewall the installation will work fine.
Do not remove the setting otherwise you can't run the app after it's installed as it connects to internet again..
regards

Mine didn't install on win 7 64 bit
Xp sp2 was totally fine
Sent from my LG-P990 using XDA App

Hi i have same problem,but i don´t know how to allow 9002 port a tried to look for tutorials on google but i didn´t find anything that works and i still cant istall lg mobile support tool

What router do you have Branding/model?

internet explorer
sani340 said:
Hi i have same problem,but i don´t know how to allow 9002 port a tried to look for tutorials on google but i didn´t find anything that works and i still cant istall lg mobile support tool
Click to expand...
Click to collapse
hi, i had the same problem and was able to install the update tool on internet explorer instead of google chrome. thought it might be helfull

the thread is written solved but we actually needs step by step guide.

how?????
walkerx said:
Everytime I try to install the LGMobile Support Tool it won't go any further on the progress bar than just above the 'ob' of LGMobile.
this is just a quick update and may help others who end up having same issues - the reason the app freeses during install is because it accesses the internet on port 9002 - once you allow this port outbound on your router/firewall the installation will work fine.
Do not remove the setting otherwise you can't run the app after it's installed as it connects to internet again..
regards
Click to expand...
Click to collapse
HOW do you do that??????

wee2000 said:
the thread is written solved but we actually needs step by step guide.
Click to expand...
Click to collapse
Yes, how did you solve this??

I would like to say some really bad word for the OP, as this kind of behavior is the worst!!!
F YOU MAN!
there is nothing worse than presenting the problem, and telling after that: "ok I solved it, move on ..." << well youare a douche. biggest one there is.

Change hosts file
Hi there all, I had the same problem and solve it while going to hosts file C:\Windows\System32\drivers\etc
Open up hosts file with notepad and delete any line that does not have hashtag "#" in front.
So it should look something like this :
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for
# Windows.
#
# This file contains the mappings of IP addresses to host
# names. Each # entry should be #
# kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding
# host name. # The IP address
# and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on
# individual # lines or following
# the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
#
#
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Save it, File --> Save ot Ctrl+S and close. Double click on B2CAppSetup.exe and let me know if it worked for you.
Cheers

Unable to Install the LG MOBILE SUPPORT TOOL
Klindic said:
Hi there all, I had the same problem and solve it while going to hosts file C:\Windows\System32\drivers\etc
Open up hosts file with notepad and delete any line that does not have hashtag "#" in front.
So it should look something like this :
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for
# Windows.
#
# This file contains the mappings of IP addresses to host
# names. Each # entry should be #
# kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding
# host name. # The IP address
# and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on
# individual # lines or following
# the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
#
#
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Save it, File --> Save ot Ctrl+S and close. Double click on B2CAppSetup.exe and let me know if it worked for you.
Cheers
Click to expand...
Click to collapse
The above method didn't work for me. Please help suggest an alternate method or another OS build where this might work.

I know it's old post but today i have problem installing lg mobile support tool.
i install lg pc suite first and then voila lg mobile support tool installed.

Igoritza said:
I would like to say some really bad word for the OP, as this kind of behavior is the worst!!!
F YOU MAN!
there is nothing worse than presenting the problem, and telling after that: "ok I solved it, move on ..." << well youare a douche. biggest one there is.
Click to expand...
Click to collapse
WTF are you *****ing about??? He thinks he solved the problem by allowing port 9xxx (it is not the solution, but all the same...) and now you would like someone to solve it for you at your home on your own router?!?!?
F U man!! what else would you like???

in your windows explorer, right click on the downloaded setup file named "LGMobileSupportTool" and go to file properties. In the attributes section, check Unblock. You must have administrator privileges. Run the file as admin.

Hi guys, in my case it was caused by running LG Bridge app on the background so go to tray and kill this app then installer of support tool was able to finish loading.

Hello everyone
I am more than aware that this is a very old thread, so let me explain myself a bit.
Basically, i have an old optimus l7 ii (wrong phone for this thread, ik but where else am i going to ask) that i want to update to kitkat from jb. to do that, i have to install this tool for the cse flash in lg flash tool 2014 to work. problem is the exact same one as in the original post, except none of the methods mentioned here worked for me. not opening port 9002,editing the hosts file, closing lg bridge, running it as admin, nothing at all. i think the reason why it doesn't work might be because the servers needed for the installer to work are down (what with lg now having shut down their mobile division and everything). still though, i need some way for this to actually work (if there is one even at this point)

Switch Internal To External

I got this method HERE. It works on AHD. And it's better than script autorun in init.d. You can use my modified build.prop and vold.fstab. Just copy build.prop to /system and vold.fstab to system/etc and set permission to -rw -r -r. It replaces your internal with external and you can have 5gb free to store your installed apps. You can store game data on your sdcard. This is great! Thanks a lot to ZaYAC-ua!
Here's my modified build.prop and vold.fstab which I only tested on Stock JB ROM : https://www.box.com/s/8l7hwc9xir746ot0z1hw
Here's another modified build.prop and vold.fstab which I've tested on CM10 : https://www.box.com/s/w51ji42yunoof8iyzaaa
Here's for CM10.1 ROM : https://www.box.com/s/d4to8rifptb545iyxy4z. Copy 11extsd2internalsdCM10-1 to your init.d folder in /system/etc. Don't forget to set permission to -rw -r -r. Credit goes to Youngunn2008.

What about current games and apps in internal storage? May Applying this affect them or I must re-install?

devilsking said:
What about current games and apps in internal storage? May Applying this affect them or I must re-install?
Click to expand...
Click to collapse
You should do this edit on completely stock rom without any apps installed on internal. Factory reset first and it should be running fine.
Btw,I added another modified build.prop and vold.fstab which I've just tested on CM10.

huatz84 said:
You should do this edit on completely stock rom without any apps installed on internal. Factory reset first and it should be running fine.
Btw,I added another modified build.prop and vold.fstab which I've just tested on CM10.
Click to expand...
Click to collapse
hi, i tried this but what happend is after i restart after the motorola dual core and turn out completely black. i dont know if i did right. i put the swapping folder in the internal memory of the phone and then i opened theRoot Explorer and copy the buildprop and paste and replace the existing files and same also what i did to void.fstab copy and replace in system/etc after this I turn off then turn on then turn into black. now i just run my phone to rsdlite to bring it back. thanks

ryuben2k said:
hi, i tried this but what happend is after i restart after the motorola dual core and turn out completely black. i dont know if i did right. i put the swapping folder in the internal memory of the phone and then i opened theRoot Explorer and copy the buildprop and paste and replace the existing files and same also what i did to void.fstab copy and replace in system/etc after this I turn off then turn on then turn into black. now i just run my phone to rsdlite to bring it back. thanks
Click to expand...
Click to collapse
Have you set permissions of both files? It should be -rw -r -r.

huatz84 said:
Have you set permissions of both files? It should be -rw -r -r.
Click to expand...
Click to collapse
Sorry but how to I do that? Because what I did is i just hold the file that I download and went to /system and paste ( ask me if I want to replace the existing file) and click Mount R/W to paste. Mounted to R/O will change to R/W. same with vold.fstab. thanks
Sent from my MB886 using xda premium

With root explorer,browse to build.prop and hold until popup some menus and choose permission. Look at my screenshots. Do the same with vold.fstab.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT925 using Tapatalk 2

huatz84 said:
I got this method HERE. It works on AHD. And it's better than script autorun in init.d. You can use my modified build.prop and vold.fstab. Just copy build.prop to /system and vold.fstab to system/etc and set permission to -rw -r -r. It replaces your internal with external and you can have 5gb free to store your installed apps. You can store game data on your sdcard. This is great! Thanks a lot to ZaYAC-ua!
Here's my modified build.prop and vold.fstab which I only tested on Stock JB ROM : https://www.box.com/s/8l7hwc9xir746ot0z1hw
Here's another modified build.prop and vold.fstab which I've tested on CM10 : https://www.box.com/s/w51ji42yunoof8iyzaaa
Click to expand...
Click to collapse
///////////////////////////////////////////////////////
vold.fstab in ics 404 the line reads
dev_mount sd card /mnt/external1::lun auto /devices/platform/msm_sdcc.3/mmc_host
what can be done/add to swap?
the phone factory name of devices are
internal storage /mnt/sdcard
sd card /mnt/external1
usb disk /mnt/usbdisk_1.1.1
thankyou

htchd2fix said:
///////////////////////////////////////////////////////
vold.fstab in ics 404 the line reads
dev_mount sd card /mnt/external1::lun auto /devices/platform/msm_sdcc.3/mmc_host
what can be done/add to swap?
the phone factory name of devices are
internal storage /mnt/sdcard
sd card /mnt/external1
usb disk /mnt/usbdisk_1.1.1
thankyou
Click to expand...
Click to collapse
Can you upload ics vold.fstab? I'll take a look at it.
Sent from my XT897 using Tapatalk 2

Thank you, i finally did it. Like to ask the advantage of it?
Sent from my MB886 using xda premium

ryuben2k said:
Thank you, i finally did it. Like to ask the advantage of it?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
You don't have to worry about internal low space anymore. You can store a huge game data. Real Racing 3,Dark Knight Rises,Amazing Spiderman,MC4,NFSMW won't be a problem now. You just have to buy an external sdcard. I'm using 32gb Team class 10. Waste no more space. Make it fully loaded..lol
Sent from my XT897 using Tapatalk 2

huatz84 said:
Can you upload ics vold.fstab? I'll take a look at it.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
/////////////////////////////////
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point[:[asec_point]:[lun_point]]> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## asec_point - Whether asec mount is needed for this value, if not, use "none"
## Else, supply a folder name under /mnt/secure/
## If not supplied, "asec" will used by default
## If supplied, /mnt/secure/asec_point will be used
## This is for further extension, not needed now
## lun_point - The target lun device for this volume. If not supplied, will use
## /sys/devices/platform/usb_mass_storage/lun0/file
## else, will use /sys/devices/platform/usb_mass_storage/lun_point/file
## part - Partition # (1 based), or 'auto' for first usable partition.
## For a disk with only 1 partition, use '1' is different to 'auto'
## Using 1, will not re-write its partition table when formatting
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/external1::lun auto /devices/platform/msm_sdcc.3/mmc_host
dev_mount usbdisk_1.1.1 /mnt/usbdisk_1.1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1:1.0
dev_mount usbdisk_1.1 /mnt/usbdisk_1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.1
dev_mount usbdisk_1.2 /mnt/usbdisk_1.2 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.2
dev_mount usbdisk_1.3 /mnt/usbdisk_1.3 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.3
dev_mount usbdisk_1.4 /mnt/usbdisk_1.4 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.4
dev_mount usbdisk_1.5 /mnt/usbdisk_1.5 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.5
dev_mount usbdisk_1.6 /mnt/usbdisk_1.6 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.6
dev_mount usbdisk_1.7 /mnt/usbdisk_1.7 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.7
//////////////////////
Here u go
Thanx

huatz84 said:
You should do this edit on completely stock rom without any apps installed on internal. Factory reset first and it should be running fine.
Btw,I added another modified build.prop and vold.fstab which I've just tested on CM10.
Click to expand...
Click to collapse
After the switch, was you able to see the content of the external (was internal)? In my case, I have to use the "bind" script in order to see it.

htchd2fix said:
/////////////////////////////////
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point[:[asec_point]:[lun_point]]> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## asec_point - Whether asec mount is needed for this value, if not, use "none"
## Else, supply a folder name under /mnt/secure/
## If not supplied, "asec" will used by default
## If supplied, /mnt/secure/asec_point will be used
## This is for further extension, not needed now
## lun_point - The target lun device for this volume. If not supplied, will use
## /sys/devices/platform/usb_mass_storage/lun0/file
## else, will use /sys/devices/platform/usb_mass_storage/lun_point/file
## part - Partition # (1 based), or 'auto' for first usable partition.
## For a disk with only 1 partition, use '1' is different to 'auto'
## Using 1, will not re-write its partition table when formatting
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/external1::lun auto /devices/platform/msm_sdcc.3/mmc_host
dev_mount usbdisk_1.1.1 /mnt/usbdisk_1.1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1:1.0
dev_mount usbdisk_1.1 /mnt/usbdisk_1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.1
dev_mount usbdisk_1.2 /mnt/usbdisk_1.2 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.2
dev_mount usbdisk_1.3 /mnt/usbdisk_1.3 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.3
dev_mount usbdisk_1.4 /mnt/usbdisk_1.4 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.4
dev_mount usbdisk_1.5 /mnt/usbdisk_1.5 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.5
dev_mount usbdisk_1.6 /mnt/usbdisk_1.6 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.6
dev_mount usbdisk_1.7 /mnt/usbdisk_1.7 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.7
//////////////////////
Here u go
Thanx
Click to expand...
Click to collapse
There's a different mount point on ICS. I think maybe ICS has mass storage mode. I can't be sure to mount the exact point. You can try adding line like this :
dev_mount external1 /sdcard auto /data/media
Make no changes in first line. Then,adding line like above.
tvd0405 said:
After the switch, was you able to see the content of the external (was internal)? In my case, I have to use the "bind" script in order to see it.
Click to expand...
Click to collapse
You can't see internal after doing it. Your internal will be storage for apps now. It's 5gb free space you can use to store installed apps. It's not shared anymore.
Sent from my XT925 using Tapatalk 2

huatz84 said:
There's a different mount point on ICS. I think maybe ICS has mass storage mode. I can't be sure to mount the exact point. You can try adding line like this :
dev_mount external1 /sdcard auto /data/media
Make no changes in first line. Then,adding line like above.
You can't see internal after doing it. Your internal will be storage for apps now. It's 5gb free space you can use to store installed apps. It's not shared anymore.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Can I do the vise-versa way: converting external to internal?

huatz84 said:
There's a different mount point on ICS. I think maybe ICS has mass storage mode. I can't be sure to mount the exact point. You can try adding line like this :
dev_mount external1 /sdcard auto /data/media
Make no changes in first line. Then,adding line like above.
You can't see internal after doing it. Your internal will be storage for apps now. It's 5gb free space you can use to store installed apps. It's not shared anymore.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
Interesting. Now I am confused to what I see after the binding.
Sent from my XT925 using Tapatalk

the_onlysun said:
Can I do the vise-versa way: converting external to internal?
Click to expand...
Click to collapse
To restore back to stock mount,just erase build.prop and vold.fstab. Rename build.prop.bak and vold.fstab.bak to build.prop and vold.fstab.
Sent from my MB886 using Tapatalk 2

huatz84 said:
To restore back to stock mount,just erase build.prop and vold.fstab. Rename build.prop.bak and vold.fstab.bak to build.prop and vold.fstab.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
If i will reset to factory, it will return back to internal/external or only if i use rsdlite? Or if i flash other rom. Thanks
Sent from my MB886 using xda premium

ryuben2k said:
If i will reset to factory, it will return back to internal/external or only if i use rsdlite? Or if i flash other rom. Thanks
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
It will be disappeared once you update to another rom via cwm or rsd lite.
Or just remove build.prop in system and vold.fstab in system/etc. Then,rename build.prop.bak to build.prop and vold.fstab.bak to vold.fstab.
Sent from my MB886 using Tapatalk 2

huatz84 said:
I got this method HERE. It works on AHD. And it's better than script autorun in init.d. You can use my modified build.prop and vold.fstab. Just copy build.prop to /system and vold.fstab to system/etc and set permission to -rw -r -r. It replaces your internal with external and you can have 5gb free to store your installed apps. You can store game data on your sdcard. This is great! Thanks a lot to ZaYAC-ua!
Here's my modified build.prop and vold.fstab which I only tested on Stock JB ROM : https://www.box.com/s/8l7hwc9xir746ot0z1hw
Here's another modified build.prop and vold.fstab which I've tested on CM10 : https://www.box.com/s/w51ji42yunoof8iyzaaa
Click to expand...
Click to collapse
thanx ....it works......
i tryed the other metod with no success....
finally i can use my fat 64gig memory card....
now we need a superKernel.....
come on.......

[GUIDE] Recover your Ace-i baseband after flashing incorrect Odin Package

How to recover your Galaxy Ace's baseband
ONLY FOR WORKING DEVICES, THIS IS NOT A GUIDE ON HOW TO UNBRICK
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, etc. Please do some research if you have any concerns about the
* topics included in this guide before following it! YOU are choosing to
* follow these steps, and if you point the finger at me for messing up your
* device, I will laugh at you.
*
* For any further assistance, please reach an authorized technical service.
*/
a)Pay close attention to the way the commands are shown below, i.e. it's BML not BM1, but not in caps, in minus: bmlXX where XX is the corresponding number.
b)Make sure there is enough space on /sdcard/ at least 50 megabytes to be sure no app will take over that space
c)Use extreme caution when following this guide, you're messing with the bootloader here, if you are doing it wrong, you'll kill your phone with no chance of easy-homemade-recovery like Odin or a USB Jig.
d)If you definitely did it wrong, and no recovery method helps, prepare your pocket to take your phone to a specialized tech center.
This is a very simple tutorial for those of us you who after a really, really bad brick had been seen in the need to flash a determined firmware which is not the corresponding to your phone's country. Well, fear not for I have come to save your 3G!!!
Steps:
Get a phone of the exact same model as yours, in stock (this is important because that will determine if the settings being applied are the actual facotry ones). We will refer to this as the Source phone
Root the source phone, if it's not already rooted (again, this is important, 'cause a non-rooted phone might not allow us to read /dev/bml partitions and/or execute dd command well, although I have to investigate that)
Install terminal emulator on the source phone, if it's not already installed. Alternatively, you can enable USB Debugging and use ADB instead
input the following commands (mind the caps):
Code:
# dd if=/dev/bml1 of=/sdcard/Boot_img/BcmBoot.img
# dd if=/dev/bml13 of=/sdcard/Boot_img/sysparm_dep.img
# dd if=/dev/bml14 of=/sdcard/Boot_img/HEDGE_NVRAM8_RF_LE.bin
I have used the directory "Boot_img/" for this case, you can use whatever you want lol :cyclops: but it's important to have these 3 files by themselves as we're putting them into a tar file
Perform the command (For the example I've used BOOT_S5830CVJKL4, but you should use the model name for the boot from the Source phone):
Code:
# cd /sdcard/Boot_img/
# tar -cf BOOT_S5830CVJKL4.tar ./*
Dismiss the Source phone, and ready up the "Target" phone, the one to have the newly created boot image applied.
Place the Target phone in download mode
Grab Odin3_V3.07 (Proven to work best with the Ace-i)
Once your phone's been detected, select the PIT file and the Bootloader file (I'm not telling you how to do it here, there are good ODIN tutorials for the Ace-i and I assume you search for them)
Start flashing
?????????????
PROFIT!
There is no need to revert to stock actually, although it *might* be a better idea to flash this over stock rom lol, there's less chance of bricking.
Credits:
@lyriquidperfection for the PIT Magic application, which has perfect and wonderfully helped me determine the necessary partitions to pick.
@feetsonfire for an awesome guide on flashing via ODIN
Anyone else who I may have missed, you can mention them below

Nice guide, dude! It will help all peoples, who got same like this one.
Pretty one but, i'm don't get this same problem like this guide.

I might add that use EXTREME caution using dd command and write the EXACT words as here because flashing a simple wrong partition can easily hard brick your phone.
DO NOT CONFUSE l with 1
And whichever path you choose in your sdcard, mind that it doesn't have space (you know it breaks the command)

iamareebjamal said:
I might add that use EXTREME caution using dd command and write the EXACT words as here because flashing a simple wrong partition can easily hard brick your phone.
DO NOT CONFUSE l with 1
And whichever path you choose in your sdcard, mind that it doesn't have space (you know it breaks the command)
Click to expand...
Click to collapse
Adding these details to OP, as small they may be, they are certainly true and very important

Towelroot exploit for i9305 – source code

Hi,
I9305 is not officially supported by towelroot. So I searched for some details about the exploit and found this pastebin.com/A0PzPKnM (which seems to be decompiled and cleaned - made more readable towelroot v1) and some articles about how its supposed to work (blog.nativeflow.com/the-futex-vulnerability and tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/). I have to admit that I don’t understand it fully, but well enough to modify it to this pastebin.com/1fdmC4Xv , which is working exploit on my i9305 with Android 4.3, kernel 3.0.31. I didn’t make any big changes – I made few modifications to compile the code, added lots of debugging output, changed what happens when the hack is successful and added the iov_index variable, which is the most important change. The original code is not nice and my changes are not nice neither, please be lenient while reading it. If you want to use it, compile it with android ndk, push to /data/local/tmp and run. There can be one argument, number from 0 (default) to 7 (you can use bigger, but it makes no sense). If it succeeds, you’ll get root prompt. Otherwise it can freeze or reboot the phone. You can check the kernel panic reason in /proc/last_kmsg. If you see that it crashed in plist_add because “Unable to handle kernel NULL pointer dereference at virtual address 0000000c”, subtract 0xc from the address and use as the argument (iov_index) next time. Don’t give up, it doesn’t work always. Note that, the phone will reboot after you quit the root shell. Its up to you what you do with this, but AFAIK successful execution of this exploit doesn`t change the KNOX warranty bit, at least my phone still says that the system is “official”.
Remember to be careful, when doing anything of this and don’t blame for any damage.
If you want to play with it in debugger, you don’t have to use the android emulator as suggest in the article mentioned above – I used vanilla kernel 3.0.31 compiled with exynos4_defconfig, buildroot userspace and latest qemu with the machine smdkc210.
Pavel
P.S. I don`t have enough posts here, so you have to use the links manually

prqek said:
Hi,
I9305 is not officially supported by towelroot. So I searched for some details about the exploit and found this pastebin.com/A0PzPKnM (which seems to be decompiled and cleaned - made more readable towelroot v1) and some articles about how its supposed to work (blog.nativeflow.com/the-futex-vulnerability and tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/). I have to admit that I don’t understand it fully, but well enough to modify it to this pastebin.com/1fdmC4Xv , which is working exploit on my i9305 with Android 4.3, kernel 3.0.31. I didn’t make any big changes – I made few modifications to compile the code, added lots of debugging output, changed what happens when the hack is successful and added the iov_index variable, which is the most important change. The original code is not nice and my changes are not nice neither, please be lenient while reading it. If you want to use it, compile it with android ndk, push to /data/local/tmp and run. There can be one argument, number from 0 (default) to 7 (you can use bigger, but it makes no sense). If it succeeds, you’ll get root prompt. Otherwise it can freeze or reboot the phone. You can check the kernel panic reason in /proc/last_kmsg. If you see that it crashed in plist_add because “Unable to handle kernel NULL pointer dereference at virtual address 0000000c”, subtract 0xc from the address and use as the argument (iov_index) next time. Don’t give up, it doesn’t work always. Note that, the phone will reboot after you quit the root shell. Its up to you what you do with this, but AFAIK successful execution of this exploit doesn`t change the KNOX warranty bit, at least my phone still says that the system is “official”.
Remember to be careful, when doing anything of this and don’t blame for any damage.
If you want to play with it in debugger, you don’t have to use the android emulator as suggest in the article mentioned above – I used vanilla kernel 3.0.31 compiled with exynos4_defconfig, buildroot userspace and latest qemu with the machine smdkc210.
Pavel
P.S. I don`t have enough posts here, so you have to use the links manually
Click to expand...
Click to collapse
Hi! I use I9305 with android 4.4.4 - without any branding. Could U help me with root this device without knox flag? Thank u, I'm from polish and my english is soo bad ;/ I want ready aplication to install if u could do this for me

wow thanks you

Hi schizyk12,
I am afraid, that I will disappoint you. I don`t have any other phone than my i9305 with 4.3, so it would be a blind shot to create such an application. Even if I had some more devices, I am not sure if I have time to do this. Another problem is that I am not even sure whether this would work on 4.4.4. What kernel does it use? See this www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3153 , if your kernel version is higher than 3.14.5 then the bug this is exploiting is fixed. If you kernel is build after May 26th, 2014, it is also probably fixed.
I am attaching the binary that worked for me. You can try it - unzip it and pull it into /data/local/tmp using adb (if you don`t know how to do it, search the web, it`s not difficult) and execute from adb shell as /data/local/tmp/tr_c 1 (or some other integer, see my original post). Keep trying, it may not work for the first time. If it succeeds, you will see something like this:
Code:
cpid3 resumed.
hack.
/system/bin/sh
[email protected]:/data/local/tmp #
If your phone reboots, it is a good sign – the bug is probably not fixed.

I also have i9305 with Android 4.3 (kernel 3.0.31) and everything seems to work fine - when I execute tr_c 1 it displays a lot of lines but there are few, which look exact same like in your post above. Now the problem - this method doesn't give me root access... I don't know what is wrong. Can you help me with this? Maybe you know how to get it working? Thanks for all of your work PS: Sorry for my english.

What do you mean by root access? This is not one the “one click root” applications, this is only the exploit. If you see at the end what I posted in my previous post, you have root access, but only in that one session. If you want to have rooted device, you have to do the rest manually. Unfortunately I didn`t find any article describing what this means. There are only lots of “one click” apps. Finally I used Koushiks Superuser – it is simple and opensource, so it was quite easy to find how the installation (“rooting”) works. Take a look at this script github.com/koush/Superuser/blob/master/Superuser/assets/update-binary . Don`t execute it, it is supposed to be run from recovery. Here are briefly the steps to be done (I hope I didn`t forget anything, don`t do it if you don`t understand it):
1) mount -oremount,rw /system
2) copy su to /system/xbin
3) chown it 0:0 and chmod it to 6755
4) create link from /system/bin/su to /system/xbin/su
5) modify (or create) /system/etc/install-recovery.sh (see github.com/koush/Superuser/blob/master/Superuser/assets/install-recovery.sh)
6) sync and reboot
I actually used the disabled ssh service from /init.rc and I am enabling it install-recovery.sh, so if the su daemon is killed, it is restarted automatically. The daemon is needed because of bypassing SELinux, the suid bit is not enough (I suppose I can chmod to 755 in step 3).
You don`t have to compile the whole supperuser, you can download it from here www.koushikdutta.com/post/superuser .
But there is one problem with this version – if the selinux is enforcing, the su works only from adb shell. It is because the socket used for communication between su and daemon is in /dev, which is not accessible by applications. So I moved it to /data/local/tmp/. Now it works for apps and not for adb shell. But you have to compile the su binary to do this. I should report a bug to Koushik.... Also adding setenforce 0 to install-recovery.sh should help, but it turns off SELinux.
Pavel

Yeah, I thought it will be something like "one-click root". Now I understand - I had root access from adb but not normally rooted phone I read your instructions and I have more questions. Did you do this on your phone? Is the warranty void still 0 after these operations? I don't want to change it to 1
PS: I'm not sure if I can make this work, so I must live without root on this device since it'll be easier to do

I*did all of this on my phone I don`t see any triangle like here www.mobot.net/samsung-galaxy-s2-removing-yellow-triangle-37410 . The know warranty void in download mode says 0, so I guess it is OK. But the device status in settings says custom, but this happened after I removed knox related applications. I didn`t try to put them back. It may fix it. If I remember well, the step I described didn`t change any of these bit and statuses.
It`s not so difficult, you just need some understanding how Linux system works.