Develop Bugs

Cannot Mount System as r/w

I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.

Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?

your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom

try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.

if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.

mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...

after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse

mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!

I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.

It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...

sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.

cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?

yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this

fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?

its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS

Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.

I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app

I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD

[Help] Problem Rooting using the No-PC Method

Hey Guys,
Before I ramble on about my problems, I would like to thank all the amazing devs that work night an day to make our phones awesome. I have been reading these forums for a couple of weeks and have seen how helpful everyone in these forums are to us noobs.
I'm not new to Rooting (Rooted my G1 a while back and Jailbroke a 1st Gen iPhone way way back lol), but this is my first time Rooting my 3G Slide, which I have had since they were first launched.
I am attempting the No-PC Method described here: http://forum.xda-developers.com/showthread.php?t=896148
I have been trying since last night with no success. I have followed the process step by step, to the T, and continue to encounter the same error every time I try.
I succesfully flash the ESPRIMG.zip and then go to Recovery to apply the "update.zip" file so I can go into Clockwork Recovery, however instead of going into Clockwork Recovery it just gives me the following error:
E:failed to verify whole-file signature
I have searched the forums and none of the responses and solutions have been helpful as almost all of them are users who have already flashed a ROM on their phones as opposed to the Stock one, and a lot of them seem to be prior to this new AndRoot method.
Also, I am using this method as I do not have a USB cable for my phone or a PC for that matter, and havent really researched any Mac mathods of Flashing a Custom ROM to the phone.
Any help would be mucho appreciated!

i think you have to have the update.zip file in the root of your sd card

I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/

