I kinda screwed my efs folder.
I have no IMEI and my Baseband is Unkown.
I tried re-flashing a modem, re-flashing to stock, but nothing seems to work.
So I tried restoring my backup of the efs folder.
I have a backup of my efs folder in 2 forms:
efs_28Oct2011-2110.tar.gz
and
efs.autobackup.img
But I can't get any of these to work. I search all forums, but it just fail everytime.
Anyone has any advice? I really don't know how to apply these backups.
Firstly, be very careful with what you're doing!
You can restore your EFS .img with helcat's kernel companion tool. Download from this post
http://forum.xda-developers.com/showthread.php?t=1182922
OR, in your EFS gz file, find and extract nv_data.bin and copy to your internal sdcard. Now in a terminal emulator or adb
cp /sdcard/nv_data.bin /efs/nv_data.bin
rm -rf /efs/nv_data.bin.md5
After restoring your IMEI using one of the methods above, your SIM might not work. If that should happen, remove the sim card, boot your phone and run this command
su
chown 1001:1001 /efs/nv_data.bin
Well the first way didn't work, actually it cleared the whole efs folder, I don't understand why.
Now i'm trying the second way, but it gives:
Can't create /efs/nv_data.bin : Read-only file system
Ok I managed to restore my complete efs folder, by using Root Explorer and the Tar.gz backup it all went fine, but I still don't have baseband: unkown and no IMEI, so I suppose it was al about the rom after all?
arcshooter said:
Ok I managed to restore my complete efs folder, by using Root Explorer and the Tar.gz backup it all went fine, but I still don't have baseband: unkown and no IMEI, so I suppose it was al about the rom after all?
Click to expand...
Click to collapse
>> First take backup using mybackup pro
>> Flash the ROM Using Odin method,once rebooted do factory reset
>>I believe u should get back
sendhiloo7 said:
>> First take backup using mybackup pro
>> Flash the ROM Using Odin method,once rebooted do factory reset
>>I believe u should get back
Click to expand...
Click to collapse
Well thx, I'm gonna try this, but I just realized that every time I reboot my device, my just restored efs with root explorer is empty again, think I have to fix this first?
This is exactly what happened too me:
http://forum.xda-developers.com/showthread.php?p=18026421
So when i try to restore it :
1)Using Hellcat's kTool .It gives the msg "efs restored.you may want to reboot now."
but when i check in /efs folder it is still empty.And after reboot there is only 1 file named cryptprop_essiv (1 byte) in it.
using terminal emulator
a)i type
Code:
su
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
it says
Code:
efs/
efs/cryptprop_rebootMode
tar:can't remove old file efs/cryptprop_rebootMode:
read-only file system
#tar:write: Broken pipe
then when i try the above after mounting /efs as r/w in root explorer,then this happens
Code:
efs/
efs/cryptprop_rebootMode
efs/cryptprop_onetimeboot
efs/cryptprop_securewipedata
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/nv_data.bin
efs/nv.log
efs/nv_data.bin.md5
efs/dmp/
efs/dmp/sett/
efs/dmp/sett/system/
efs/dmp/sett/system/volume_ring_last_audible
efs/dmp/sett/system/vibrate_on
efs/dmp/sett/system/time_12_24
efs/dmp/sett/system/screen_brightness_mode
efs/dmp/sett/system/volume_ring
efs/dmp/sett/system/volume_notification
efs/dmp/sett/system/volume_notification_last_audible
efs/dmp/sett/system/dtmf_tone
efs/dmp/sett/system/sound_effects_enabled
efs/dmp/sett/system/haptic_feedback_enabled
efs/dmp/sett/system/VIB_FEEDBACK_MAGNITUDE
efs/dmp/sett/system/screen_brightness
efs/dmp/sett/system/screen_off_timeout
efs/dmp/sett/system/mode_ringer
efs/dmp/sett/system/volume_system
efs/dmp/sett/system/volume_system_last_audible
efs/dmp/sett/system/vibrate_in_silent
efs/dmp/sett/system/airplane_mode_on
efs/dmp/sett/system/power_saving_mode
efs/dmp/sett/secure/
efs/dmp/sett/secure/mobile_data
efs/cryptprop_applied_result
efs/imei/
efs/imei/mps_code.dat
efs/imei/bt.txt
efs/imei/keystr
efs/calibration_data
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/.nv_state
efs/redata.bin
efs/edk_p
efs/cryptprop_persist.sys.timezone
efs/cryptprop_lockscreen.patterneverchosen
efs/cryptprop_lockscreen.password_type
efs/cryptprop_lock_pattern_autolock
efs/cryptprop_lock_pattern_visible_pattern
efs/cryptprop_lock_pattern_tactile_feedback_enabled
efs/cryptprop_lockscreen.lockoutattemptdeadline
#
After this all files get back in /efs,but after i reboot.same problem occurs.no imei.Only 1 file present in folder
cryptprop_essiv
b)when i try to use this method
Code:
su
busybox umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
it says
Code:
umount:can't umount /efs:Invalid argument
and i just did a little experiment.i just copied a small random file in the efs folder.after i reboot it is gone and replaced by that cryptprop_essiv file.
even if i delete this file and reboot it comes back again.
Click to expand...
Click to collapse
But I can't figure out how he fixed it, just doing whats said there isn't working.
To restore your EFS from your tar.gz file the commands are as following:
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs_28Oct2011-2110.tar.gz -C /
reboot
Not sure about how to restore your img file though but the tar.gz file should work.
Wow, out of the blue, after I tried every and really every way to restore it, your code just works! HERO! Thx
Now I'm sure my efs folder is fine and not corrupt, but still it gives
IMEI (nothing)
Baseband: Unknown
And it won't recognize my sim.
What is the problem here?
Related
I have now seen a number of cases of the EFS partition getting wiped / corrupted on the SGS II, leaving users with an effectively useless phone.
With this in mind, i've written a little init.d script for my ROM which backs up the EFS partition on boot if a backup does not already exist. A non intrusive safety net for users if you will.
The script just needs a suitable boot image that runs init.d, although it could easily be tacked onto the end of install-recovery.sh if that's not the case.
I'd love to encourage all developers to use this script for users' sake!
You can download the script here - http://cl.ly/2j0p0R3F07052m2T2u0e - but it's very simple, here's the code...
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs.autobackup.img ];
then
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.autobackup.img
fi
umount /sdcard
Note the manual mount / umount of sdcard is necessary because this happens late in the boot process.
Cheers!
P
Hats of to you Paul.Although I have already made a backup of my EFS folder,such a script would save MANY people from A LOT of trouble.
tolis626 said:
Hats of to you Paul.Although I have already made a backup of my EFS folder,such a script would save MANY people from A LOT of trouble.
Click to expand...
Click to collapse
i havent...never did. i think i wiped about a hundred times now and flashed and reflashed...is it possible to recover the efs folder?
haasgo said:
i havent...never did. i think i wiped about a hundred times now and flashed and reflashed...is it possible to recover the efs folder?
Click to expand...
Click to collapse
If your phone is working, it means your EFS partition is still there...
You can back it up using the many tutorials out there in the forum...
Sent from my GT-I9100 using XDA Premium App
Problem is that the users who read how to backup EFS folder fall in to two category s those that read up first and would have backed up EFS and those that only pick the manual up after something is broke .
This script would be a saver for many of the second group and big thanks to Paul and i hope devs do run with it .
jje
I would like to adapt your script for Nexus S.
Once i got the img file of efs partition, how do can a make a script for restoring thet img file to efs partition?
Or what to do with that img file?
EDIT: @ paul - One more question - how do I mount /sdcard on Nexus S through the script? mount command in the Terminal Emulator shows my /dev/blocks/vold/179:3 as mount point, but if I use that mount point in the script it won't mount the /sdcard. Any idea?
EDIT2: I got it working with this command:
mount /dev/block/platform/s3c-sdhci.0/by-name/media /sdcard
and I got the efs.autobackup.img on my sdcard.
How do I restore the efs.autobackup.img to efs partition?
Thanks Paul this is a very useful utility hope it gets sticky
May i ask what conditions these people are falling foul of getting the EFS wiped? Is it rouge roms/cwm zips, wiping to much in recovery, Odin flashing?
Curious so i may steer clear, have a backup but staying away is half the battle
paulobrien said:
You can download the script here - http://cl.ly/2j0p0R3F07052m2T2u0e - but it's very simple, here's the code...
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs.autobackup.img ];
then
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.autobackup.img
fi
umount /sdcard
Click to expand...
Click to collapse
Hi Paul, I have modified your script so that it makes a tar file, tar file keeps the permissions for the efs partition and its easier to restore. Here it is:
Code:
#!/system/bin/sh
# EFS auto backup script for Samsung Galaxy S II
# By @paulobrien - http://s2.MoDaCo.com
mount /dev/block/mmcblk0p11 /sdcard
if [ ! -f /sdcard/efs_autobackup/efs-backup.tar.gz ];
then
mkdir /mnt/sdcard/efs_autobackup
busybox tar zcvf /sdcard/efs_autobackup/efs-backup.tar.gz /efs
fi
umount /sdcard
mynamesteve said:
Thanks Paul this is a very useful utility hope it gets sticky
May i ask what conditions these people are falling foul of getting the EFS wiped? Is it rouge roms/cwm zips, wiping to much in recovery, Odin flashing?
Curious so i may steer clear, have a backup but staying away is half the battle
Click to expand...
Click to collapse
Some hit "wipe EFS" in ODIN.
It's possible to mess up a zip badly enough to wipe EFS
A normal wipe shouldn't do it, but a bad CWM build could in theory do it...
A dodgy "virus" could do it, if it were targetting rooted phones, or had a root exploit.
That's why I keep an EFS backup on my PC and off-site
brainmaster said:
Hi Paul, I have modified your script so that it makes a tar file, tar file keeps the permissions for the efs partition and its easier to restore.
Click to expand...
Click to collapse
Nope dd is much better, but safer to have both, but dd should be used with bs=4096k option.
how to restore the efs folder?
how to restore the efs folder?
Please, need to restore EFS, not sure what happened but tried installing Cognition R3 and lost my EFS, I do however have a prior efs.autobackup. Please help.
Hello,i accidently deleted all the files inside /efs while messing with root explorer.Now the /efs folder is empty.
but i had done backup (both clean and raw).(have both tar.gz and .img of mmcblk0p1)
So when i try to restore it :
1)Using Hellcat's kTool .It gives the msg "efs restored.you may want to reboot now."
but when i check in /efs folder it is still empty.And after reboot there is only 1 file named cryptprop_essiv (1 byte) in it.
using terminal emulator
a)i type
Code:
su
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
it says
Code:
efs/
efs/cryptprop_rebootMode
tar:can't remove old file efs/cryptprop_rebootMode:
read-only file system
#tar:write: Broken pipe
then when i try the above after mounting /efs as r/w in root explorer,then this happens
Code:
efs/
efs/cryptprop_rebootMode
efs/cryptprop_onetimeboot
efs/cryptprop_securewipedata
efs/.files/
efs/.files/.dx1/
efs/.files/.dm33/
efs/.files/.mp301/
efs/nv_data.bin
efs/nv.log
efs/nv_data.bin.md5
efs/dmp/
efs/dmp/sett/
efs/dmp/sett/system/
efs/dmp/sett/system/volume_ring_last_audible
efs/dmp/sett/system/vibrate_on
efs/dmp/sett/system/time_12_24
efs/dmp/sett/system/screen_brightness_mode
efs/dmp/sett/system/volume_ring
efs/dmp/sett/system/volume_notification
efs/dmp/sett/system/volume_notification_last_audible
efs/dmp/sett/system/dtmf_tone
efs/dmp/sett/system/sound_effects_enabled
efs/dmp/sett/system/haptic_feedback_enabled
efs/dmp/sett/system/VIB_FEEDBACK_MAGNITUDE
efs/dmp/sett/system/screen_brightness
efs/dmp/sett/system/screen_off_timeout
efs/dmp/sett/system/mode_ringer
efs/dmp/sett/system/volume_system
efs/dmp/sett/system/volume_system_last_audible
efs/dmp/sett/system/vibrate_in_silent
efs/dmp/sett/system/airplane_mode_on
efs/dmp/sett/system/power_saving_mode
efs/dmp/sett/secure/
efs/dmp/sett/secure/mobile_data
efs/cryptprop_applied_result
efs/imei/
efs/imei/mps_code.dat
efs/imei/bt.txt
efs/imei/keystr
efs/calibration_data
efs/.nv_core.bak
efs/.nv_core.bak.md5
efs/.nv_data.bak
efs/.nv_data.bak.md5
efs/.nv_state
efs/redata.bin
efs/edk_p
efs/cryptprop_persist.sys.timezone
efs/cryptprop_lockscreen.patterneverchosen
efs/cryptprop_lockscreen.password_type
efs/cryptprop_lock_pattern_autolock
efs/cryptprop_lock_pattern_visible_pattern
efs/cryptprop_lock_pattern_tactile_feedback_enabled
efs/cryptprop_lockscreen.lockoutattemptdeadline
#
After this all files get back in /efs,but after i reboot.same problem occurs.no imei.Only 1 file present in folder
cryptprop_essiv
b)when i try to use this method
Code:
su
busybox umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
it says
Code:
umount:can't umount /efs:Invalid argument
and i just did a little experiment.i just copied a small random file in the efs folder.after i reboot it is gone and replaced by that cryptprop_essiv file.
even if i delete this file and reboot it comes back again.
Please any help would be appreciated.
i have the same problem too but i did't play with those folder it happened when my phone run out of battery and shut down it self when turn on no signal imei gone. inside efs folder only have cryptprop_essiv file
Seems like you have permission problems. I don't know if this will help any, but in CWM, goto Advanced, and Fix Permissions.
You could try using Heimdall to flash the efs.img using download mode.
You can get Heimdall at http://www.glassechidna.com.au/products/heimdall/
Using the command line should be as easy as when the phone is connected in download mode.
"heimdall flash --efs efs.img"
*If it is possible using Odin I don't know since I don't have Windows and have never used it.
** I have also never used the Heimdall GUI
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
seemsoweird said:
i solved it... i extract the tar.gz file and rename the .nv_data.bak to nv_data.bin and copy to efs folder then reboot and wait for awhile all done in root explorer ...by the way i also got fix permission but i dont know whether got effect anot.
Click to expand...
Click to collapse
please can you explain more how can you copy file in efs folder? becuase its system file read only?
Hi,
I have few questions in the EFS are..
i know that its the most important folder in Android system and it contains a lot of info abt the phone, imei etc etc....so my questions are...
1. What are the possible scenarios that EFS will get corrupt and show "BAD IMEI"?
2. Why its happening when we are not doing anything on that particular folder?
3. If a phone is never rooted, but flashes new ROMS, is SGS2 prone to EFS folder corrupt?
I am on KJ2 and not rooted and my phone is never rooted and i dont want to root also..at lease for near future....
Appreciate your help guys.....
Yes, EFS contains IMEI, wifi MAC address, product code, and other very important information, most of these in the nv_data.bin folder.
1) Attempting to change the product code, trying to unlock the phone, etc can result in corrupt data in EFS.
2) Answer is same as above, by using dfifferent methods one might try to change product code (example: to force install a rom or something that's not actually meant for his device)
3) SGS2 is a little prone to efs corruption while flashing roms. Installing official roms might have less risks, but still always backup efs folder because if there is no backup to restore, then the only way out is to take the device to a Samsung service centre.
(Assuming you're rooted, run in a terminal)
To Backup:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
this backs up efs as a .gz file in your internal usb storage.
To Restore:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs-backup.tar.gz -C /
reboot
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
wohenyingyu01 said:
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
Click to expand...
Click to collapse
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
thank u but it doesn't work. new backup changes nothing but make it biger, it seems that i can delete it by RE, but if i refresh i appears again. is there any way to format?
BroBot175 said:
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
Click to expand...
Click to collapse
Tubes6al4v said:
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
Click to expand...
Click to collapse
yep, but it confuses me if the backup exists forever.......
wohenyingyu01 said:
yep, but it confuses me if the backup exists forever.......
Click to expand...
Click to collapse
aha me to :L did you try the root explorer way?
BroBot175 said:
aha me to :L did you try the root explorer way?
Click to expand...
Click to collapse
yep, it doesn't work.....finally i flash the rom with formating scripts through odin, it seems xwkg4, and flash back. now everything's gone~
You can rename and delete backups with the rom manager app from the market.
http://market.android.com/details?id=com.koushikdutta.rommanager
while in recovery:
adb shell mount /data
adb shell rm -r /data/media/clockworkmod/backup/DATED_FOLDER
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
got the same problem and tried a lot
slack04 said:
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
Click to expand...
Click to collapse
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
i've tried to delete the backups in rom manager, but still can't and was told error occured while deleting.
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
really need reply if anyone else is confused with the same problem ...
chenxian352 said:
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
Click to expand...
Click to collapse
Is 5.8.3.1 for this tablet? If not...
chenxian352 said:
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
Click to expand...
Click to collapse
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
If his tablet is the GT-P7510 model, yes.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
sure about that, i got the recovery from clockworkmod.com.
i formatted it in windows, and everything was deleted but the clockworkmod folder! ghostly exist
something i just thought.. i'm using windows 7, when the tablet connect to my laptop, windows recognize it as a portable device. it's special i guess. is there any way to let it be removable disk?
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
MapleSyrup said:
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
If his tablet is the GT-P7510 model, yes.
Click to expand...
Click to collapse
thx for reply. yes my tablet is GT-P7510. i can't delete them in re explorer, delete failed.
could you please tell me how to mount the partition?
chenxian352 said:
could you please tell me how to mount the partition?
Click to expand...
Click to collapse
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
problem solved! thanks MapleSyrup
really thanks MapleSyrup! i executed all commands after normally powerup.
i just did them in cmw mode, all worked!
when normally powerup, in adb shell, command line prompt start with
Code:
[email protected]:/ #
in cmw(recovery) mode, it changes to
Code:
~ #
and no 'Permission denied' anymore when execute rm
i'm not English actually, literal words may be incorrect, hope readers could get it.
thanks sincerely. i've spent almost half day on the issue, you cant imagine how happy i am now, ha
MapleSyrup said:
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
Click to expand...
Click to collapse
I'm a little more of a newb here, and Don't understand the above stuff. I'm having the exact same issue.
ROM Manager basically just messed up my phone to the point that I can't delete backups in clockworkmod. Also the backups are showing 0 bytes in size even though they've taken up 3 gigs on my SDCard
I Got ROM manager to install the latest CWM, which is great. I Then was trying it out, and noticed you can do a backup right from it. It Loads CWM and performs a normal Nandroid backup.
Here is the issue, It shows that it has take up the space on my SDCard, but the folder contents are empty in clockworkmod/backups
Also, I can't delete them at all. I Tried ES Explorer and nothing worked. Said denied.
Hello xda!!
I own a GS3 i9300 and im a noob at android's and codings.
When I start the phone, I have no IMEI, cant see any carrier, I don't have lock screen and I don't have that power menu.
The only method I am using to correct this whole issue is :
-Go into Root Explorer
-Go to "/system/efs
-Copy the whole "Efs" directory
-Paste on /Efs
and voilá, it starts to work. I get everything back. The problem is I want this to be permanent, like a normal Phone. I have a rooted stock Rom. This might be simple to solve but I really don't know.
Thanks
raixa said:
Hello xda!!
I own a GS3 i9300 and im a noob at android's and codings.
When I start the phone, I have no IMEI,
Restore your backed up EFS folder .
Fix Permissions see sticky .
IMEI/ EFS see multiple posts on the subject .
jje
Click to expand...
Click to collapse
I've used fix permissions but i cant restore any EFS cause EFS pro says this "efs pro can't locate mount point"
Should I flash a new firmware and restore the EFS?
Just flashed stock firmware and Efs problem still continue.
I have the EFS backup.
The problem is that every single time my device reboots, the EFS folder appears, but has nothing inside. I can´t change permissions on the folder because root explorer wont let me.
Any solution?
raixa said:
Just flashed stock firmware and Efs problem still continue.
I have the EFS backup.
The problem is that every single time my device reboots, the EFS folder appears, but has nothing inside. I can´t change permissions on the folder because root explorer wont let me.
Any solution?
Click to expand...
Click to collapse
No firmware (stock or custom) modifies efs partition when flashed. If it was broken before, it will be when you flash stock firmware also.
You will need root access to fix this problem. If I had this problem I would flash a rom with root, busybox and as no other mods to be on the safe side (or root and install busybox on the stock one). Try to make a new file in /efs (use a file manager with root access) and reboot . The file should be there after restart. If it is the the phone is ok and you will just need to restore the backup. If it isn't you will need help from someone with more experience.
Thanks dav_991.
Just tried your solution but after the restart, there's nothing on /efs again.
One thing I noticed is that when I enter /efs folder its "mounted like R/W", but if I switch to "Mount R/O" and I get out of Root explorer, some files appear on the Efs folder. Thing is every time I restart the phone it appears mounted as R/W.
raixa said:
Thanks dav_991.
Just tried your solution but after the restart, there's nothing on /efs again.
One thing I noticed is that when I enter /efs folder its "mounted like R/W", but if I switch to "Mount R/O" and I get out of Root explorer, some files appear on the Efs folder. Thing is every time I restart the phone it appears mounted as R/W.
Click to expand...
Click to collapse
On my s3 /efs is mounted as rw by default. I do not think that this is related to your problem. To see which partition (and how) is mounted as /efs, in terminal emulator type (and grant permission when asked):
Code:
su
cat /proc/mounts | grep /efs
It should look like:
Code:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
Yot could also post the files that are in the efs partition before and after you mounted as ro with command:
Code:
ls -la /efs >/sdcard/efs_list.txt
In phone memory you will get a file named efs_list.txt with the names of the files (every time you run the command the file is overriten, take this in consideration. Also be careful not to misspell something, you could overrite something you need).
I did some more research and ended up being the /Efs folder that wasn't mounted.
Managed to solve it by the terminal, adding the SU command.
Thanks everyone.
Best Regards,
Luis Matos