• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[WARNING] Back up your /efs folder

Rudedawg

Rudedawg

Android Expert
Ok those that have rooted and those that would be rooters, listen up.
Most guides you'll read will not mention anything about this but for the love of god do it because should the unthinkable happen then you'll have an option other than having to send your handset humbly off to Samsung for repair.

BACK THE HECK UP EVERYTHING!!!!

And by everything I mean everything and in my case the /efs folder.

For my problem see: http://androidforums.com/galaxy-s2-international-all-things-root/430934-unknown-baseband.html


PLEASE read the following post and take note.

[WARNING!] Backup your /efs folder before you flash - xda-developers


Also install this app: https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en


My Samsung Galaxy S2 became one step better than bricked but still effectively an expensive media player with no phone capabilities.

To a few this may be old news but to many more this may save a few handsets. My new handset arrives tomorrow as I was still under warranty and was able to flash the carrier firmware. Not everyone may be that lucky?

RD
 
Unlucky mate.
At least you have a replacement being sent, putting to bed any of the "rooting invalidates your warranty" debate. (effectively it does, but seemingly it depends on who it gets sent back to, so its a bit of a lottery I guess)

Next time, install Siyah kernel, as this automatically backs up your EFS folder
 
hawker said:
Unlucky mate.
At least you have a replacement being sent, putting to bed any of the "rooting invalidates your warranty" debate. (effectively it does, but seemingly it depends on who it gets sent back to, so its a bit of a lottery I guess)

Next time, install Siyah kernel, as this automatically backs up your EFS folder
Click to expand...

Nice tip


As for the warranty void issue , well yes your right but It take alot of playing dumb on the phone. Going through every little step on their poxy diagnostic tick sheet. I had reflashed the orange firmware which would leave no obvious trace I'd diddled with the phone just incase. But no , no questions or queries about me flashing the phone ever came up.

Thanks Orange.
 
steslatt said:
How did you manage to "semi" brick it?
Click to expand...


I was getting a repeated force close when trying to add contacts. My address book would not load. I was running Villain 2.3 still. Everything else was fine so hesitated updating the firmware. To try rectifying the problem I restored the phone to a restore point a couple months ago. The error remained so I restored back to an even earlier point. Upon doing so it caused even more grief and put me in the position i'm now in.
 
I tried Rom Manager yes but my back ups were all created via CWM. I had tried flashing via Rom manager. Ive read lots about problems with that program. So never again.
 
I was wondering if it was that what caused the problem in the first place? Or did you already have the problem before you tried rom manager?
 
steslatt said:
I was wondering if it was that what caused the problem in the first place? Or did you already have the problem before you tried rom manager?
Click to expand...


You know what I wouldn't be surprised. I had tried to flash 3 different updates and a Modem through Rom Manager. All 3 times it took me into the download mode and failed to flash. It is certainly top of my suspect list.
Some people say it works but for me...no i wont be using it again.

This wasn't noticed until after installing the program no. Like I said it all started when I tried adding a new contact to my phone book. Resulting in repeat force closes. :(

A real pain in the ass. I'm not afraid to reroot the new phone when it arrives but you can be darn certain ill be taking a few extra security steps this time round. :)
 
Ive always stayed clear of rom manager, too many horror stories. Stick to just using CWM.
Also I think this thread should be stickied so more users are made aware of the problem.
 
steslatt said:
Ive always stayed clear of rom manager, too many horror stories. Stick to just using CWM.
Also I think this thread should be stickied so more users are made aware of the problem.
Click to expand...

I was easily fooled. Chainfire made it..must be legit right? Looked like CWM became Rom manager....Wrong! Massive mistake .
 
ROM Manager is not the problem - Samsung's recovery implementation is. That's why Chainfire had to modify Koush's ROM Manager code for the GS2 - compatibility with other devices is proving well-nigh impossible.

ROM Manager and CWM Manager are simply front-ends to CWM Recovery, so backups are fine. So long as you perform backup/restore functions from CWM you're golden; ROM Manager can still be used to rename/delete backups, d/l ROMs, kernels, modems etc but DON'T use it to install anything - boot to recovery and do it from there.

Note: CWM Recovery 5.0.x.x should be more compatible. I haven't had a chance to test ROM Manager with it yet but I will soon.

p.s. Agreed 100% that this need to be added to the Guide. It's becoming more of an issue now that CM7 has been released. I'll add something when I get more time this evening.
 
I was wondering, just how is this efs folder restored if a backup has been made and it all goes fubar?

Siyah makes a .tar and .img backup of this, and the only instructions I've come across to restore a backed up efs folder uses adb, and as far as I know, this requires installing an android SDK.
Is there an easier way to do this? Seems pretty long winded and complex to me.

I'm assuming it cant be as straight forward as a copy+paste of the folder using root explorer?
 
Slug said:
Note: CWM Recovery 5.0.x.x should be more compatible. I haven't had a chance to test ROM Manager with it yet but I will soon
Click to expand...

It's not! I tried booting into CWM Recovery 5.0.2.6 from ROM Manager and stuck at the yellow triangle. Normal boot just loops.... reflashed kernel and stock ROM.... same result. Bugger! :-(
 
This is not good and is one of the main reasons I'm off the Siyah kernel at the moment and back onto nimph 2.1.3
 
Rudedawg said:
Ok those that have rooted and those that would be rooters, listen up.
Most guides you'll read will not mention anything about this but for the love of god do it because should the unthinkable happen then you'll have an option other than having to send your handset humbly off to Samsung for repair.

BACK THE HECK UP EVERYTHING!!!!

And by everything I mean everything and in my case the /efs folder.

For my problem see: http://androidforums.com/galaxy-s2-international-all-things-root/430934-unknown-baseband.html


PLEASE read the following post and take note.

[WARNING!] Backup your /efs folder before you flash - xda-developers


Also install this app: https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en


My Samsung Galaxy S2 became one step better than bricked but still effectively an expensive media player with no phone capabilities.

To a few this may be old news but to many more this may save a few handsets. My new handset arrives tomorrow as I was still under warranty and was able to flash the carrier firmware. Not everyone may be that lucky?

RD
Click to expand...
Very courteous of you.Which method do you suggest for a quick and thorough back up of current system?I am running Villain.
 
hawker said:
This is not good
Click to expand...

Aye, tell me about it! Several unmentionable muscles did a lot of puckering but in the end a full wipe from stock and reflash of the appropriate CF-Root kernel got it back up and running.

and is one of the main reasons I'm off the Siyah kernel at the moment and back onto nimph 2.1.3
Click to expand...

The issue is with ROM Manager and the way Samsung configure the recovery in the GS2. CWM has no problem booting into recovery, and my backup made with CWMR 5.0.2.6 restored fine from 5.0.2.3. v4.0.0.2 won't touch it, reporting that the *.img files are 'not found'.

My current advice is not to use ROM Manager unless specifically required i.e. by CM7, and even then only use it with the CWMR it flashes.
 
You must log in or register to reply here.
Back
Top Bottom