Related
I mean, I have this file on my SD card from when I rooted (downgrading from 1.72)
If I flash this ROM, it will just flash stock 1.34 (which I'm running at the moment) right?
I think I left it on my SD card as "backup" because it can be installed from the bootloader, but now I'm wondering whether this is necessary, and whether I can delete it
Cheers
Edit: Also, I have some other files backed up, not sure if I need them
part7backup
part17backup
su
superuser.apk
make a backup dir on sdcard and move the zip file into this dir.
LooieENG said:
I mean, I have this file on my SD card from when I rooted (downgrading from 1.72)
If I flash this ROM, it will just flash stock 1.34 (which I'm running at the moment) right?
I think I left it on my SD card as "backup" because it can be installed from the bootloader, but now I'm wondering whether this is necessary, and whether I can delete it
Cheers
Edit: Also, I have some other files backed up, not sure if I need them
part7backup
part17backup
su
superuser.apk
Click to expand...
Click to collapse
Yes that is going to be a stock rom, no root.
As for the other files the part files you should copy to your PC the su and superuser files are not needed as long as you only flash roms that are pre-rooted.
LooieENG said:
part7backup
part17backup
Click to expand...
Click to collapse
Copy these two to your computer, as (I think?) one of them is a backup of the /misc partition before running gfree to S-OFF, not sure about the other though
Thanks for the replies
So I should keep the part backup files on my computer, and if I keep that ROM on there, that should mean that if I mess up and can't get to recovery, as long as I can get to the default bootloader, I can flash it from there, right?
This guide is based on a guide by Candanga on the i9000 forums, and some commands from supercurio
Please hit thanks on their posts and show them some love for the write up.
-----------------------------------------------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centres.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
What you will need:
Rooted SGS II to get permissions as a SU (Super User) and perform the backup
I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile. <- Busybox Commands(or Google them)
Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS II during this process, because it may request SU permissions [currently doesn't on CF-root]; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS II.
Here are 3 methods, I recommend that you do both Clean and RAW.
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD in sdcard/efs/, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can greatly support in recovering your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
+1 just do it....
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
JJEgan said:
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
Click to expand...
Click to collapse
From the thread:
I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
Click to expand...
Click to collapse
And just copying the folder won't preserve permissions etc.
JJEgan said:
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
Click to expand...
Click to collapse
As long as you don't copy it to /sdcard, because it's VFAT and you'll lose the permissions settings on the files. If you copy it to /data or something then that's fine.
bumpity bump
RyanZA said:
As long as you don't copy it to /sdcard, because it's VFAT and you'll lose the permissions settings on the files. If you copy it to /data or something then that's fine.
Click to expand...
Click to collapse
Thanks the SGS 1 EFs i copied was copied to external sd card and then copied off to PC . Did likewise on SGS 2 using Super Manager .
So according to what you are saying that was not going to back up if needed .
jje
JJEgan said:
Thanks the SGS 1 EFs i copied was copied to external sd card and then copied off to PC . Did likewise on SGS 2 using Super Manager .
So according to what you are saying that was not going to back up if needed .
jje
Click to expand...
Click to collapse
It would probably have worked, but it would have made your EFS files readable and writable by any app that tried - not the end of the world since it's unlikely that any apps would try, but you still might as well avoid it if you can. I don't think there are any executables in EFS or anything that this will actually break though.
Thanks i did lose IMEI at one flash on SGS1 but a second flash recovered it .
I do like full backup of original firmware and anything else before playing with phone .
jje
I've done all 3 forms of backup myself. . Clean, raw and basic
thanks for the info. have had close calls previously and having backups would have helped ease the stress
Updated first post
Vodafone Fimrware backup BUKE1
Guys,
Have got a new samsung from Vodafone UK , but the firmware kernel seems a bit different, BUKE1. Is this something now and is the above method correct to backup the entire firmware so that it might be useful for vodafone samsung users. Is there an easy guide to backup the firmware ?
Regards
VJ
Guys can someone give me a bit of advice pleeeease
I followed this guide but am a bit worried i might have messed it up, i'm comfortable with command prompt as i'm a software dev but haven't used linux commands much.
Anyway i used the ADB shell from the Android SDK tools and entered the first command to backup the efs directory to the internal sdcard....
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Click to expand...
Click to collapse
And i got a lot of
Code:
cp: can't preserve ownership of 'sdcard/efs/...' : Operation not permitted
messages flashing up?
However i checked to see if the backup had been made and it had? What does this mean?
Next i compressed it using...
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
Click to expand...
Click to collapse
Which seemed to work as i have the file in the place i expect
When i did the next step...
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can support greatly to recover your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
Click to expand...
Click to collapse
It completed really quickly, with no messages telling me it was done but when i checked root explorer i couldn't find /dev/block/mmcblk0p1?
What has it done with it? I have dev/block/ but there is no mmcblk0p1? Although i do have /sdcard/efs_dev-block-mmcblk0p1.img. Should i have both?
From what i understand cat concatenates files and prints them to standard output, so i'm assuming the > is piping the std output to the internal sdcard?
Sorry for the questions but i thought i understood what i was doing but the last step and the "can't preserve ownership of.." messages from the first step threw me
Could someone explain this to me a little ;p
These aren't steps but rather separate methods achieving different things. Don't bother about the first one - it notes unix permissions lost , which is why you are seeing the can't preserve ownership messages. The files still backup but correct r/w permissions do not. You may as well chuck the files really, since you managed the tarball (second instruction). Just grab this and backup to external storage, in case you ever need it.
The raw backup will be under sdcard as you have found - stash this away somewhere safe too. You won't find mmcblk0p1 in root explorer as it is a partition, not a folder.
Thanks for the swift reply simion_levi
These aren't steps but rather separate methods achieving different things. Don't bother about the first one - it notes unix permissions lost , which is why you are seeing the can't preserve ownership messages. The files still backup but correct r/w permissions do not. You may as well chuck the files really, since you managed the tarball (second instruction). Just grab this and backup to external storage, in case you ever need it.
Click to expand...
Click to collapse
Do if i move the tarball to the external drive i can get rid of the sdcard/efs directory i copied to the internal card? The tarball has all the correct permissions?
The raw backup will be under sdcard as you have found - stash this away somewhere safe too. You won't find mmcblk0p1 in root explorer as it is a partition, not a folder.
Click to expand...
Click to collapse
Ok i didn't realise it was a partition, so i've just created an image of the partition that the efs folder resides on? Should i copy this to my external sd card as well?
Cheers brother
No problem! Yes, you've got it - backup the tarball and the partition image to computers, external drives etc so you can recover back to the phone in case of future catastrophe. The sdcard/efs directory can be deleted as the tarball contains exactly the same files (but with correct permissions).
Awesome, will get it done later. Out of interest how do you recover the partition image in the event of a disaster occurring?
Sent from my GT-I9100 using XDA App
One question please, since i stumbled on this one almost by luck.
Is there anything else to save before departing from stock?
Thanks.
Okay, so this guide assumes I already rooted my phone, but as a newbie I am completely in the dark about what does and what does not potentially harm the /efs. I would rather backup EVERYTHING before I flash/change anything, but from what I have read so far I need at least root to do backups.
Would it be safe to flash the Lite'ning Rom v1.1, coming from stock I9100XWKE2/I9100XENKE1/I9100XXKDJ/I9100XWKE2, and then backup mmcblk0p1?
Thanks!
Soo, I know there's a lot of these threads around, but I can't find the answer I'm looking for. I'm wondering: After I flashed 4.2 I got this extra "0" folder on my internal sdcarrd. Can I just cut/paste the content of the "0" folder back to the original sdcard root? or will this have a negative effect on the storage?
Regards.
olfyboy said:
Soo, I know there's a lot of these threads around, but I can't find the answer I'm looking for. I'm wondering: After I flashed 4.2 I got this extra "0" folder on my internal sdcarrd. Can I just cut/paste the content of the "0" folder back to the original sdcard root? or will this have a negative effect on the storage?
Regards.
Click to expand...
Click to collapse
I had this issue earlier so i moved everything back to the root folder and deleted "0". If you are planning on flashing a few 4.2 roms i suggest you use the latest TWRP recovery or wait for the updated clockwork recovery because everytime you flash 4.2 roms they automatically create a 0 partition so you will end up with 0/0/0 etc depending on how many you flash
K, thanks!
I think I'll just copy the content of the "\0" folder back to the root, and stick with the ROM I'm on now. Then I'll update CWM when an update is released.
Aaargh.. I'm getting kinda pissed now..
When I try to copy the sd-content back to the root, it says that the device has stopped responding, or isn't connected. Can you tell me what is the standard root folder for the sd-content?
After installing a previous backup the was still a 0 folder so I copied all of the files to the root folder however it made the pictures unable to view
Sent from my Galaxy Nexus using xda app-developers app
I've tried several methods to move my clockworkmod folder out of the "0" folder to the sdcard "root" to no avail.
I'm currently backing up everything from "0" to my desktop. Once that's done, how can I push the clockworkmod folder to the sdcard "root"?
daewond3r said:
I've tried several methods to move my clockworkmod folder out of the "0" folder to the sdcard "root" to no avail.
I'm currently backing up everything from "0" to my desktop. Once that's done, how can I push the clockworkmod folder to the sdcard "root"?
Click to expand...
Click to collapse
Seems like there are some problems copying big folders over to the root. Try to first copy the CWM folder from your PC into some folder on the sd-root. Then, from your phone, open up a file explorer and copy the CWM folder to the root. Pretty weird, but it looks like it's working for me..
Edit: Yupp! worked for me. Hope you'll sort it out aswell.
olfyboy said:
Seems like there are some problems copying big folders over to the root. Try to first copy the CWM folder from your PC into some folder on the sd-root. Then, from your phone, open up a file explorer and copy the CWM folder to the root. Pretty weird, but it looks like it's working for me..
Edit: Yupp! worked for me. Hope you'll sort it out aswell.
Click to expand...
Click to collapse
Thanks for the help!
What file explorer did you use? Every one that I've used takes me directly to the "0" folder when I hit "sdcard" thus I can't seem to paste the clockworkmod folder into sdcard root.
daewond3r said:
Thanks for the help!
What file explorer did you use? Every one that I've used takes me directly to the "0" folder when I hit "sdcard" thus I can't seem to paste the clockworkmod folder into sdcard root.
Click to expand...
Click to collapse
move it to /data/media
---------- Post added at 12:26 AM ---------- Previous post was at 12:11 AM ----------
here's how it works
before the virtual link to /sdcard was /data/media
cwm was writing under /data/media so cwm folder would show up under /sdcard as well
now the virtual link to /sdcard is /data/media/0
that's because of multiuser (even if multiuser is not working on phones)
cwm is still wriyinb to /data/media so cwm golder eoll mot show up under /sdcard
solutions
1. to copy cwm foldrr on pc: move cwm folder from /data/media to /data/media/0 that is to /sdcard then attach phone to pc and copy folder from sdcard
2. to restore from a backup on your vomputer: attach phone to pc, create cwm folder on sdcard andcopy h erebackup folis, copy cwm foldef from /data/media/0 into /dara/media
it is normal to have a /data/media/0 which means /sdcsrd
it is not normal to have /data/media/0/0 which means /sdcard/0
the latter happens on your second installation etc.
daewond3r said:
Thanks for the help!
What file explorer did you use? Every one that I've used takes me directly to the "0" folder when I hit "sdcard" thus I can't seem to paste the clockworkmod folder into sdcard root.
Click to expand...
Click to collapse
I used solid explorer beta2. You'll find it on google play
Sent from my Galaxy Nexus using Tapatalk 2
I haven't updated to 4.2 yet because of this sdcard/0 issue I'm reading about
I don't care much about what's on my SD card besides my Nandroid backups so the only thing for me is: can I restore a backup from CWM if I move the "clockworkmod" folder from sdcard/0 back to the root of the SD card?
I assume there's no other adverse effects of all our files and stuff being on sdcard/0 instead of just sdcard root?
Enhanced said:
I haven't updated to 4.2 yet because of this sdcard/0 issue I'm reading about
I don't care much about what's on my SD card besides my Nandroid backups so the only thing for me is: can I restore a backup from CWM if I move the "clockworkmod" folder from sdcard/0 back to the root of the SD card?
I assume there's no other adverse effects of all our files and stuff being on sdcard/0 instead of just sdcard root?
Click to expand...
Click to collapse
read my commeny above: yes, although cumbersone, yes
I'm thinking this is the appropriate thread to post this so here I go. I flashed the newly released 4.2 rooted stock image and there were a few problems :
1. I forgot to delete the cache/dalvik cache, which created a bootloop and completely messed up my device, and I had to wipe/factory data reset from the recovery to fix it (in which case I had to lose almost all of my data)
2. I accidently overwrote an existing nandroid backup of the previous (CM 10 stable) ROM I had made to restore just in case anything happens, so I was out of options to restore my nexus to a working state. I finally had to use the crashed ROM's nandroid backup using an advanced recovery so I had my photos, videos etc intact. I got it finally working but anyways,
3. I restored my apps+data using titanium backup. I wanted to go back to my CM10 backup which I had made using ROM manager and it was still present with the rest of my data. But when I selected the backup which made, the device restarted and gave me an error stating "SD CARD MARKER NOT FOUND" :crying:
Now I'm unable to restore or even make a new backup with ROM manager. And to add, I have like three folders for storage using up too much space on my sdcard :
1. root/sdcard - I have no idea where this came from but it sure has an awful lot of my files copied there
2. root/storage/sdcard0
3. root/storage/emulated - has two subfolders : 0, legacy
All of the above locations contain the same exact files and I just want my nexus back the way it was. I know I can flash CM10 right away but I just wanna get some help on how to delete and make changes to these added folders by properly moving the files without crashing the os.
Any help would be greatly appreciated!
I am having this issue as well and am very very annoyed. Please help. Thanks. I cannot get into recovery manually or otherwise. Keep getting Andy with the red exclamation mark in his chest and must remove battery to reboot.
Fu#k rom manager and CWM use TWRP an rom toolbox pro an you will be fine on 4.2 JB.
Sent from my Galaxy Nexus using xda premium
Update: got it working.. had to flash back cm10 stable, move files around and get back the old ROM manager backup and restore it. Its fine now. Not to mention the 4.2 ROM was pretty unstable on my nexus, causing several reboots and sometimes it froze (especially when I connected it to my desktop) and I had to remove the battery and put it back in to get it working. Moreover the 4.2 rom screwed up the file system, making my nexus' SD card unreadable on any desktop. It just wouldn't install the drivers whatsoever. I'd wait for cm10.1 than try any other custom 4.2 from now on.
Sent from my Galaxy Nexus using xda app-developers app
daewond3r said:
Thanks for the help!
What file explorer did you use? Every one that I've used takes me directly to the "0" folder when I hit "sdcard" thus I can't seem to paste the clockworkmod folder into sdcard root.
Click to expand...
Click to collapse
You can download Root Browser Lite from play store, which gives you complete access to the root of your phone and internal files such as system/.
Hey guys wanted to know how can i clean wipe all the data folders on my phone except the new ROM file i want to flash
i have done normal formats and wipes but got so many dead/duplicated folders on it with the 0/0 and some other stuff
for exmple with root browser i got the SDCARD folder and then i got the STORAGE/SDCARD0 folder again
also got STORAGE/EMULATED/0/ and here ALSO all the files
and also on STORAGE/EMULATED/LEGACY
what am i missing guys?
The SDCARD folders are in fact only links to the real sdcard folder.
I think these links are needed because android used to have another folder structure and older apps wouldn't be able to accept the sdcard.
For a completely clean wipe you can select wipe internal data in TWRP. Maybe you can push the ROM you want to flash via ADB push. But I'm not sure about that.
Cliff666 said:
The SDCARD folders are in fact only links to the real sdcard folder.
I think these links are needed because android used to have another folder structure and older apps wouldn't be able to accept the sdcard.
For a completely clean wipe you can select wipe internal data in TWRP. Maybe you can push the ROM you want to flash via ADB push. But I'm not sure about that.
Click to expand...
Click to collapse
Ok thanks bud, its just that i know that the /0/ folder is a shortcut to the real folder yet the other 2 i wrote down are old files that i had with other ROMS i have used back in the day
Tried to remove the tmobile Carrier IQ from my device, last week. I used Solid explorer, to do it. This is the list:
/system/app
QXDM2SD.apk
QXDM2SD.odex
HtcResetNotify.apk
HtcResetNotify.odex
Htcloglevel.apk
Htcloglevel.odex
Smith.apk
Smith.odex
Udove.apk
Udove.odex
/system/priv-app
IQ-tmobile-release-signed.apk ???????
IQ-tmobile-release-signed.odex ???????
IQToggle.signed.apk
IQToggle.signed.odex
MyBreeze.apk
MyBreeze.odex
/system/lib
system/lib/libiq_service_tmobile_2.2.so
/data/data
com.carrieriq.tmobile
com.carrieriq.tmobile.IQToggle
The two questionable files above were slightly different, on my device. They read:
IQ-tmobile-release-unsigned.signed.apk
IQ-tmobile-release-unsigned.signed.odex
Against my better judgment, I continued to delete all of those files. Now, I can't even get past the banner on the home screen. It says, "Unfortunately, System Manager Application has stopped." I went to my bootloader and did a factory reset. Then, went to TWRP and did another factory reset and wiped the cache, dalvik & data. I used Firewater to unlock, root & S-OFF from KitKat Stock 4.4.2 and would prefer to keep it if possible. I had absolutely no problems with that version. The pictures are below.
As you can see, everything seems to be perfectly unaffected. I get calls, texts, voicemails, and every notification. It won't let me go beyond the home screen. If anyone can find KitKat 4.4.2 Stock Rom for Tmobile USA, I'd greatly appreciate it.
I am guessing you didn't do a backup before hand?
bradley_e_smith said:
I am guessing you didn't do a backup before hand?
Click to expand...
Click to collapse
Actually, I did a Titanium & NAND backup. But I didn't keep a copy of the NAND, in the internal storage. I just got an OTG Adapter. Gonna see if I can push the NAND onto the internal storage. Hopefully, it'll work. If not, I could definitely use your expertise.
Well then, all you need to do is to unpack the nand backup on your PC, and find the missing files and using TRWP mount / as rw and push the files back to your phone.
bradley_e_smith said:
Well then, all you need to do is to unpack the nand backup on your PC, and find the missing files and using TRWP mount / as rw and push the files back to your phone.
Click to expand...
Click to collapse
So, how do I do that?
Take your backup. the files that end in .win000, win001, win002, etc are tar files. So the easiest way would be to get a 'tar' program (cygwin has one built into it), and looking at each file look (tar -vtf [filename] -> will list the contents of the archive) for your missing files. By using -xvf option you can extract the file(s) you need.
BTW: On my lollipop backup of my M8 phone I didn't see any file that "IQ" in the filename, so kitkat must be different than lollipop.
-brad