yixmal said:
I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/
Click to expand...
Click to collapse
yeah, that's not good if that's all you have there. i was working with someone over at the tmobile forums who was getting the same error (http://forums.t-mobile.com/t5/myTouch-3G-Slide/Easy-root-unroot-Froyo-for-all/td-p/649239/page/6) and it turned out they had the downloaded files in a different folder, and moving them to the root made it work... you may want to try using the files you need from this link instead: http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html

I'm a newbie to the whole programming side of computers, familar with using one though. I am going through the steps of the no pc rooting, and I read through step 6 and I thought it was confusing it says...
Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device multi-select copy then rm r/w in program in upper left on data local folder. I am confused with the rm r/w section there, I haven't gone through the steps, just want to have a general idea before I get in there and screw something up.

Yeah, that ones a lil tricky apparently. Root explorer can be found in the market for ~$4, but if you click the link for the tmobile forum, we found that another app (free) works just as good.

I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Anyways, mine's working now.
As for the step 6 on the instructions. It basically means that after you paste the files you need to go back to the android system (the folder where you can see everything thats on the android) and at the very top of the window you will see a button that says "R/W" next to something like "Mount as R/O". You just need to hit that button so you can write to the folders, then go back to /data/local and long press "Image_flasher" click on permissions and make sure everything is checked, then repeat on "mtd0.img" file.
I know its a long explanation for such a small step but I try to be as detailed as i can. Hope it helped.

Get
update.zip
Put iton ur SD card
and a ROM.zip that you like n the SD card as well..
see if that works

yixmal said:
I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Click to expand...
Click to collapse
^ This
I just went through the same thing - I had restored my phone back to stock and then went to re-root it. I have 2 copies of ESPRIMG, file sizes as follows:
The one that was giving me problems: 145,045,641 bytes
The one that ended up working: 143,701,302 bytes
Once I used the slightly smaller ESPRIMG the process worked perfectly. When using the other one I was getting the same error as the OP.

So confused with storage/backups

Please help me out here.
I can never find backups.
I recently realized the theres a "0" folder in every single "0" folder
And each one goes back in time a little, Which is where all of my older backups we're.
But when I make one now!
There's no backup folder.
Or anything within the TWRP folder but a weird file named TWRPS.something or something.
I deleted the 0 folder and it hasn't came back... I kinda figured it would.
I need a make a backup!!!!!
I've spent hours and hours and hours and hours setting up Paranoid Android.
YOU ALL KNOW how many per app color possibilities there are and how long it takes to make every single thing match.

Can someone please explain how the phone handles and places backups and why I can't seem to make one currently...

1. Use CWM, a lot easier IMO
2. Make sure you're using the LATEST version (6.0.2.3)
3. In 4.2.x, Google introduced the multi-user feature to Android (mainly for tablets). The first user is '0', second is '1', etc. As phones only use one user all data is moved to '0'. However, CWM still stores backups in the root (like it did in 4.1.x) so they are only visible in CWM UNLESS you use a root explorer (e.g. ES) to view the root directory and then you can find them in /data/media/clockworkmod. From there, you can delete/move them onto your '0' folder and then copy them to your PC to save space

EddyOS said:
1. Use CWM, a lot easier IMO
2. Make sure you're using the LATEST version (6.0.2.3)
3. In 4.2.x, Google introduced the multi-user feature to Android (mainly for tablets). The first user is '0', second is '1', etc. As phones only use one user all data is moved to '0'. However, CWM still stores backups in the root (like it did in 4.1.x) so they are only visible in CWM UNLESS you use a root explorer (e.g. ES) to view the root directory and then you can find them in /data/media/clockworkmod. From there, you can delete/move them onto your '0' folder and then copy them to your PC to save space
Click to expand...
Click to collapse
Thank you, I guess I will switch to CWM I flashed it on a friends phone last night and it's a lot better than it was
2 years ago or so lol.

As long as your on the most current version of CWM or TWRP (loads better IMO) it fixed the nesting issues...
Sent from my Galaxy Nexus using Tapatalk 2

0dBu said:
As long as your on the most current version of CWM or TWRP (loads better IMO) it fixed the nesting issues...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure what you mean by nesting but I have TWRP and evrytime I make a backup now it's not in the TWRP folder.

Nesting is the creation of 0 folders ie /0/0/0/0/0 etc. Updated recoveries prevent this so your backups will be in /0/twrp/ and not /0/0/twrp after flashing new rom
Bloods thicker than water

namtombout said:
Nesting is the creation of 0 folders ie /0/0/0/0/0 etc. Updated recoveries prevent this so your backups will be in /0/twrp/ and not /0/0/twrp after flashing new rom
Bloods thicker than water
Click to expand...
Click to collapse
Okay That makes sense, I switched over to CWM and I'm on the newest version.
I read someone that backups are no longer accessable from other apps or a PC, So I can't drag em' to my laptop for safe keepings.
I see it on my phone... But once I plug up to the laptop I can't find anything.
Edit: never mind I looked up a little and saw the very detailed post by the Recognized Contributor.

Okay so I'm using the newest CWM, Along with the newest ROM manager.
apparently the only way to get my backups to my pc is to ADB pull them (not too educated in which)
Or use this backup download server which is SLOW!!!!!!!!!!!
It's still trying to recognize it, Hasn't even started downloading yet.
Anyone know a better way?
Usually I'm not so bent on having a backup on my pc but that's when I actually had a SD card.
Now that it's internal I don't trust it one bit, Google made the storage a damn maze with this 0 folder and the legacy folder and all that crap.

[Q] Getting Gapps on [JUNE 17][4.2.2] PARANOIDANDROID v3.60 | HALO

A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.

lovingboth said:
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
Click to expand...
Click to collapse
Repartition your sd-card by using the partitioning guide in my sig.

onknope what
abaaaabbbb63 said:
Repartition your sd-card by using the partitioning guide in my sig.
Click to expand...
Click to collapse
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.

lovingboth said:
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
Click to expand...
Click to collapse
Theres no need for a swap partition. If you are using PA it will just act as a waste of space, since the rom doesnt utilize it in any way.
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.

chromium96 said:
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
Click to expand...
Click to collapse
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)

lovingboth said:
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
Click to expand...
Click to collapse
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.

chromium96 said:
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
Click to expand...
Click to collapse
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'

lovingboth said:
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
Click to expand...
Click to collapse
Go to system/app. Are the google apps installed? What permissions do they have?

abaaaabbbb63 said:
Go to system/app. Are the google apps installed? What permissions do they have?
Click to expand...
Click to collapse
Ah, no they're not.
About sixty are, owned by root, with rw (owner) and r (group and global) permissions.
I am being tempted to bite the bullet, install the ADK on something and try the adb method.

What about /sd-ext/gapps/system/app. Anything there?

chromium96 said:
What about /sd-ext/gapps/system/app. Anything there?
Click to expand...
Click to collapse
Yep, they are there, with what I presume are the right permissions: as above, owned by root, rw-r-r.

Doing some more nosing around, and looking at the alternative installation instructions on woh-roms.weebly.com/gapps.html
$ adb shell ls /sd-ext/gapps/system
app etc framework lib usr
Click to expand...
Click to collapse
Yes, doing
ls /sd-ext/gapps/system
produces that.
# enable extgapps (quotes needed)
$ adb shell "echo x > /sd-ext/gapps/.extgapps"
# gapps dir should look like this (if .extgapps doesnt exist the init script wont run)
$ adb shell ls -a /sd-ext/gapps/
.extgapps system
Click to expand...
Click to collapse
Yes, doing
ls -a /sd-ext/gapps/
produces that.
.extgapps is a zero byte file, rather than one byte containing 'x' as there, but the root explorer instructions would produce a zero byte file, so presumably a) there's no touch command and b) it's the presence of the file that's important, not what it contains.
BUT...

