Related
This Guide is for any user that has a Rom installed. This will back-up almost everything the user has put on the phone.
So, here are some things you need.
Heimdall One Click KB2 - http://forum.xda-developers.com/showthread.php?t=1266172 (thanks to AdamOutler)
1) First, make a nandroid backup.
2) Make an /efs backup (adb pull /efs) (also can use an app called nitrality available in market)
3) Now, you will need to Plug in your phone to the computer. Take ALL the folders on your SD card and copy them to your laptop. (Mine was user/android/sdcardbackup)
4) Remove Micro-sd card, and SIM card
5) Open up your dialer and dial this code *2767*3855# THIS WILL WIPE YOUR SD CARD and /DATA
6) Reboot the Phone
7) put your Phone in download mode, open heimdall One Click and insert the phone and make sure that heimdall recognizes it
8) Flash the new firmware Bootloaders not required
9) Have the Phone Boot up Completely (takes a long time)
10) Check to see if your /efs has been edited. Use this thread http://forum.xda-developers.com/showthread.php?t=881162 (and your efs backup) to get it back.
11) You might want to dial *2767*3855# Just in case if there is anything left.
12) You should be running KB2, have your SD cleared, and ready to be turned into samsung.
Post Questions and comments below!
i decided to save this one, no clue why, just wanted to feel important...
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
bigbooty said:
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
It isnt supposed to erase the /efs but ill include it, thanks!
sepherian said:
It isnt supposed to erase the /efs but ill include it, thanks!
Click to expand...
Click to collapse
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
When my cappy messed up, my imei got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs. Product code was different also. Flash enough roms and it can mess up something as someone might be a novice coder and mess your device up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: fixed Imei
Nucleartx said:
When my cappy messed up, my meid got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
meid? i think you mean imei?
bigbooty said:
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
Click to expand...
Click to collapse
Yes, I know. This Flash is not intended to mess with the /efs AT ALL, i have checked the package and it has no reference to /efs in the scripting. The post including the package also says this:
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Click to expand...
Click to collapse
So as you can see the number i have them call wipes the data and SD but they have their nandroid and SD backups. The number i have them call also doesnt touch the /efs. Trust me, I tested this method before i posted it and i didnt make an efs backup and my IMEI was perfectly fine afterward. I assume that nothing here messed with my /efs at all.
The only thing that would change the NVdata.bin would be an unlock tool. And i doubt that it even changes it.
OP was updated with more accurate steps.
What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA
1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium
Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium
Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA
I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.
Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.
you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?
EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!
Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null http://imageshack.us/photo/my-images/546/sc20120828223834.png/
http://imageshack.us/photo/my-images/266/sc20120828223733.png/
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dutchthomas said:
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I tried ics and ginger stock and nothing
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
kishke said:
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
Click to expand...
Click to collapse
I try this method and repair the lock screen that did not work but still not working imei imei null / null thank
That is REALLY BAD.... Not sure what to tell you... Heard someone else did that and they were screwed....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
If it's only IMEI number that's missing use the search, there was a thread a while back with someone having the same issue, he got told to edit some file and enter his IMEI from the phone's sticker.
aiyoros02 said:
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null
Click to expand...
Click to collapse
Exactly what rom framework did you flash?
cschmitt said:
Exactly what rom framework did you flash?
Click to expand...
Click to collapse
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
aiyoros02 said:
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
Click to expand...
Click to collapse
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
aiyoros02 said:
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
Click to expand...
Click to collapse
Sorry to say then, without a nandriod backup you're SOL.
cschmitt said:
Sorry to say then, without a nandriod backup you're SOL.
Click to expand...
Click to collapse
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
talk2sharn said:
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
Click to expand...
Click to collapse
Check out these threads, there are solutions but you got to pay up at least €10
http://forum.xda-developers.com/showthread.php?t=2288390
http://forum.xda-developers.com/showthread.php?t=2287136
how to use efs1.bin efs2.bin and efs3 bin to restore imei
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
bmyury said:
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
Click to expand...
Click to collapse
howto backup/restore efs
dont know if it will fix the imei though
Update 9/1/2012: A user has successfully restored with this method! Continue to "Testimonials" for more info!
Update 9/2/2012: TrevE has now come up with a way to leverage Samsung's built-in restore to your advantage! Read below for more!
Update 9/3/2012: Changed adb commands to reduce Operation not permitted problems.
Thanks to the efforts of some great developers, there is now *possibly* a more comprehensive method to backup your IMEI. While I have not personally tested a restore using this method, a user in IRC has done a manual NVRAM wipe and restored it using this method, without the roaming issues caused by a occasionally-bungled QPST restore or manual IMEI injection. In addition, posts in this thread indicate a successful restore from an actual occurrence of the problem, all without the use of QPST and also without any roaming issues!
Before I go any further, the same old disclaimer still applies; you accept all responsibility for what you do to your own device!
Theory:
The theory is that the S3 has, in the boot process, a routine which is "tripped" when it detects an error condition. This routine is designed to "save" your IMEI by restoring images from two built-in backup blocks. The problem is, it actually does the opposite; for whatever boneheaded reason, the default backup blocks contain dummy images with an IMEI of 0 and no carrier identification. This is why your phone forgets what carrier it's on and what its IMEI number is; the restore routine actually overwrites the phone's only copy of the IMEI data with a dummy. Because much more data is lost than just the IMEI, this is also why a QPST injection (not a QCN restore) persistently leaves you on roaming.
In an initial attempt to solve this problem, users have attempted to "dd", or create an image of, a single block supposedly containing the IMEI when the phone is still in a good state. This is the efs.sbn method that you may have seen. However, upon further inspection, it turns out the IMEI data is actually spread across five different block devices, hence why the efs.sbn method is either ineffective or leaves you on roaming! After the block devices were identified, a SynergyROM team member created an easy-to-use recovery zip that allows you to image these five blocks, allowing you to reflash them should the Samsung boot process overwrite your IMEI! Re-flashing these blocks after they've been crapped up virtually ensures your phone has been fully restored to its pre-IMEI-loss condition, thereby preventing roaming or data issues seen consistently with a manual injection, or intermittenly with a QPST restore. You do not need SynergyROM to use this tool; I've done it from full stock.
But wait: there's more. About a week after the development of this tool, several unused boot entry points were discovered that revealed a way to control Samsung's built-in "safety" feature and actually make it work properly! Two backup blocks were put in by Samsung themselves; "fsg" and "backup". The great news is that, although these images may contain dummies by default, you can instruct the bootloader to write your good NVRAM data to them so that the good data is what's written to NVRAM in the event of an error. That is, instead of restoring a dummy image over your good IMEI...it restores a good backup instead and you don't lose a thing! How awesome is that?
Developers are now recommending a new IMEI backup regimen, leveraging Samsung's built-in IMEI backup and SynergyROM's manual backup, together with an optional QCN backup you can do for good measure. Of course I can't make any guarantees, but doing this backup should leave you in such a good spot that almost nothing can total your IMEI or leave you in a roaming state. Here are the new instructions on how to backup your IMEI, iron-clad. Do Parts A and B, in order, C is optional but will give you added peace of mind.
Backup:
Part A (Samsung's built-in backup):
1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread.
If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.
2. For ADB: Connect your phone to the computer and ensure it is in "Debug Mode" (Settings->Developer Options->USB debugging). Then. in the command prompt, type the following:
Code:
adb reboot nvbackup
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
3. Your phone will reboot and copy the contents of two IMEI partitions to the two built-in backup blocks. You may see tiny blue text on the bootloader screen indicating that it is copying.
4. Allow it to finish and then reboot back into Android. The "fsg" and "backup" block devices now contain your IMEI information as they should have in the first place.
Part B (SynergyROM's "Plan B" manual backup):
1. Download the attachment at the bottom of this post. This is an update ZIP you can run right from recovery.
2. Reboot into recovery. On stock this can be done by turning off the phone and then turning it back on while holding UP and HOME.
3. CWM: Use VOL UP and VOL DOWN together with HOME to select "install zip from sdcard" then "choose zip from sdcard". Navigate to the folder you downloaded it to (most likely Download/). Select the zip you just downloaded to "flash".
TWRP: Touch "install" and navigate to the folder you downloaded the zip to (most likely Download/). Swipe to confirm flash.
4. Allow the backup to complete successfully. "Flash" is a bit of a misnomer; this is actually just a script that will safely backup your EFS and radio information to /sdcard/synergyrom/backup without touching your ROM at this point. When the script completes, reboot.
Part C: Backup with QPST:
Once the gold standard of IMEI backup, this method (in my opinion) should now be done only in the event of an unlikely complete catastrophe where neither Samsung's built-in restore nor SynergyROM's restore works. Simply follow the instructions here for extreme peace of mind; you don't need to do this if you don't want to, but I personally did.
Restore:
Do not do this unless your IMEI has been lost!
Performing Part A of the backup should ensure that you never lose your IMEI in the first place; the theory being that the Samsung built-in backup now has a good image to restore itself, as opposed to a dummy image. However, things may still happen. If you've still lost your IMEI, perform each of these methods in order of priority, "A" being the first.
Restore Plan A:
Run the following command from adb, just like when you backed up (have Android SDK installed, connect phone, and ensure USB debugging is enabled):
Code:
adb reboot nvrestore
This method triggers Samsung's built-in IMEI restore; except this time, you got good images on your side. Simply allow the phone to restore and reboot itself when completed. NEVER PERFORM THIS COMMAND WITHOUT DOING PART A OF "BACKUP" FIRST; THIS WOULD RESTORE THE DUMMY IMAGES INSTEAD AND WIPE YOUR IMEI!
Restore Plan B:
Sometimes a fluke happens and the nvrestore does not work. That's why this one is Plan B and not Plan A. Good thing you did Part B of "Backup"! Rather than instructing Samsung's bootloader to restore your NVRAM, this method will do so manually from recovery using a manually done backup.
It's just like when you backed up, except now you want to flash the zip containing your NVRAM info that the other zip built for you. This zip is located in /sdcard/synergyrom/backup. Simply navigate to this path and flash the zip beginning with "keybackup"; this will write images to 5 block devices from a time when your IMEI was all good. Reboot the phone; if all went well, you now have your IMEI back with no roaming!
Restore Plan C:
Both methods above may fail you in extremely unlikely circumstances. At this point, you'll need to try using QPST to get your IMEI back. If you did Part C in "Backup", you can follow instructions in that same thread to get you back up and running. In most QPST restores, you shouldn't have any issues with data or roaming.
Restore Plan D:
The planets have lined up, the Cubs have won the World Series, and all three above methods have failed you in what is surely a sign of the apocalypse. Far more likely, though, is that you didn't have a backup of anything and your IMEI is gone for good. The good news is that you can still get your phone working; the bad news is that you'll be stuck on roaming and may have problems with data. You'll need to perform an "IMEI injection" which is a kludgy last-resort restore method that manually writes the IMEI to NVRAM; the link I provided in Part C of "Backup" will tell you how to do it.
Testimonials:
This method has been tested good by the following users in this thread!
amaury48 said:
Just flashed CM10 09-01 nightly and lost data, confirmed I lost my IMEI. I had used the process in the OP a while ago to backup my IMEI. Just would like to confirm that I just flashed the backup it created and happy to report all is well again. Thanks for the post of this tool........saved my butt......
Click to expand...
Click to collapse
alee said:
I'll join the club. Lost my IMEI while doing the latest CM10 nightly. Restored and was back in action in no time.
Click to expand...
Click to collapse
Nght12 said:
Hey, used your backup method and ended up having to use it later in the day. It works. I'd reply but I can't yet due to being a new member here
Click to expand...
Click to collapse
Please continue to let everyone know if this restore has worked for you after an IMEI loss!
Happy flashing!
TrevE said:
The other trickery we ran into is partitions do not like to be written to for whatever reason outside of package_extract_file right outa the zip. dd'ing directly back failed over and over, I have no clue why, poor esc must have flashed 100 zips before I gave up looking into it. So the updater zip restore uses only package_extract_file, actually writing partitions out properly. I have high hopes that it will actually work, but until tested otherwise do as many types of backups as you can
Click to expand...
Click to collapse
Your restore dd commands won't work.
con247 said:
Your restore dd commands won't work.
Click to expand...
Click to collapse
Good catch. I'll revise the guide appropriately.
So will this work on any ROM?
Sent from my SCH-I535 using xda app-developers app
Yeah I'm on stock rom just rooted an cwm. Can I flash this zip an since I don't have synergy, where will the backup be stored?
Sent from my SCH-I535 using xda app-developers app
Worked on CM10.
I'm all for redundancy of backups, so here's hoping this method fully works when restoring. I have not experience a loss of IMEI myself, but I definitely want to be safe. I know the original efs backup method was proven to be an incomplete backup, but I thought the QPST NV backup method was proven to work? Are you saying that restoring with tthe QPST method (where you have an NV backup before you lose IMEO) does not work and will still having roaming issues?
At any rate, it will be interesting to see if this is the "one true backup" to rule them all for IMEI. So basically, you flash the zip in recovery and it creates another zip with the backed up contents. And in the event of an IMEI loss, you just flash the new zip and should be good to go? At least, that's the theory, right?
Travisimo said:
I'm all for redundancy of backups, so here's hoping this method fully works when restoring. I have not experience a loss of IMEI myself, but I definitely want to be safe. I know the original efs backup method was proven to be an incomplete backup, but I thought the QPST NV backup method was proven to work? Are you saying that restoring with tthe QPST method (where you have an NV backup before you lose IMEO) does not work and will still having roaming issues?
At any rate, it will be interesting to see if this is the "one true backup" to rule them all for IMEI. So basically, you flash the zip in recovery and it creates another zip with the backed up contents. And in the event of an IMEI loss, you just flash the new zip and should be good to go? At least, that's the theory, right?
Click to expand...
Click to collapse
You nailed it!
Nice, I'm assuming this is similar to what the Synergy ROM team is now including?
nyjumpman said:
Nice, I'm assuming this is similar to what the Synergy ROM team is now including?
Click to expand...
Click to collapse
Its the same. Just a standalone version.
Sent from my SCH-I535 using Tapatalk 2
Confirmed successful backup using CWM.
I can confirm this backup method works using CWM.
I first tried it with TWRP via Goo Manager and the script didn't execute properly.
I tried flashing the file while still in TWRP and I couldn't even find the zip file anywhere, user error I'm guessing.. lol.
So I flashed CWM over TWRP via ROM Manager PRO and flashed the zip file with CWM via ROM Manager PRO and the zip script executed nicely. I found the backed up zip file where the OP said it would be.
Here's to hoping I never have to use the backed up file, but it's good to know I have it there if needed.
Thanks again OP!
xCHPx said:
So will this work on any ROM?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This should work regardless of ROM as it is a recovery zip. I've tested it with CWM: I've never used TWRP so I don't know how well it would work in TWRP.
tu3218 said:
Yeah I'm on stock rom just rooted an cwm. Can I flash this zip an since I don't have synergy, where will the backup be stored?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've tested a backup successfully on full stock, rooted. The backup will be stored in a folder called "synergyrom" but this just the name the tool gives to the directory (as the tool was created by the Synergy team) and has no impact on function or dependency on SynergyROM.
Travisimo said:
I'm all for redundancy of backups, so here's hoping this method fully works when restoring. I have not experience a loss of IMEI myself, but I definitely want to be safe. I know the original efs backup method was proven to be an incomplete backup, but I thought the QPST NV backup method was proven to work? Are you saying that restoring with tthe QPST method (where you have an NV backup before you lose IMEO) does not work and will still having roaming issues?
Click to expand...
Click to collapse
QPST method is not perfect; it is better than a simple IMEI injection, but the boot bug writes crap over much more than just the IMEI. This is why either method may leave you on roaming (althogh a QPST restore only sporadically causes roaming). In addition, various DRM keys may be erased as well, leaving you potentially unable to play back HDCP/PlayReady titles; QPST does not restore these.
At any rate, it will be interesting to see if this is the "one true backup" to rule them all for IMEI. So basically, you flash the zip in recovery and it creates another zip with the backed up contents. And in the event of an IMEI loss, you just flash the new zip and should be good to go? At least, that's the theory, right?
Click to expand...
Click to collapse
That's correct. When you "flash" the backup zip, nothing actually is written to the ROM as far as I can tell; it runs just like a script/batch file and saves your backup zip to /sdcard/synergyrom. The tool itself creates a new flashable zip in this directory, one that does modify your unit, which you can then use only in the event that the bootloader craps up the NVRAM.
Just did this on cm10. Backed up without issue and I see the folder it created. Thank you. I've done qpst as well so now I feel very safe
Sent from my SCH-I535 using Tapatalk 2
hopesrequiem said:
Just did this on cm10. Backed up without issue and I see the folder it created. Thank you. I've doneSame. Thanks for the info.ll so now I feel very safe
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Same
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
So this requires an unlocked bootloader? I just did this but it skipped because my bootloader is still locked. Is that correct in that it needs to be unlocked for this backup process to work?
Sent from my SCH-I535 using xda app-developers app
Just did this, thanks!
I now have 3 different types of backups. I feel safe now if I ever lose it.
Safe-r, I should clarify.
Sent from my SCH-I535 using Tapatalk 2
Made my back up on unofficial cm10 0816. Thanks.
Sent from my SCH-I535 using xda premium
tu3218 said:
So this requires an unlocked bootloader? I just did this but it skipped because my bootloader is still locked. Is that correct in that it needs to be unlocked for this backup process to work?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There is no excuse to not be unlocked at this point.
Sent from my SCH-I535 using Tapatalk 2
tu3218 said:
So this requires an unlocked bootloader? I just did this but it skipped because my bootloader is still locked. Is that correct in that it needs to be unlocked for this backup process to work?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
lol ur still locked???
here. http://forum.xda-developers.com/showthread.php?t=1839791
enjoy bro. now you got no excuces
Stryker1297 said:
lol ur still locked???
here. http://forum.xda-developers.com/showthread.php?t=1839791
enjoy bro. now you got no excuces
Click to expand...
Click to collapse
i know i know lol I've been hesitant because of the IMEI issue and the phone is pretty damn good as is. But I'm slowly leaning towards flashing custom roms to get rid of the bloat, and since there are more ways now to hopefully restore the IMEI in case its deleted.
I've tried several methods to backup EFS and IMEI and none of them work. I've tried scripts through CWM, using the Infuse Toolbox, terminal reboot nvbackup, and using PC programs to send ADB commands to my phone.
All of these methods just create empty files without the backed up info.
The only messages I have seen are success messages, except one script told me that it failed because the EFS partition is locked.
Has anyone experienced this problem and has a solution?
Thanks.
My phone is not unlocked, this was my only though when I got that error message.
blastagator said:
I've tried several methods to backup EFS and IMEI and none of them work. I've tried scripts through CWM, using the Infuse Toolbox, terminal reboot nvbackup, and using PC programs to send ADB commands to my phone.
All of these methods just create empty files without the backed up info.
The only messages I have seen are success messages, except one script told me that it failed because the EFS partition is locked.
Has anyone experienced this problem and has a solution?
Thanks.
My phone is not unlocked, this was my only though when I got that error message.
Click to expand...
Click to collapse
is your phone rooted? try to root it before making efs backup
muzdai said:
is your phone rooted? try to root it before making efs backup
Click to expand...
Click to collapse
Yes it is rooted. I'm currently running the newest SlimBean.
blastagator said:
Yes it is rooted. I'm currently running the newest SlimBean.
Click to expand...
Click to collapse
the efs script i wrote and zen tool kit efs backup was meant to be used on froyo or gb - on samsung file partitions
the efs on cm7,9,10,10+ has been moved to a different partition
if you can see your efs on jb, use a root tool and make your own back up (root explorer is a good tool for this)
Ah so just copy /efs to a backup spot? I'll have to look in to how to restore that to GB if I ever bork my phone.
Thanks!
blastagator said:
Ah so just copy /efs to a backup spot? I'll have to look in to how to restore that to GB if I ever bork my phone.
Thanks!
Click to expand...
Click to collapse
that would work..after you do it, check the files in that folder to make sure it has appropriate files and sizes.
you can also long press the /efs folder using Root Explorer and it will give you an option to make a back up in a tar format too.
review the script thread i made..it shouldn't take long
save multiple copies
the sure fire way, if you ever get a chance is to have a copy of it while in rooted stock gb or froyo
My only problem is on download mode, the device on device manager is unknown.
I tried to installing and reinstalling Kies but it didnt work.
Any suggestions is appreciated.
villain_allain said:
My only problem is on download mode, the device on device manager is unknown.
I tried to installing and reinstalling Kies but it didnt work.
Any suggestions is appreciated.
Click to expand...
Click to collapse
I have this same problem, infuse appears on the computer as an unknown device... tried different cables, ports, and removing and re-installing drivers... all sorts of combinations to no avail...