Related
Is there a way to Backup and Restore Original Shipped Firmware? Is we have Norton Ghost for Android then it will be good...
The purpose is to claim the phone for warranty, after flashed with customized firmware. The phone's hardware might go fault.
Well as a previous sgs user I know that the best way is to have root on ur device then u can access cwm to create a complete image (backup) of ur current os.
I don't know if there is a better way of doing so
Cheers
Sent from my GT-I9100 using Tapatalk
A lot of branded roms are posted in the Branded rom post in dev section .
jje
For an own backup, exactely as you bought the phone, here's what I did:
- flash an insecure kernel (stock kernels are available for all FWs, so restoring original stock kernel is easy)
- apply root
- dump all important partitions:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
As a more easy/convinient alternative you could flash a kernel with a custom recovery (like CF-Root, containing CWM recovery) and use the Nandroid backup feature from the recovery menu - but those root-kernels usually perform a few more changes on the /system partition, so I did my "initial stock backup" just using an insecure kernel and root applied.
HellcatDroid said:
For an own backup, exactely as you bought the phone, here's what I did:
- flash an insecure kernel (stock kernels are available for all FWs, so restoring original stock kernel is easy)
- apply root
- dump all important partitions:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
As a more easy/convinient alternative you could flash a kernel with a custom recovery (like CF-Root, containing CWM recovery) and use the Nandroid backup feature from the recovery menu - but those root-kernels usually perform a few more changes on the /system partition, so I did my "initial stock backup" just using an insecure kernel and root applied.
Click to expand...
Click to collapse
Thanks for the advice! I have a question regarding Nandroid and CWM. Restoring the image made with Nandroid is easy enough, but won't the carrier/Samsung detect that a custom recovery (CWM) has been installed and consider it voiding the warranty regardless of the stock ROM being on the device?
Thanks in advance.
techjunkieza said:
Restoring the image made with Nandroid is easy enough, but won't the carrier/Samsung detect that a custom recovery (CWM) has been installed and consider it voiding the warranty regardless of the stock ROM being on the device?
Click to expand...
Click to collapse
After restoring a stock backup via a custom recovery/nandroid, just flash a stock kernel afterwards with Odin as well.
That will restore kernel and the recovery back to stock too.
All that is then left from a rooting is two files and a few symlinks hidden in /system/xbin - unlikely they'll go and check that IMO.
HellcatDroid said:
After restoring a stock backup via a custom recovery/nandroid, just flash a stock kernel afterwards with Odin as well.
That will restore kernel and the recovery back to stock too.
All that is then left from a rooting is two files and a few symlinks hidden in /system/xbin - unlikely they'll go and check that IMO.
Click to expand...
Click to collapse
Thanks dude. I was wondering how it is done. I did not know that flashing a stock kernel will make the recovery mode default as well. I'm new to Android so please forgive the noob questions. Surely there should be a list of files in a thread somewhere which indicates which files are modified when rooting the phone?
So I take it by restoring the original ROM, flashing a stock kernel (if you have a custom recovery mode or root access), removing the files and symlinks and resetting the ROM counter that the phone will be "stock" again?
techjunkieza said:
Thanks dude. I was wondering how it is done. I did not know that flashing a stock kernel will make the recovery mode default as well. I'm new to Android so please forgive the noob questions.
Click to expand...
Click to collapse
He, I had to learn all this myself recently, the SGS2 is my first Android device as well
For the SGS2 the recovery mode is part of the main kernel (partition), so flashing a stock kernel replaces that as well.
AFAIK this a unique Samy thing, on the other Android devices the recovery actually resides on its own partition.
techjunkieza said:
Surely there should be a list of files in a thread somewhere which indicates which files are modified when rooting the phone?
So I take it by restoring the original ROM, flashing a stock kernel (if you have a custom recovery mode or root access), removing the files and symlinks and resetting the ROM counter that the phone will be "stock" again?
Click to expand...
Click to collapse
Depending on how you rooted it's just /system/xbin/su that gets replaced and /system/xbin/busybox that gets added.
Then all the symlinks busybox installs - not sure if busybox has an "uninstall" option to remove them, if not just dump all symlinks in /system/xbin, on stock FWs there are none in this dir.
HellcatDroid said:
He, I had to learn all this myself recently, the SGS2 is my first Android device as well
For the SGS2 the recovery mode is part of the main kernel (partition), so flashing a stock kernel replaces that as well.
AFAIK this a unique Samy thing, on the other Android devices the recovery actually resides on its own partition.
Click to expand...
Click to collapse
Thanks a lot for the advice. I see many people asking the same questions but no one really gives them answers. I'm guessing it's betterfor it to be on two different partitions in terms of coupling. For noobs, the Samsung way is easier.
HellcatDroid said:
Depending on how you rooted it's just /system/xbin/su that gets replaced and /system/xbin/busybox that gets added.
Then all the symlinks busybox installs - not sure if busybox has an "uninstall" option to remove them, if not just dump all symlinks in /system/xbin, on stock FWs there are none in this dir.
Click to expand...
Click to collapse
Great. Thanks. I would like to know what Android does on a low level in order to gain root access. I'm going to research that a bit.
Thanks very much for the info!
techjunkieza said:
I would like to know what Android does on a low level in order to gain root access. I'm going to research that a bit.
Click to expand...
Click to collapse
Well, once one knows what happens it's not that much magic that happens.
Basically, the stock su gets replaced with a custom one that actually has a way of allowing other user (IDs) to run as root, Superuser.apk is installed to maintain su's database of allowed (and disallowed) user IDs and last not least busybox is installed to gain some shell commands not available (or limited) on stock.
All that is done via an adb daemon (already) running with root perms - that's what the insecure kernels do, they simply let the adbd run with root perms (so the above things can be done).
Each app running has it's unique, own user ID it's running with, so root access/permissions can easiely be maintained that way.
I hope that was what you wanted to know
HellcatDroid said:
Well, once one knows what happens it's not that much magic that happens.
Basically, the stock su gets replaced with a custom one that actually has a way of allowing other user (IDs) to run as root, Superuser.apk is installed to maintain su's database of allowed (and disallowed) user IDs and last not least busybox is installed to gain some shell commands not available (or limited) on stock.
All that is done via an adb daemon (already) running with root perms - that's what the insecure kernels do, they simply let the adbd run with root perms (so the above things can be done).
Each app running has it's unique, own user ID it's running with, so root access/permissions can easiely be maintained that way.
I hope that was what you wanted to know
Click to expand...
Click to collapse
Basically, yes! You definitely deserve a thanks for all of this. I was looking for information of what you just described but couldn't find anything. Shot dude!
how to reset counter without the USB jig ?
You don't.
Best you can do is getting rid of the triangle by flashing a stock kernel, but to reset the counter you really need the USB jig.
Great post! I cannot find a clear answer to these questions as well:
1. What is the location of the so called "boot loader" and how to make a backup? On Intel architecture it's on the first few sectors of the disk block device.
2. What is the location of the "ODIN mode/Download mode" application and how to make a backup? I suspect it may be in some read only memory and there is nothing to backup?
3. What is the location of the partition table? How to backup?
I want to understand the real/core/linux/android way of doing these, not just blindly running arbitrary tools.
Thanks in advance.
HellcatDroid said:
You don't.
Best you can do is getting rid of the triangle by flashing a stock kernel, but to reset the counter you really need the USB jig.
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=1494114
I already did it on my SII running ICS 4.0.3, worked great!..., but..., read the thread and cross your fingers...
gingingingin said:
1. What is the location of the so called "boot loader" and how to make a backup? On Intel architecture it's on the first few sectors of the disk block device.
2. What is the location of the "ODIN mode/Download mode" application and how to make a backup? I suspect it may be in some read only memory and there is nothing to backup?
3. What is the location of the partition table? How to backup?
Click to expand...
Click to collapse
1, 2 and 3: they are outside of the normal partitioned space / on hidden partiions (the bootloader partition is visible in ICS though) and you should not touch them.
Backing them up is useless as when the bootloaders are corrupted/broken, you'll have no way to restore them anyways as no bootloader == no boot to run anything, hence no restoring.
One is advised to leave them alone and not touch them - usually you can't access them anyways.
2: "Download Mode" is part of the secondary bootloader (partitions /dev/block/mmcblk0p2 and mmcblk0p3).
Hence the inability to access Download Mode when the bootloaders are broken.
Does it mean that "Download Mode" can be corrupt by overwriting this secondary bootloader? What about the the primary one? Is this a sure way for "hard bricking"? I was always wondering is there a way to completely lock yourself out of SGS2, but could not get a conclusive answer in the forum. Or you can recover from any failure by having any single piece backed up?
What do update packages mean when they contain a bootloader update - is it primary or secondary bootloader, or both?
You didn't say about the location of the partition table, although it's quite often part of the updates to have a PIT file with a new layout?
And last but not least, what is the basic sequence to recover from a partition based raw backup, like the one we're discussing in the thread?
Regards,
Anton
Hi everyone. I've just rooted my galaxy s 2, running on gingerbread XWKE8. I'm planning to install a new rom.have heard about various rom available.
1. Is villain 2.0 rom okay? The main purpose for installing a custom rom for me is to save battery as I'm outdoor most of the time. as of now my gingerbread is working well except for this battery issue. Is it worth changing the rom?
2.Was reading about titanium backup
I've done back up of my custom apps + system data on phone' s external sd card. I don't have paid version of titanium. Can't buy it either. (no credit card).anyway, shall i be get nandroid backup too, just in case? when i install new rom n use TB for restore, since it*
Has system data as well, won't it overwrite the old data on the new rom? it sounds un believable coz it thwarts the whole purpose of installing a new rom. So will there be an option of ticking individual files to restore as per my choice? (no pro version of . titanium). If so, how do i know which one to be restored?
3. If clockworkmode has a back up option why do we need a titanium backup? cos it gives a nandroid type backup?
4. Can clockworkmode be used to upgrade to a new firmware (custom our stock) or odin should be used as in rooting with a little modification (depending on if firmware has one file or 3 files)?
Please enlighten.
Thank you very much
Sent from my GT-I9100 using XDA App
1) See for yourself if it's worth it.
2) Yes do a nandroid and check this before changing rom.
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
4) Depends on how the files are provided. Both should be possible.
For a credit card alternative I use this.
Hi.thanks a lot for replying. How do I get nandroid backup? Do I've to use rom manager in order to do nandroid backup? Cos when I search for nandroid in market, it doesn't return any nandroid app as such.
Sent from my GT-I9100 using XDA App
No boot in to recovery, go to backup and restore and backup.
TheGhost1233 said:
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
Click to expand...
Click to collapse
So if I happen to dislike or have problems with a custom rom, I just restore the backup of my rooted stock rom and all is back to the way it was (all, data/boot/apps/settings ...)? I think it will be, but I just want to be sure.
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
dav pahwa said:
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
EFS post in Dev section probably .
jje
I already linked to the right thread, in the thread there are different commands. All you have to do is pick a method, create the efs folder, copy the command to the terminal emulator and hit enter.
Sent from my Transformer TF101 using XDA Premium App
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Default [REF] Backup /efs folder. IMPORTANT.
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.
Hi theghost & thanks for replying. Yes, i had read that link . But being a starter in androids, i had some doubts n thought if someone else knows a more simplified thread. Eventually i followed the same thread only.
As the author said, there r two methods - clean & raw n he advises to use both. when u used raw , in the end comes- no such file directory exists. When i checked my files->sdcard , i could see efs folder n some files inside it (which wasn`t happening even with astro file manger) I copied the efs folder N pasted it into Externalsd folder (default Ext. sd card folder ?)
R my efs folder files safe now ?
Is there any other precaution to be taken , any files to be saved before i embark on installing New villain rom 2.0 as per instructions given here http://forum.xda-developers.com/showthread.php?t=1081368 .
Strangely efs folder saving point isn`t mentioned here , even though its so important. (But then may be its very basic) Is there any other basic that i should know ?
Thanks a lot again.
with regards.
Create the efs folder with astro, then use the raw method and copy the .img to your pc.
Sent from my Transformer TF101 using XDA Premium App
How n where to create ef folder using astro? When i click on app
The home page shows
(folder icon)/mnt
(Home icon)(search icon) etc.
Folder-ifs
Asec
Obb
Sdcard
Secure
Usb
On this home page I should crate folder-efs ?
Sent from my GT-I9100 using XDA App
No in sdcard
Sent from my GT-I9100 using XDA Premium App
But sdcard already has efs folder with some files in it . This was created when I used the emulator. But the RAW step had failed as I told u earlier.
Sent from my GT-I9100 using XDA App
nikzDHD said:
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Click to expand...
Click to collapse
Thanks mate. I'm backing up only custom apps, not custom apps.
Sent from my GT-I9100 using XDA App
Mist that you already had the efs folder. If you already have something there your probably good. If you still want the raw method to work make sure you type su first and hit enter and than exactly copy the cat command (ChromeToPhone is great for this) it should work.
Didn't work out mate .
Sent from my GT-I9100 using XDA App
I'm comfortable with it. Thanks for yo support mate
Sent from my GT-I9100 using XDA App
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.
I got an EFS.tar backup
I got Odin
I got Heimdall
I got YP-G1 stock.tar.md5
I just don't know how put it all together.
Back on GB roms, I would just wipe everything via CWM, use Odin to flash stock, and then wipe once again.
But this is ICS. Surely it's different, right?
I wrote out instructions in either the LinICS or the Nebula thread (I can't remember it was several weeks ago), also the files are in the Restore to stock thread from Zaclimon. you gonna have some issues in that your efs backup is an efs.tar instead of an efs.rfs
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
theplasmastorm said:
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
Click to expand...
Click to collapse
IT DOESN'T, when you go to LinICS or any of the CM9 ROMs your player is converted from RFS partitions to MTD ones and you HAVE TO use HEIMDALL with a PIT file to reparttion the player back to RFS as you flash the stock ROM.
Totally lost on what to do. I don't know where to begin or anything. I need someone to hold my hand step by step like a baby.
I've read the recovery thread and did some searches around the place, but I don't really understand a thing. I have a US YP-G1
Alright after some fiddling around I got back to stock but the usual blank efs issues are there. I still don't understand how to restore my efs.tar. Could someone help me please?
I also can't mount efs and have no idea what to do with the blankefs.img in the recovery thread
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
theplasmastorm said:
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
Click to expand...
Click to collapse
Did you have content on your efs.tar?
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
one thing that works, atleast the method I used to solve it, once you've copied the contents back into the EFS folder on the player, then flash the Dream Ultra ROM from CWM, then after booting the ROM up shutdown and wipe data/factory reset, then use Odin to flash the stock GB.tar through odin.
Roms at these links.
http://forum.xda-developers.com/showthread.php?t=1719685&highlight=dream+ultra
http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0
Oh snap that worked. Aroma installer to the rescue.
theplasmastorm said:
Oh snap that worked. Aroma installer to the rescue.
Click to expand...
Click to collapse
Now make a a proper EFS.rfs backup using the method described here http://forum.xda-developers.com/showthread.php?t=1632376&highlight=efs+backup that way next time you need to revert back from an ICS ROM you can flash the efs.rfs to the efs section instead of the blankefs.img and not have to go through this again.
FYI the method listed can be done on the player using terminal emulator just go into it and type su to gain superuser then type the the part for making an efs backup and your done, then copy that file to your PC.
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
theplasmastorm said:
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
Click to expand...
Click to collapse
Sorry, it was in my older videos that I did, forgot to mention it in that one, guess I'm not the only one to goof up if it's not in the OP either.
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
Whenever I try to do these steps before flashing dream ultra rom it tells me "tar not found" I have a efs.tar on my sd card for certain.
I had backed up my EFS in my Galaxy S3 just recently I just want to verify everything is OK. How to do it? Don’t say me to use something like ktool from Play Store and backup & verify from the app. That was the first I tried for the backup process. But it didn't work totally. Now I had backed up EFS with EFS Pro tool by ‘lyriquidperfection’. Again the latest version that was posted on the thread itself didn't work for me. I just used an old version and everything is done. Please just say me how to verify it. This is a serious issue BTW.
Thanks
Forget these tools! Install TWRP-recovery and backup your system including efs-partition or only efs. And trust it and do nothing more.
Alternative: make a backup-archive of efs with BusyBox and TerminalEmulator. This archive's integrity you can check. Very basic & simple.
if with Terminal Emulator
rp158 said:
Forget these tools! Install TWRP-recovery and backup your system including efs-partition or only efs. And trust it and do nothing more.
Alternative: make a backup-archive of efs with BusyBox and TerminalEmulator. This archive's integrity you can check. Very basic & simple.
Click to expand...
Click to collapse
Is this the command for backing up efs partition in Terminal Emulator "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096"?
1. What does this "bs=4096" indicate?
2. How to check the integrity then?
Thanks for the help
I didn't use the image, but the archive.
Create: tar -zcvf /sdcard/efs-backup.tar.gz /efs
Validate: tar -tvf /sdcard/efs-backup.tar.gz
Restore: tar -zxvf /sdcard/efs-backup.tar.gz -C /
You may safely restore instead of / to /sdcard/test and compare /efs and test with diff-command.