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?
Related
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?
Forgot to have nandroid backup . Wiped data, cache partition, dalvik cache, battery stats Couple of times. Screwed up the phone for flashing, No signal.. Later, I was able to fix it with SGSII_repair But, stuck with a generic IMEI (004999010640000). I haven't backed up efs folder. Now I'm only left with cryptprop_es in the previous efs folder.. Is there any way to restore original IMEI ???
computechnopro said:
Forgot to have nandroid backup . Wiped data, cache partition, dalvik cache, battery stats Couple of times. Screwed up the phone for flashing, No signal.. Later, I was able to fix it with SGSII_repair But, stuck with a generic IMEI (004999010640000). I haven't backed up efs folder. Now I'm only left with cryptprop_es in the previous efs folder.. Is there any way to restore original IMEI ???
Click to expand...
Click to collapse
Try this ! You must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.
IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:
1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]
2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.
3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.
4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder
7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"
8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:
adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin
9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.
If all the above steps do not work, check with a called developer Odia on XDA, he has recovered many phones with lost EFS.
All the best.Hope this helps!
ksantoshh said:
Try this ! You must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.
IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:
1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]
2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.
3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.
4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder
7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"
8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:
adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin
9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.
If all the above steps do not work, check with a called developer Odia on XDA, he has recovered many phones with lost EFS.
All the best.Hope this helps!
Click to expand...
Click to collapse
I don't have the nv_data files or, anything related to that !!!
Have you tried GSII_Repair from the Market ? This might be your last best chance before you need to send it to Samsung/your telco for repair. Look for it, read the description & then decide whether you want to try it or not.
If this doesn't work, nothing else will.
Edit to add - My bad.
MistahBungle said:
Have you tried GSII_Repair from the Market ? This might be your last best chance before you need to send it to Samsung/your telco for repair. Look for it, read the description & then decide whether you want to try it or not.
If this doesn't work, nothing else will.
Click to expand...
Click to collapse
Yeah !. This is the App Which Has Set The Generic IMEI & Brought Back The Phone's Signal !!! Would it Be A Problem in Future if, I Stick With This Generic IMEI ??? (I Know That Some Operator Blocks This IMEI But, Mine Didn't, Yet..)
MistahBungle said:
Have you tried GSII_Repair from the Market ? This might be your last best chance before you need to send it to Samsung/your telco for repair. Look for it, read the description & then decide whether you want to try it or not.
If this doesn't work, nothing else will.
Click to expand...
Click to collapse
He says in the opening post he has tried GSII_Repair which gave him the generic IMEI.
OP, if your EFS folder is empty and you made no previous backups I suspect you will have to send it for repair.
Imei is known by telephone company?
Can't he just get imei from them and create new folder if there is no backup?
Isn't imei on phone box?
Sent from my HTC Glacier using XDA App
The necessary files are encrypted. Even if he knows the IMEI it's not just a simple case of creating a text file with it in for example. I wouldn't be surprised if his MAC address has gone too.
Do a search for the post about user ODIA who has helped some with no IMEI .
jje
ksantoshh said:
Try this ! You must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.
IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:
1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]
2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.
3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.
4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder
7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"
8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:
adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin
9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.
If all the above steps do not work, check with a called developer Odia on XDA, he has recovered many phones with lost EFS.
All the best.Hope this helps!
Click to expand...
Click to collapse
I am not able to delete the efs folder from the root dir. stuck at that step ... please help ...
ano.cresent said:
I am not able to delete the efs folder from the root dir. stuck at that step ... please help ...
Click to expand...
Click to collapse
I believe you have to remount your root folder as R/W.
Are you using a rooted phone with root explorer set to read write ????
jje
suggestion thru my experience
ano.cresent said:
I am not able to delete the efs folder from the root dir. stuck at that step ... please help ...
Click to expand...
Click to collapse
for my phone i encounter that imei 00...... i just save by the online back up where its automaticaly back up my data online and i found my efs folder. very simple step what i did. i ownload this efs file foler then all the conten inside i just copy to efs folder in my root directory and asking to replace existing file yes then reboot the phone. after reboot i checked my imei thru *#06# it back to the original same with the sticker under my battery pack on my gt i9000 hope it will help for other people easy and simple step it will back to original if you have back up efs file..
just to shared my experienced regarding to the problem stated..
Does anyone know where the App folder is on an S2?
I have installed a new ROM (CM7.2.0) and now my phone is stuck with LaucherPro constantly crashing, so I cannot access the running apps to cancel it.
I have got ADB working and I can see the folders on the phone but I cannot find the App folder (I have checked all of the folders). All I have under system is a bin folder and nothing in the data folder.
I had made an Nandroid image before I changed the ROM, but that has now has a duff MD5 checksum (no error when initially created. I have attempted to re-create the checksum as per the instructions:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
all seems OK with the commands because I successfully deleted and re-created the nandroid.md5 file but it is still mis-matched, so I'm trying to remove LaucherPro.
I have created a new nandroid image from the problem ROM and as expected LauncherPro crashes on that image also.
NOTE - Some of the nandroid images that were OK also now fail to pass the checksum!
I have an old nandroid image (CM 7.2.0) that I have restored to, so I have a working phone, but I would like to get back to my last set-up by removing the problematic LaucherPro app.
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
Hi guys, having an odd problem.
I've made some nandroid backups (about three) via CWM Recovery, and I can't seem to browse to them, or delete them.
It's definitely taking up space, and I'm not sure what to do now.
A backup that I made straight to my external SD card however, seems to be browse-able, so I'm a bit confused now.
Attached are some screenshots from ES File Browser (with root access turned on).
The last screenshot is going to /storage/sdcard0/clockworkmod/ (same directory, but now I can't seem to see anything about "backups").
I've also tried to delete these backups straight from CWM Recovery, but CWM says that it can't access the folder.
Oddly enough, if I do another backup (straight to internal), it seems to put all the files in /sdcard/Clockworkmod/backups but never to be accessed again.
Anyone have any ideas?
Delete via Windows Explorer .
jje
JJEgan said:
Delete via Windows Explorer .
jje
Click to expand...
Click to collapse
Thanks for the suggestion, but nope, that didn't work. (Obviously tried that first).
The folder was shown as empty via Windows.
After a lot of digging and trying different things (including Root Explorer and Terminal Emulator), I've managed to delete it.
I'll post the instructions so other people who may have similar problems in the future can follow it.
First, you'll need ADB and you'll need to reboot into CWM Recovery.
Once you've gotten that sorted, boot into CWM Recovery and go to "mount and storage" and then select "mount /data".
This will mount the /data structure which we need to use.
Afterwards in CMD, use the following:
Code:
adb root
adb shell
After this, you should be logged in as ~ (root)
Proceed to go into the directory using the cd function. (PROTIP: Use the ls function to check where you're going.)
You need to get to ../clockworkmod/backup/
You'll find that you can finally access the /backup/ folder, and you'll then be able to delete the files. Please note that the below command will delete ALL the files within this folder.
Code:
rm -rf *
Afterwards, do
Code:
cd ..
to get back to the ../clockworkmod/ folder and then run the below code to delete the now empty /backup/ folder:
Code:
rmdir backup
no, to be logged in as root you need to type in "su"