... if I do
logcat -C
(after doing logcat -c, going oops, rebooting, and getting it right )
then the lines that are supposed to be there aren't.
I'll get the email working, email the output to myself and stick it in a pastebin or similar.

pastebin.com/Qtrps3A8 has the whole thing.
At the start, various links are possibly not set up:
I/run-parts( 75): ln: /system/etc/permissions/com.google.android.maps.xml: Out of memory
I/extgapps( 155): Created /system/etc/permissions/com.google.android.maps.xml
Click to expand...
Click to collapse
is just one example, then later
D/AlarmScheduler( 1300): No events found starting within 1 week.
I/Goo Parser( 839): GAPPS: No file, skipping item 0
I/Goo Parser( 839): GAPPS URL: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130702-signed.zip
I/AlarmReceiver( 839): gooVer: 3601
Click to expand...
Click to collapse
.. so what file is it looking for, and is this down to trying to do things with the card before it is ready?

What has changed:
The search 'app' has gone from the list - I can see from the logs that it is supposed to be replaced, but here it's just missing.
The browser is now very like Chrome... and I don't remember that being the case.

[Q] [HELP!!!] Finding EFS backup that works with SGH-i317

Hey everyone!
I have a AT&T Samsung Galaxy Note II SGH-i317 build UCAMC3 rooted supersu running stock 4.1.2 and stock recovery. Basically all I've done is root it (using odin and an autoroot .zip from a guide I found) and everything works fine and no problems and imei is there and modems all working etc.
I've been trying to back up my efs file before flashing CWM and XenonHD11.1. I've tried TONS of methods and I haven't been able to get any of them to work. Methods include efs pro v1.9 and v2.0, using terminal emulator, and two or three different tool kits. Oh and I think one used odin if I remember right (maybe not, not important I guess). I've also looked for an app but haven't found one that supports my model. Anyone have a solution or suggestion?
More info:
I'm also having other issues that could very well be effecting my being able to use efs pro and tool kits to backup efs:: My Windows XP SP3 won't install drivers for my phone: Drivers downloads> drivers installs> phone connects (tried usb debug mode and normal)> driver install error "The required section was not found in INF". So EFS Pro (both versions) don't detect phone at all. Odin does detect it fine (weird). Toolkits don't detect phone at all.
Terminal Emulator doesn't find any files or directories that any guide that I've found says to use (weird?).

If rooted...
Use a root capable file explorer application. ..(root explorer app works great)...
Once inside the application. ..grant it root access. ..
Then enable R/W Access in the application setting at the top of the screen. ..
Then navigate to your EFS folder. ..
Long press the folder. ..and select "copy" from the drop down menu...
Then navigate to your SD card...
Hit the menu selection button at the top of the screen. ...and select "paste"...
Allow the file to copy. .then verify you have created a successful copy by backing out of the application and opening it again. ...and navigating to the SD card...
You should see the copy. ..
Warning. ..
Root access applications can be dangerous if you are unfamiliar with the layout or the ramifications of playing inside of protected system files. ..
Practice on a non critical file like a picture or music file first...before moving or copying anything critical. ..
Enjoy. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

Thank you! And thank you for the warning advice too! Great idea to practice! I haven't tried it yet but I'm going to soon when I get a chance. I ended up reading and finding out that doing a nandroid backup also backs up efs along with everything else and that cwm and twrp's backup makes a nandroid backup. So I chanced it and flashed cwm via Odin and everything was fine and I did a couple backups of stock rom and build and kernel and all and then flashed XenonHD with halo and I LOVE it! Thank you again!
Sent from my SAMSUNG-SGH-I317 running XenonHD 11.1 with Halo using xda app-developers app

sgh-i317 EFS seems like its gone
would it be posible to get a copy of the efs files.
out of nowhere it seems like the efs file just went missing. ive finally got to were i can look thru system files but its no wear to be found,
there not much i can do at this point that i know of, it seems like the efs files that are missing are keeping it from booting up. right now the only thing it will do is hang at the att logo, im on the mk6 with the knox counter. .but i cant figure out what els to do...
any advice would gratefully be appreciated and would be my hero.