Related
Isn't root explorer just like every other file explorer? Why do more people use it and is always on tutorials?
if you need to edit system files with root aceess .. mount system as r/w , remove bloats ..in short advanced tasks .....you need it ...
if you haven't even rooted or don't want to touch system leave it
Because its fast, clean and you can use ROOT
Sent from my Galaxy ace using XDA App
1.) Inbuilt unzip
2.) Inbuilt unrar
3.) Inbuilt text editor (useful for modifying values of config files e.g. build.prop
4.) Full access /root
happily1986 said:
1.) Inbuilt unzip
2.) Inbuilt unrar
3.) Inbuilt text editor (useful for modifying values of config files e.g. build.prop
4.) Full access /root
Click to expand...
Click to collapse
= some advance tasks which only users that know what they are doing should do
as i have seen many dudes deleting system apps after which cry on xda
So I'm guessing its worth the money then. And as far as I've searched, there isn't a free version
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
I have no idea what you mean.
robinandroid said:
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
Click to expand...
Click to collapse
Sent from my Samsung Galaxy Ace using XDA App
robinandroid said:
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
Click to expand...
Click to collapse
yes you can. just a matter of a build.prop edit at the right parameter.
Because with default File Explorer you cannot Search, Copy, Paste ... etc
Root explorer use root permisions, it's the best, i use it and i'm verry happy with it !
R/W
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
BNAS said:
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
Click to expand...
Click to collapse
dude you seriously need to reconsider
your SD-CARD IS R/W ALWAYS
why you need root explorer to do that ??
BNAS said:
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
Click to expand...
Click to collapse
just restart the phone ......
madman_amit said:
dude you seriously need to reconsider
your SD-CARD IS R/W ALWAYS
why you need root explorer to do that ??
Click to expand...
Click to collapse
Dude.. To eliminate system apps you need root explorer. Default is R/O not R/W.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
prateek_gemini said:
just restart the phone ......
Click to expand...
Click to collapse
Restarted... Wiped cache, wiped davik cache, still no go. Used Nandroid to restore to a prior ROM I was using (Cog x2). Now it works. Found out that write protection on the SD partition was set to S-ON. Had to restore to a different ROM to get it back online. Super user was not granting permission to Root Explorer with Stock deodexed rooted ROM. Strange. Anyway, maybe someone else will come across this same issue and know that it is ROM related to write only partitions.
Thanks!
BNAS said:
Dude.. To eliminate system apps you need root explorer. Default is R/O not R/W.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
Restarted... Wiped cache, wiped davik cache, still no go. Used Nandroid to restore to a prior ROM I was using (Cog x2). Now it works. Found out that write protection on the SD partition was set to S-ON. Had to restore to a different ROM to get it back online. Super user was not granting permission to Root Explorer with Stock deodexed rooted ROM. Strange. Anyway, maybe someone else will come across this same issue and know that it is ROM related to write only partitions.
Thanks!
Click to expand...
Click to collapse
Hello. You want to mount r/w on your SD CARD. Madman is right. It's always r/w on the card.
System and card is different.
Sent from my GT-S5830 using Tapatalk
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
ok my esf folder is empty and now my s4 is stuck in factory mode. me being me they never got backed up and now i have no clue what to do. i have tried to unroot and go to stock with odin3 and no luck then rerooted. is there any way to fix this? would upgrading to ME7 fix this? i would rather not go to ME7 but if i have to i will. i just want my phone to get out of factory mode. :crying:
I could tell u also me7 wouldn't fix it...
hyperdrive powered s4
---------- Post added at 04:21 PM ---------- Previous post was at 04:19 PM ----------
Can someone please help him to repopulate his efs without a back up... I've seen it has been done i really can't tell him how do so
hyperdrive powered s4
---------- Post added at 04:31 PM ---------- Previous post was at 04:21 PM ----------
If I gave him an efs backup of mine and just filled in his imei number would this potentially work?
hyperdrive powered s4
---------- Post added at 04:48 PM ---------- Previous post was at 04:31 PM ----------
Okay scratch that idea, u need to Odin to stock and sent for repair to Samsung or get a warranty replacement sorry man...hopefully you can send Sammy a note saying not to take the upgrade while they have it for repair
hyperdrive powered s4
Do you not have a back up of your efs folder? Did you try copying the efs folder to your pc using dd if=/of= to see if anything is there? Did you enable the hidden menu and enter the code related to your efs?
Sent from my TouchPad using xda app-developers app
Surge1223 said:
Do you not have a back up of your efs folder? Did you try copying the efs folder to your pc using dd if=/of= to see if anything is there? Did you enable the hidden menu and enter the code related to your efs?
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
He didn't have a backup
hyperdrive powered s4
Basiclly if i run a TouchWiz rom my esf if missing and it puts my phone in factory mod, but if i have something like cyanogenmod it is fine. I have been running cyanogenmod since the begging of september. Than decide i wanted to try hyperdrive and and found out my esf folder is all messed up now
I have never backed up the efs folder before but after reading this thread I made a copy and saved it to my external sd card. I hope I never need it. Good luck to the OP!
So are u sayin if u put cm back it fixes your efs folder if so, your efs folder is being put in a different spot and the touchwiz rom cant find it
Sent From My Hyperdriven S4
ebsk8er06 said:
So are u sayin if u put cm back it fixes your efs folder if so, your efs folder is being put in a different spot and the touchwiz rom cant find it
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
ok if i flash a touch wiz ROM its gets stuck in factory mode because my phone esf folder is missing every all the files, but if i flash CM it is works fine. so either CM does not need those files or it moved them somewhere else. So im going to try a TW ROM and with root explorer to try and search for factory mode and see what comes up. worst thing that can happen is it does not work and i will re flash to stock and un root and take my phone to Verizon.
Stop. The first thing you should do is dd these to your sdcard/pc
efs -> /dev/block/mmcblk0p10
modemst1 -> /dev/block/mmcblk0p11
modemst2 -> /dev/block/mmcblk0p12
m9kefs1 -> /dev/block/mmcblk0p13
m9kefs2 -> /dev/block/mmcblk0p14
m9kefs3 -> /dev/block/mmcblk0p15
Sent from my TouchPad using xda app-developers app
If cm is working an u have service and data it has moved the files I've read a thread somewhere telling how to get it back to the right location but I can't seem to find it right now
hyperdrive powered s4
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and may the force be with you!
Leahcim
This was on sammobile.com I don't know if it will work on the s4 but maybe worth a try
hyperdrive powered s4
ebsk8er06 said:
If cm is working an u have service and data it has moved the files I've read a thread somewhere telling how to get it back to the right location but I can't seem to find it right now
hyperdrive powered s4
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Good luck and may the force be with you!
Leahcim
This was on sammobile.com I don't know if it will work on the s4 but maybe worth a try
hyperdrive powered s4
Click to expand...
Click to collapse
well the thing is the IMEI number is the correct one and i am connected and have service it's just that my phone is stuck in factorymode anyways i backed up the EFS folder and deleted it and it was regenerated but was still empty. if anything im going just unroot and take it to Verizon
Well just delete the factory mode apk
hyperdrive powered s4
ebsk8er06 said:
Well just delete the factory mode apk
hyperdrive powered s4
Click to expand...
Click to collapse
I know i could do that and i wanted to try to fix it but after all i have tried i give up lol. the only bad thing is there is no lock screen , but i will get over it
OK it looks like I goofed and didn't backup the right messaging app in titanium...
However, before I decided to install a my new ROM I took a image backup in CWM and I'm guessing the messages got backed up too. I would reload the backed up image that CWM did but I'm getting this pesky MD5 mismatch nonsense.
So rather than faff with that, is there a way I can extract the messages / sms history from the image and restore it whilst in my new ROM environment?
Thanks...!
invertgoat said:
OK it looks like I goofed and didn't backup the right messaging app in titanium...
However, before I decided to install a my new ROM I took a image backup in CWM and I'm guessing the messages got backed up too. I would reload the backed up image that CWM did but I'm getting this pesky MD5 mismatch nonsense.
So rather than faff with that, is there a way I can extract the messages / sms history from the image and restore it whilst in my new ROM environment?
Thanks...!
Click to expand...
Click to collapse
you can use root explorer to extract the tar file for the /data backup. should be on your sdcard under the clockworkmod folder.
then you can use root explorer or an sqlite reader and navigate to /data/data in your extracted folder, and find the messaging app folder. then use the sqlite reader to read one of the .db files. sooner or later one of those .db files will have you messages in it. I dont think you can restore this(you can try to copy the .db and put it in the /data/data for your current messaging app) but you can at least read it.
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
if it extracts to an img you will have to
Code:
mkdir datafolder
busybox -o loop data.img datafolder
then navigate through that datafolder with the instructions above.
Hi,
In my rooted xperia sola, the system memory and internal storage became read only. So I can't open any apps that needed to write on system files... and am not able to flashing for reinstall. I was using root explorer as file manager, but now it can't mount root as r/w. Memory card and presence are working...
If I uninstall an application or delete a file from internal storage, after rebooting that app or file will be still there. Even rom toolbox is failed to uninstallation of apps. When using flashtool it says too many bad blocks and read only file system. What can I do in this situation.... please help me...
Any solution for this issue?
I also have this kind of problem, my phone is now useless due to application crashed.
I tried PC Companion and Sony Mobile FlashTool but no luck.
Open recovery and try fixing permission
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
I think its issue with rom
---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------
Try to mount system folder as read and write using es file explorer or root explorer but make sure you are rooted and have given file explorer root permissiond
---------- Post added at 08:23 AM ---------- Previous post was at 08:23 AM ----------
Plz report after doing
You can try to run "adb remount". This command should be able to remount /system as rw .