Hey guys, worst part about samsung devices is always their EFS issues.. my samsung tool app has already gained support for SM-G900A, SM-G900F, SM-G900H, SM-G900T before root and custom roms are available, so first thing is first, root(when available) and backup EFS!
ive kept all downloads and discussion within the original thread here! - SAMSUNG TOOL APP HERE
this was made possible by leoaudio13 dumping his partition table!
I love u mate!
Sent from my SM-G900F using Tapatalk
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
leoaudio13 said:
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
Click to expand...
Click to collapse
gonna be hard though!
leoaudio13 said:
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
Click to expand...
Click to collapse
actually thats not hard with root. lol
I'm working on recovery. waiting to hear back from tester(s) to see if we have a working img yet.
PlayfulGod said:
actually thats not hard with root. lol
I'm working on recovery. waiting to hear back from tester(s) to see if we have a working img yet.
Click to expand...
Click to collapse
it wasnt hard without root either
ricky310711 said:
it wasnt hard without root either
Click to expand...
Click to collapse
well you didnt get me the boot/recovery dumps til afterwards.
PlayfulGod said:
well you didnt get me the boot/recovery dumps til afterwards.
Click to expand...
Click to collapse
thats because nothing was accessible until after root, dumping system was easy, but any other directory/file on the device wasnt able to be read after until being rooted..
samsung didnt even include tar binary so I dumped over adb, then CF helped root and then we dumped raw images!
ricky310711 said:
thats because nothing was accessible until after root, dumping system was easy, but any other directory/file on the device wasnt able to be read after until being rooted..
samsung didnt even include tar binary so I dumped over adb, then CF helped root and then we dumped raw images!
Click to expand...
Click to collapse
yea system can be gotten with adb pull w/o root.
Check hangouts, got 2 imgs for yall to test.
PlayfulGod said:
yea system can be gotten with adb pull w/o root.
Check hangouts, got 2 imgs for yall to test.
Click to expand...
Click to collapse
corect! but some files I was still denied permissikn to pull from /system :/
ricky310711 said:
corect! but some files I was still denied permissikn to pull from /system :/
Click to expand...
Click to collapse
Gah!!! Im drunk ricky
Sent from my SM-G900F using Tapatalk
updated.
LTE devices have a QualcommChip, where everything is stored in the nvRAM, the EFS includes only files that have nothing but absolutely nothing to do with the IMEI.
Gesendet von meinem Nexus 5 mit Tapatalk
I backed up my EFS to internal storage but cant find it don't see no /data/media/SamsungTool/ (using EFS file explorer) just want to save a copy to the PC. What's the exact name of the backed up file so i can use the search feature? cheers.
Offica said:
I backed up my EFS to internal storage but cant find it don't see no /data/media/SamsungTool/ (using EFS file explorer) just want to save a copy to the PC. What's the exact name of the backed up file so i can use the search feature? cheers.
Click to expand...
Click to collapse
Backup to your External SD instead.
/storage/extSdCard/SamsungTool/efs.img
Sent from my SM-G900T
dynospectrum said:
Backup to your External SD instead.
/storage/extSdCard/SamsungTool/efs.img
Sent from my SM-G900T
Click to expand...
Click to collapse
Gotta buy a new sd card, But yeah did a search for efs.img and didn't come up, I'll wait and try when i get my sdcard.
G900s/g900l
Hi will it work on the G900S or G900L?
thehacker911 said:
LTE devices have a QualcommChip, where everything is stored in the nvRAM, the EFS includes only files that have nothing but absolutely nothing to do with the IMEI.
Click to expand...
Click to collapse
@thehacker911
For full backup, which partitions do you recommend?
Galaxy S5 SM-900P Partition table
you can still simply create a copy right?
I have always had rooted phones and my SGS 5 is no exception, it got rooted using CFroot in the carpark immediately on picking it up.
I have therefore always simply made a copy of the efs folder on to the external sd card which is then synced to my dropbox.
However I have not really kept up to date with developments in these areas, so my question is nowadays is this still enough to ensure the safety of my device and it's ability to connect to my carrier. In the past when I have had issues after flashing roms and things simply deleting the /efs folder and copying the contents of my back up into it and rebooting has always been sufficient to get my carrier back up and running is this still the case with the international SGS5 qualcomm variant or do I need to consider other elements?
When will it work for SM-G900V? I just rooted my phone today and would like to use this for my backups. I just tried it by using EFS backup and now it's stuck on a triangle with an exclamation mark that says Please Wait. Ugh! Help...
Related
I have included a script in a initd script segment to create a file called efs.autobackup.img
The forum is filled withon how to creating the .img file but i couldnt find about how to restore.Ktool doesnt work on this.
I am asking this in behalf of a fellow xda member.He got a factory efs files in some old Indian firmware, flashed it by using clear phone efs in odin and now he has some generic IMEI.How to extract the files inside the .img file atleast??
Atleast he can use the files to change his IMEI using nv_data.bin and nv_data.bin.md5
If it's a raw .img (20MB in size) kTool should work fine.
Just rename the file to "efs.img" and put it to /sdcard (root of the internal storage when mounted to the PC).
Then run a restore via kTool (be sure to use latest version).
HellcatDroid said:
If it's a raw .img (20MB in size) kTool should work fine.
Just rename the file to "efs.img" and put it to /sdcard (root of the internal storage when mounted to the PC).
Then run a restore via kTool (be sure to use latest version).
Click to expand...
Click to collapse
Yes its 20MB size!!Ohk hellcat.Am PMing him.he is a new user and he his too terified
Thank god he had flashed my ROM,The wickedrom v1.1 which had auto efs script.
I will ask him to report here.
One thing he has fake IMEI now.This should work right?
Doing a search uncovers a ton of threads/posts about restoring efs
chetan_mohanty said:
I have included a script in a initd script segment to create a file called efs.autobackup.img
The forum is filled withon how to creating the .img file but i couldnt find about how to restore.Ktool doesnt work on this.
I am asking this in behalf of a fellow xda member.He got a factory efs files in some old Indian firmware, flashed it by using clear phone efs in odin and now he has some generic IMEI.How to extract the files inside the .img file atleast??
Atleast he can use the files to change his IMEI using nv_data.bin and nv_data.bin.md5
Click to expand...
Click to collapse
MistahBungle said:
Doing a search uncovers a ton of threads/posts about restoring efs
Click to expand...
Click to collapse
I have been trying to help him with zillions of links from xda.Nothing has worked.I am not a noob man
I do the homework before posting
chetan_mohanty said:
I have been trying to help him with zillions of links from xda.Nothing has worked.I am not a noob man
I do the homework before posting
Click to expand...
Click to collapse
If the .img is OK and not already of a broken EFS, or the image itself is corrupted (all these things can happen, sadly) then it can surely be restored.
HellcatDroid said:
If the .img is OK and not already of a broken EFS, or the image itself is corrupted (all these things can happen, sadly) then it can surely be restored.
Click to expand...
Click to collapse
He is saying that restoring with efs.img makes his phone go to unknown baseband and IMEI.
I have asked him again to post it in this thread
Is there any way to extract that .img file???
chetan_mohanty said:
Is there any way to extract that .img file???
Click to expand...
Click to collapse
In a shell, type:
Code:
su
mkdir /sdcard/mnt
mount -t ext4 /sdcard/efs.img /sdcard/mnt
Then use your fav. filemanager to go to "mnt" on the internal storage.
If the mount command gives you an error, it's likely the .img is corrupted.
is there a methoid of copying files from the root dir without the phone being rooted. this is my second sensation and i really want to do it correctly this time around so i want to backup my efs folder before i root my phone... and even if root my phone im going to need to install a custom rom to get su and i might loose my imei number again and i really dont fancy doing that again
blackcell1 said:
is there a methoid of copying files from the root dir without the phone being rooted. this is my second sensation and i really want to do it correctly this time around so i want to backup my efs folder before i root my phone... and even if root my phone im going to need to install a custom rom to get su and i might loose my imei number again and i really dont fancy doing that again
Click to expand...
Click to collapse
Have u tried copying it with es file explorer, just allow it to go up to root and copy the file.
Sent from my GT-I9000 using XDA
W1nst0n said:
Have u tried copying it with es file explorer, just allow it to go up to root and copy the file.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
yes iv tryed that and it just copys the folder with no content within the folder...
blackcell1 said:
yes iv tryed that and it just copys the folder with no content within the folder...
Click to expand...
Click to collapse
OK, have u tried using abd or adb
Sent from my GT-I9000 using XDA
iv had no joy with trying to use adb with pulling files, it says i have no permission. but iv rooted my phone and iv done a nand backup with 4ext recovery, is there any method of extracting the files i need to back up ? incase i loose my efs files when i flash my first custom rom.
blackcell1 said:
iv had no joy with trying to use adb with pulling files, it says i have no permission. but iv rooted my phone and iv done a nand backup with 4ext recovery, is there any method of extracting the files i need to back up ? incase i loose my efs files when i flash my first custom rom.
Click to expand...
Click to collapse
If you rooted then just give es root acsess, it works for me, what did u root with.
Sent from my GT-I9000 using XDA
This is important I think we should figure out a way asap
Sent from my GT-I9305 using xda app-developers app
install android terminal to your device
and try the command below
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/efs.img
Great I did it now I have efs.img which is 20mb is this my backup ? Jus curios how come with k-tool and i9300 it saves 2 files and much smaller. What's the difference
Sent from my GT-I9305 using xda app-developers app
compression level... if u wan a smaller file , u can download kzn or my rom and u can just backup efs with it without flashing rom..
nah 20 mb is fine thanks dude, I am just wondering why there was 2 files with the K-tool but one with this way
I am out of thanks I have been thanking the I9305 Devs all day, Dont worry another load coming your ways tomo lool
nv_data.bin not in efs folder
Hi guys,
I used Total Commander to copy my /efs directory to a backup folder within the internal sd card, so it is likely that all file permissions are retained in the efs backup. However, I did notice that my /efs directory did not contain nv_data.bin, even though my IMEI is intact. Can anyone also check whether you have nv_data.bin inside your /efs please?
No i dont have that file in that directory......Prodigiez way is excellent a nice neat Img file has been created with all the efs valuable info/data..... My Rom Is now De-Bloated, Zip_aigned/Deodexed, Rooted, Unbranded and Nandroided thanks to all these devs and my motivation
My god what rock have you lot been living under for the last year or so?
Download the POPULAR and VERY WELL KNOWN EFS Pro application from my sig.
Sent from my GT-I9305 using Tapatalk 2
there you have it, I have used your windows tool and it created the exact same EFS.img as does this command line
Code:
su
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/efs.img
But your software way is much easier and even has a way to restore it. thank you very much yeh i must of been living under a rock cause all i ever knew about was K-tool with my previous phone i9300, but K-tool does not work with the I9305
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Thanks ✟
Moving to Q&A
Maybe its just me but I prefer the old style copy and paste method. Using root explorer or similar I simply copy the efs and factory folders and save in multiple places (external sd, PC etc).
Sent from my GT-I9300 using xda premium
sxi200 said:
Maybe its just me but I prefer the old style copy and paste method. Using root explorer or similar I simply copy the efs and factory folders and save in multiple places (external sd, PC etc).
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Not a good idea as you're also losing the permission bits (I take it your external SD is a variety of the FAT file system and your PC NTFS). For example, nv_data.bin has a mode of 0700 and is owned by radio:radio. Say your /efs folder gets wiped and you then copy back your efs folder from your backup. The file (since the umask seems to be 077) will now have the mode as 0600 and be owned by root (because you'd be using Root Explorer/Terminal Emulator to copy back the files which runs as root and not radio). Whatever process (presumably running under the user radio) that looks at that file now may not be able to do so now it's owned by root.
With a tar backup, you're still preserving the permissions which are just as important as the files themselves (though you could look at another GS3 to figure out the correct permissions, granted). With a backup to an image using dd, well, it's the raw partition so I imagine everything on /efs gets backed up.
qwerty12 said:
Not a good idea as you're also losing the permission bits (I take it your external SD is a variety of the FAT file system and your PC NTFS). For example, nv_data.bin has a mode of 0700 and is owned by radio:radio. Say your /efs folder gets wiped and you then copy back your efs folder from your backup. The file (since the umask seems to be 077) will now have the mode as 0600 and be owned by root (because you'd be using Root Explorer/Terminal Emulator to copy back the files which runs as root and not radio). Whatever process (presumably running under the user radio) that looks at that file now may not be able to do so now it's owned by root.
With a tar backup, you're still preserving the permissions which are just as important as the files themselves. With a backup to an image using dd, well, it's the raw partition so I imagine everything on /efs gets backed up.
Click to expand...
Click to collapse
Thanks for that useful post, answered a couple of queries I had :thumbup:
qwerty12 said:
Not a good idea as you're also losing the permission bits (I take it your external SD is a variety of the FAT file system and your PC NTFS). For example, nv_data.bin has a mode of 0700 and is owned by radio:radio. Say your /efs folder gets wiped and you then copy back your efs folder from your backup. The file (since the umask seems to be 077) will now have the mode as 0600 and be owned by root (because you'd be using Root Explorer/Terminal Emulator to copy back the files which runs as root and not radio). Whatever process (presumably running under the user radio) that looks at that file now may not be able to do so now it's owned by root.
With a tar backup, you're still preserving the permissions which are just as important as the files themselves (though you could look at another GS3 to figure out the correct permissions, granted). With a backup to an image using dd, well, it's the raw partition so I imagine everything on /efs gets backed up.
Click to expand...
Click to collapse
I've used the copy / paste method on S1, S2 and S3 and copying the folders / files back manually with root explorer works all the time. Haven't had any issues with permissions.
I test by purposely corrupting my imei (yes I'm crazy) and copying the backup back and all is good. Mind you I also have the auto generated tar backup as well but still prefer the copy / paste method.
Sent from my GT-I9300 using xda premium
Fair enough, I'd just rather restore from a tar backup since I believe there's a reason why nv_data.bin for example is owned by radio, but good to know it works.
Sent from my GT-I9300 using Tapatalk 2
qwerty12 said:
Fair enough, I'd just rather restore from a tar backup since I believe there's a reason why nv_data.bin for example is owned by radio, but good to know it works.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Well I just checked 2 phones:
S1: I have previously restored the efs folder via copy / paste and the current owner is 'system'.
S3: It's my second S3. Unlike my first unit I haven't repasted the efs folder. Owner is 'radio'.
Conclusion is that you are correct about permissions not copying over correctly with the copy / paste method. It's an easy fix via root explorer to change if required, but not ideal especially for noobs.
Fortunately the change in owner didn't cause any issues but still probably best to use the tar method as you suggest just in case.
Thanks for the info.
Sent from my GT-I9300 using xda premium
Read this....very useful
http://forum.xda-developers.com/showthread.php?p=30682712
btemtd said:
This is important I think we should figure out a way asap
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, obviously, you copy the contents of the efs partition
Code:
/efs
and zip it into a tar ball.
Then you put it safely onto your dropbox and voilà.
Hope I could help!
LG familyguy59/Beatsleigher
does nandroid backup saves EFS as well?
in my backup folder I have these two files:
efsbackup.tar.gz
efsdev-mmcblk0p3.img.gz
but I dont remember backing them up
What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
No Luck So Far
Been working for hours trying to figure this one out. Things to note is that now there are two mount points.
1) /mnt/media_rw/sdcard1 / sdcard0 (this has the actual /dev/block/vold/179:1 origin
2) /dev/fuse /storage/sdcard1 / sdcard 0
I've been unsuccessful trying any of the old build.prop tweaks. Hopefully someone smarter will come along and bang this one out.
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
I've asked the compiler of the NeatKernel if he would fork it and swap out the sdcards in fstab.aries, but have yet to receive a reply....
Perhaps if you two went and posted the same, it might motivate him to do so.
Me too
alkspo said:
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You got Company!
vivin007 said:
You got Company!
Click to expand...
Click to collapse
Same here! I upgraded to 4.4 and then realised that the build.prop 's changes made in 4.3 doesn't work for 4.4. Downgrading to 4.3 till there is a solution.
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
alkspo said:
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
Click to expand...
Click to collapse
Good news, so it's not impossible, it's just about time to see the swap method for 4.4 floating around.
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
anatoliy0813 said:
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know it, but DirectoryBind is better m8. Once it moves and link the data to external you can forget about it.
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
bigevil124 said:
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
Click to expand...
Click to collapse
Try file, called "fstab.sun6i" in / folder. I keep trying, but all the changes, I made was unstable...If I'll make some progress I'll write it down
Hi im not sure if this helps but someone released a script for cm11 to swap sdcards. Worked fine on resurection for me all I tested.the thread is somewhere in galaxy2 forum I posted to his thread so one of my last replys. I will find the link and edit
http://forum.xda-developers.com/showthread.php?t=2595756
Sent from my GT-I9100 using XDA Premium HD app
swap internal sd to external
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
rictec said:
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
Click to expand...
Click to collapse
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
tried that but it failed
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
rictec said:
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
Click to expand...
Click to collapse
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
thank you
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
seb_131 said:
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
Click to expand...
Click to collapse
i have those thank you did not wanted to do a entire img just to change some files on boot but it looks like i have to maybe i do some more twicks and be great
Foldermount maybe a good solution
alkspo said:
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
Click to expand...
Click to collapse
Before 4.4 I could do it by "Android Internal to External sdcard" app, but this app couldn't do the trick on 4.4 KitKat OS, so "Foldermount" could be a good solution for you. All this app does is make a image of your apps (that you want to) to sdcard. The real files are located in external sdcard and only the clone file ( of max few KB) will residue at internal sdcard. If you are a gamer, this will help you until the real solution arrives.
Good Luck.
There is real solution! Or at least it works for me.
biopsin said:
Since Android 4.2 and the intro of multiusers there is a problem with bind folders across sdcards, making any attempt on mount bind folders as root would result in visible to root only.
Solution is to fool Android with temporary hijack debuggerd to create the mount binds for us. Thanks Chainfire for this workaround!
* Download both files and rename without .txt
* edit debuggerd.mnt to suit your needs (using any other dir then /emulated/legacy/ will result in read only if browsing folders from sdcard0)
* move debuggerd.mnt to /system/bin
* move mount.sh to any place with execute permissions
* execute mount.sh with any preferred method.
cheers!
Click to expand...
Click to collapse
Quoted from http://forum.xda-developers.com/showthread.php?t=2718760.
Thank You biopsin! Thank You Chainfire!
I'm including my files, but 'mount.sh' was not really changed in practical sense.
In case of 'debugger.mnt' it all depends on Your device. You need to check which block for You is internal and which external storage. Just 'mount' command should help.
You can also use it to mount only one folder - like 'obb', which will let You keep applications data on external card.
Just use "mount -o bind /storage/sdcard1/Android /obb /storage/sdcard0/Android/obb" command in debuggerd.mnt file.
You can also have different 'debuggerd.mnt' files (of course called somehow different - like 'debuggerd02.mnt') and different 'mount.sh' files which will let You mount different things whenever You like.
Enjoy!
-----
And for easier usage You can try $cripter - https://play.google.com/store/apps/details?id=sites.mjwhitta.scripter&hl=en .
It's the best I found.