Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
StarLog said:
Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
Click to expand...
Click to collapse
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
knightnz said:
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
Click to expand...
Click to collapse
Hey thanks, but I did find that, I already know how to backup and restore it.
My question was implied to be a lot more technical, like what byte structure in each file, has what representation.
What part of the bootup process touches or creates the files.
But thanks for sharing.
The file format of files in /efs has not been disclosed. People have tried reverse engineering it with various degree of success.
It does contain IMEI, carrier lock information and other radio related stuff. See unlocking threads here and in Galaxy S forums.
There is also daemon (efsd) which monitors, backups and checksums files in efs.
The radio firmware must have some way of accessing files in efs, but not directly, probably via RIL, since Galaxy S CyanogenMod folks can move it to different file system.
There is probably a lot of useful and interesting stuff stored in these files but messing with them is also dangerous, so backup first.
Thats what I needed to hear, so I must dig more. thanks for the headsup on galaxy s forum
Hi everyone,
Firstly i'm a medium level newbie who can root and change roms on my phone but probably with a level of naivety which would make many people cringe so my understanding of what i am really doing is not great..
I am looking to tidy up my phone and had a quick look in the backup/efs folder out of interest. I seem to have 7 sub folders within it. One is called efs but the others have seemingly random numbers e.g. efs-427 , efs-146 , egs-289.
Can anyone shed any light on this? i have swapped roms countless times and backed up many times as well so i am not sure if these are 'left overs' from that and i can delete some or if this is normal.
Thanks in advance.
Cheers,
iamdes
Might help or not you to figure it out.
That what my /efs had just after stock system (never flashed with custom roms) and just being rooted (for backup sake)
/imei/bt.txt
/imei/mps_code.dat
/nv.log
/nv_data.bin
/nv_data.bin.md5
It seems that i have those files in all of the folders which makes me think I have multiple copies due to changing ROMS / backing up e.t.c.. I was wondering if anyone knows if i which ones i can delete e.g. keep the folder simply titled 'efs' and delete the others or keep the one with 'efs - highest number' and delete the others....
Cheers,
iamdes
qpakao said:
Might help or not you to figure it out.
That what my /efs had just after stock system (never flashed with custom roms) and just being rooted (for backup sake)
/imei/bt.txt
/imei/mps_code.dat
/nv.log
/nv_data.bin
/nv_data.bin.md5
Click to expand...
Click to collapse
thanks a lot
I decided to start this thread as both assistance for some as well as a collaberation on workarounds when you a person flashes a 4.2.2 rom coming from a 4.1.2.
Just like some (maybe most) I flashed CM 10.1 and played around a bit with it and decided it was just not ready to be run as a daily. Being the flashalohic that I am, I made sure I backed up before flashing CM 10.1 so when I went into recovery and went to restore imagine my surprise when it was blank, yep nothing was there. Why did this happen? Well doing some research and reading/searching I found out that the update from Android 4.1.2 to 4.2.2 changes the file structure of the 'virtual' sdcard on our devices. Actually it changes it for every device. What has changed is that the ability to add user accounts, similar to any regular computer, has been implemented. However, if the proper steps are not taken before you flash a new 4.2.2 Rom, you will end up with a huge mess and run out of room on your device in a hurry.
The actual location when viewed with a root file manager has been here on 4.1.2:
/data/media
And though you will see the same files in /sdcard and /storage/sdcard0, those are just symlinks to the same info, just like a shortcut (on a windows box) or alias (on a mac box). Once you flash a 4.2.2 ROM, the actual location gets changed (and all the files moved) to here:
/data/media/0
And the symlinks get changed to /sdcard/0 and /storage/sdcard0/0. On the surface, no big deal, right? Wrong. The problems arise if the version of your custom recovery is not compatible with a 4.2.2 ROM. If it is not and you keep flashing 4.2.2 ROMs you might soon end up in trouble. If, while using the 'older' custom recovery, you continue flashing, your sdcard ends up somewhere around here:
/data/media/0/0/0/0/0/0 (etc.) with all your files copied to every '0' directory and your symlinks end up the same way, and your device quickly runs out of space (the dreaded "your device is low on storage" message).
This may also make it very difficult to restore your nandroid of a 4.1.2 ROM as well. If you are already in that situation, not to worry, the solution for that is later in this post.
So far I have only been able to to copy all the files found in the last /data/media/0/0/0/0 (?) folder to my computer. Then using a file manager that will show hidden files and folders, copy/move the files in the last '0' directory to:
/data/media/0
And then use file explorer to delete all the other '0' directories until I have just this one:
/data/media/0
leaving nothing else in the symlinks but /sdcard/0 and /storage/sdcard0/0. This techniques is if you end up with a huge file structure.
****BACK UP YOUR SD CARD FIRST!!!!! before deleting any 0 folders!!!****
NOTE: A reboot of your device is essential at this point.
If after flashing a 4.2.2 ROM you decide you don't like it and want to restore your nandroid to your saved 4.1.2 ROM, how does that work out?
1.) Get yourself a (good) root file browser.
2.) Brows to /data/media/0
note: this is where android (and almost everything else that uses a Linux kernel) mounts anything that is considered "external" storage.
3.) Do all of your file fixing from here. It will make changes universally.
4.) select all within /data/media/0 and then paste everything back into /data/media selecting merge and/or overwrite. Once done, just delete the /data/media/0 folder, reboot your phone and Profit.
This is a pain and I agree but at this point is the only way I know how to get around this. If anyone knows other ways please share.
* While writting this I came across this info from user elfaure. I havent tried this yet as I am at work and get crappy signal but please post results if you try and if it works, please thank him! *
elfaure: Ok folks for next guy who decides to upgrade to 4.2 but does NOT want the multi-user environment, give this a try.
1. Download the attached file
2. Remove the .txt extension
3. Copy it to your /data directory
4. Open Android Terminal Emulator (Free Market app if you don't already have it)
5. At the prompt type "cd /data"
6. Type "chmod 644 .layout_version" on the file in /data (/data/.layout_version)
Code:
cd /data
chmod 644 .layout_versionNow when you upgrade to 4.2 you should stay single user and have no /data/media/0 directory when you are done. If anyone tries this please let me know if it works and thank me if it does.
ps-its just a special file in a special location, the presence of which tells Android NOT to upgrade your system to a multi-user environment. If you later decide you want multi-users, delete the file and reflash (from recovery) the stock or custom firmware or ROM or recovery. If your custom ROM or recovery wipes the entire /data partition less /data/media including this file, obviously then this will not help, but with latest versions of ROMs and recoveries that should not happen any more.
http://forum.xda-developers.com/showthread.php?p=40911246#post40911246
It also looks as if he may be working on a script to help as well and I will keep track and update as needed.
So far this is what I have come up with and I hope it helps some and I hope others that are smarter than I can correct me if I am wrong on any of the above or other add information on other ways to correct this.
I think this is part of my issue but I don't have any 0 folder under data?
I too flashed the 4.2.2 ROM, and noticed that every everything on my sd card had somehow moved to my internal memory? When I went to reflash the ROM it failed. It I also tried to reflash the ROM I was originally running and it too failed. Luckily I was able to do a nandroid restore so the phone is "usable" but TWRP 2.5 still does not see my my external sd and that seems to be that make reason I can not do anything within in the recovery.
Any suggestions?
The op is telling you exactly how to fix it.
lizardking7112 said:
I think this is part of my issue but I don't have any 0 folder under data?
I too flashed the 4.2.2 ROM, and noticed that every everything on my sd card had somehow moved to my internal memory? When I went to reflash the ROM it failed. It I also tried to reflash the ROM I was originally running and it too failed. Luckily I was able to do a nandroid restore so the phone is "usable" but TWRP 2.5 still does not see my my external sd and that seems to be that make reason I can not do anything within in the recovery.
Any suggestions?
Click to expand...
Click to collapse
Let my clarify:
I have used two different file managers and even used to terminal emulator using ls -la to make sure i have no hidden files
sdcard0/data/ there is no media directory
Maybe this isn't my problem, since I don't see any file/dir with a 0, but all this mess started when I loaded up a 4.2.2 ROM?
Everyone should check this out to aid you in your flashing addiction.
Happy flashing!
http://forum.xda-developers.com/showthread.php?p=42237249
Sent from my HTCONE using Tapatalk 2
I flashing an aosp Rom and nothing in my sd card changed. Maybe I'm lucky?
Sent from my HTCONE using Tapatalk 4 Beta
Good information
so does this work? will i be able to nad back to sense and all my files are in the right place?
I couldn't get it to work, the attachment. However the new recovery I linked to looks to have promise but I haven't tested it yet cause I'm remote right now and need my phone at the moment. Will give it a go this weekend.
Sent from my HTCONE using Tapatalk 2
Seems @imneveral0ne has found a way to assist folks that like to go between 4.2.2 and 4.1.2
Check out his thread here.
http://forum.xda-developers.com/showthread.php?p=42512892
Sent from my HTCONE using Tapatalk 2
Weighing in, worked like a charm for the most part. TWRP recreated another TWRP folder inside its original TWRP folder (it has to be left at /data/media/0/TWRP for you to be able to reinstall a nandroid backup) [also forgoing obvious yo dawg joke here], but besides that my phone is back to being right as rain.
Nice write up on this issue. Thanks
sent via my tranquil⊙NE
I'm sure it wouldn't work for doing a nandroid restore, but on my Galaxy Nexus I would just make certain I had the latest version of TWRP, boot into recovery, format the SD card, and then push the rom files to /data/media/ and flash. That is my only complaint about this change, really...truly "clean" installations are inherently more risky or difficult, dependent on your knowledge level.
It won't let me delete folder 0 no matter what. Inside that folder is a ViperRom folder that won't delete as well no matter what I do!
Thanks for this info. I think I'm going to take the plunge this weekend so this will be very helpful info.
Sent from my HTC ONE using xda app-developers app
I think it moved my ROM data into the 0 folder, how do I get it out? Everything else from the 0 folder is deleted except for ViperROM's folder, and whenever I try to move or delete it, it just fails the operation. I already have a copy out of the 0 folder, but I still want it out, because otherwise I can't flash things, since it just shows the the almost* empty sdcard/0 folder. Help? Should I just put my mods in the 0 folder and deal with it?
Bseagull said:
I think it moved my ROM data into the 0 folder, how do I get it out? Everything else from the 0 folder is deleted except for ViperROM's folder, and whenever I try to move or delete it, it just fails the operation. I already have a copy out of the 0 folder, but I still want it out, because otherwise I can't flash things, since it just shows the the almost* empty sdcard/0 folder. Help? Should I just put my mods in the 0 folder and deal with it?
Click to expand...
Click to collapse
No. There is a script out there you can flash that will help. Check out post # 10.
Sent from my One using Tapatalk 4
So can we delete the legacy file now? I haven't done anything with my internal storage since coming from 4.1.2 for the first time. It looks like twrp 2.6.3 copied all my files correctly to the 0 file but all the files are still also in "legacy" folder. Is it duplicate that I can delete from legacy or are they just symlinked? I am never going back now that we have official 4.3 release.
ivwonka said:
So can we delete the legacy file now? I haven't done anything with my internal storage since coming from 4.1.2 for the first time. It looks like twrp 2.6.3 copied all my files correctly to the 0 file but all the files are still also in "legacy" folder. Is it duplicate that I can delete from legacy or are they just symlinked? I am never going back now that we have official 4.3 release.
Click to expand...
Click to collapse
I am not certain to be honest. It looks like the file structure didn’t change with the release of 4.3 so it’s possible that they are symlinked. If all your files are moved to the /0/ folder and you have nothing in the legacy folder it would make sense that you would be able to but I have yet to test this.
I suppose this weekend I could back up the phone and file tree and give it a shot
Thanks for the response. I haven't tested out yet either but will post back if I do.
Had some free time recently so finally got round to opening my OYUA and having a looksy.
ROMCleaner 3.5 works splendid with CWM and OUYA.
Why use it with the OUYA?
Its a fast and easy way to pre-install all your apps and games through a single zip flash in CWM.
No more sideloading Dropbox to download and install everytime you flash a new StockPlus or OTA, have them all ready and waiting for you upon the first boot of the ROM.
If your familiar with ROMCleaner on one of the many devices we ported it to, you'll feel right at home!
As certain design decisions were overlooked with the OUYA and it didt get the following it was expected, I didnt wont make a big deal aout the release but couldnt help playing about with to see what I could get working on it. It worked fine so here we are
Notes
More detaililed guides and instructions can be found in any of the device specific threads for ROMCleaner if you want to have a look at its features but for now Ill leave this little guide for us OUYA users.
I doubt there will be a Aroma version due to its reliance on touch input but will slowly be looking at going through the other individual tools we created before Patrics83 put the Aroma AIO toolkit together.
It starts at v3.5 as this was the last version before moving to Aroma and we kept that consistent across devices.
Any changes will only be visually to the updater-script and the default romcleaner.txt included in the zip as at its core, RC works. I will keep a dated chagelog for you though for any updates to the zip.
Basic Guide
Pre-Requisetes:ClockworkMod Recovery
On your on the root of /sdcard create a (case sensitive) folder structure as so:
Code:
/sdcard/ROMCleaner/FirstBoot/data/app/
/sdcard/ROMCleaner/FirstBoot/system/app/
Place any apks in these folders which you want installed after flashing in the relevent folders
After flashing the ROM, flash ROMCleaner 3.5.zip
Reboot as normal
First boot of the ROM will take extra time due to the apks being sorted by Android when its up and running you will find all the apps in the usual place all ready and waiting!
If you install another launcher I recommend loading OUYA Launcher first and following the setup (wifi, username etc) to get it all sorted before using your preferred launcher.
You can use RC to install other files such as bootanimation.zip (system/media/) as well and are not limited to just apks. I add TwitcyEye's KeyMap mod for example so the mapping is done with no copying files about.
It will set the correct permissions for all the files and folders so dont worry about that.
Cleaning
ROMCleaner has the ability to remove files from the system after the ROM has been flashed, but before first boot, using a text file in a simple user-friendly format.
The default list has not been optimized for OUYA and I have not got round to checking through it yet. I haven't noticed any thing important if it does but you have been warned Ill take a proper look when I get the time.
You have the ability to define a custom list for RC to use by creating a ROMCleaner_user.txt file in /sdcard/ROMCleaner/ and Ive attached a blank one with some detailed instructions on its layour and format. I recommend you use this file until I have time to cross reference the default list with the OUYA files to avoid anything being deleted.
All in all its an easy way to get your apps installed when flashing a ROM be it StockPlus or an official OTA. It requires no special access as its all done in recovery and uses its own busybox.
Anyway, Have a play and let me know how it works for you.
Like a lot of people on XDA I have very little free time these days due to my job and so-called life but will be keeping my eye on this thread and the OUYA in general
#probably for formatted guide
#just in case
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
TadeoNYC said:
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately thats a completely different thing. All this is done in recovery where as TB etc are app specific done while the OS is up and running.
RC installs (and can remove) the apps before the OS has loaded for the first time.
Hi everybody,
hopefully someone here can answer a few questions for me.
I have a Samsung Galaxy 3 mini.
android version 4.4.2
kernel version 3.4.0-1670137
baseband version g730aucubng4
my service provider is AT&T
what I want to do is pretty simple, or so I thought.
I read this article ( https://www.androidpit.com/galaxy-s3-note2-memory-bump) about swapping your phone's internal and external storage so the thing doesn't get so full of apps etc. it runs like crap.
I thought "hey, I haven't rooted my phone yet for fear of loosing stuff, but it's old and slow and if it's that easy, why not"
I rooted it using kingo-root, but decided to use o-nandroid backup to create a backup before I did anything. I fallowed these instructions (http://forum.xda-developers.com/showthread.php?t=1620255/) but during the process of flashing the zip file I got a failure message and managed to wipe my memory loosing everything that wasn't on the external sd card.
anyway, to make a long story short, after 4 days of messing with different apps and trying, unsuccessfully, to do various tasks (mainly dealing with creating backups. using twrp, cwm, titanium backup) I think I've discovered the problem.
contrary to what I had read, my android device's boot-loader was not unlocked, or in fact unlockable.
I finally managed to create a backup using Safestrap. but now to my question.
with my bootloader locked, and working through Safestrap, is it possible to use something like the 11extsd2internalsd file from that first article to swap my two hard drives? or am I stuck, since I can't install new kirnels?
--now, someone is bound to say "hey, you should have searched xyz, there is a thread there about this exact thing". I thought I'd respond to that now and save them the trouble. I have spent the past 5 hours searching, googleing, and reading articles about this. so far, I have learned a lot, but I'm tired and quite frustrated with the whole endeavor.
so I thought I would try asking the experts if it's even possible to do what I originally wanted to do, or if I should just delete all these apps, unroot my phone and go back to deleting my pictures and text messages every other day to save space.
Thanks for having the patiance to read through my tale of woes, hopefully someone will be able to help me out and answer my question.
JM
You can swap internal storage with external SD by editing fstab.<device_name>.
Look, here is this file for my phone (yours will be little different) https://github.com/TeamCanjica/andr...dina/blob/cm-11.0/rootdir/fstab.samsungcodina
Just swap in places this code "voldmanaged=sdcard0"/"voldmanaged=sdcard1"
This file you can edit only after unpacking and repacking boot.img (you need to get ramdisk filesystem, more info and how to http://forum.xda-developers.com/showthread.php?t=2036528).
For flashing boot.img (kernel) after making changes, your device must be rooted (minimum this) or have custom recovery which will let you flash zip package.
As I know, last step is to edit from /system/etc/permissions/platform.xml one line (more info http://trendblog.net/fix-kitkat-sd-card-write-restriction/ )