Database Info

Need help, disparate

I bought captivate from ebay, the phone came rooted.
I installed few applications to unlock the phone, tried to use PC .bat files to extract the code, no luck, I was getting no code at all or FFFFFF.
Later I found out that in my main sd directory i have a 40mb nv data with FFFFFF.
I am not sure if this was generated as a backup .bak file from efs folder, so I went and installed terminol and tried accessing the efs folder, no luck, but I can access other folders. if i access efs it says premission denied, but using app android mate i am able to browse efs folder but it shows 0 files. other folders are ok.
My question is, after 2 days of headache, what should I do now, I have been searching all day long for answers.
Also if i run .bat files from PC while device connected, sometimes i also get permission denied message.
I'ts possible this phone was flashed before because I get the FFFFF from nv data?
plz help.
ok i was able to copy via emulator using this line
busybox cp /efs/nv_data.bin /sdcard
to sdcard and the file was 2mb in size, i have another .bak file 40mb in size, so, is this some kind of an application did this to the phone?
The phone is
2.1 update 1
i897ucjf6
kernel 2.6.29
eclair
i also have md5 file copied to sd is 1kb file.

I would say the phone definitely was flashed. With android mate did you allow for hidden files or something like that. I use root explorer.
Can you make and receive calls?
Miui

First of all, you don't seem like you know what you're doing, so back up /efs in its entirety to the sd card, then again to your computer before you do anything else and break something.
Secondly, if you're on 2.2 (which I assume you are), there is a thread that tells you how to do a carrier unlock with step by step instructions. Search for 'carrier unlock' and it should be on the first page of results.

nothing like hidden files or anything, i'll try but i get accessed already with emulator
i have a backup of most of the efs content, that's 2 files or so, i will try to search for additional files. I think one of the apps did a .bak file to the nav_data and saved it in the sdcard folder.
i'm on 2.1 i assume it was flashed forwards and backwards because the nv data is 40mb but has FFFFFF in it.
what do you think?
I saw this thread http://forum.xda-developers.com/showthread.php?p=8182729#post8182729
i think my last resort. I'll try to search for the thread you specified but im running 2.1.
p.s no luck on hidden files i cant find that setting.
p.s i bought this phone on ebay cant make calls until i unlock it for my sim. but i do have wireless connection.
p.s my kies keeps saying "connecting" to the phone, but that's i guess a different problem, i run drivers and kies full from samsung site.
nv.log shows
Fri Nov 5 14:00:33 2010: secondary NV built.
Fri Nov 5 14:00:39 2010: Plain text NCK deleted.
Thu Feb 17 10:42:30 2011: NV data back-up begin.
Thu Feb 17 10:42:31 2011: NV data back-uped.

anybody99 said:
nothing like hidden files or anything, i'll try but i get accessed already with emulator
i have a backup of most of the efs content, that's 2 files or so, i will try to search for additional files. I think one of the apps did a .bak file to the nav_data and saved it in the sdcard folder.
i'm on 2.1 i assume it was flashed forwards and backwards because the nv data is 40mb but has FFFFFF in it.
what do you think?
I saw this thread http://forum.xda-developers.com/showthread.php?p=8182729#post8182729
i think my last resort. I'll try to search for the thread you specified but im running 2.1.
p.s no luck on hidden files i cant find that setting.
p.s i bought this phone on ebay cant make calls until i unlock it for my sim. but i do have wireless connection.
p.s my kies keeps saying "connecting" to the phone, but that's i guess a different problem, i run drivers and kies full from samsung site.
nv.log shows
Fri Nov 5 14:00:33 2010: secondary NV built.
Fri Nov 5 14:00:39 2010: Plain text NCK deleted.
Thu Feb 17 10:42:30 2011: NV data back-up begin.
Thu Feb 17 10:42:31 2011: NV data back-uped.
Click to expand...
Click to collapse
*#7465625# <- Dial that number. Does it say 'off' for everything? If it does, you already have an unlocked phone.
If you're on 2.1, you might as well try the SGS Unlock tool from the market in the off chance that it WASN'T flashed forward and back to 2.1. If it was, there isn't really a reason to stay on 2.1. You might as well flash to some 2.2 rom and follow this procedure I mentioned earlier:
http://forum.xda-developers.com/showthread.php?t=831569&highlight=carrier+unlock

it says network lock is ON.
i tried the market app tools, 2-3 tools, doesn't work. they doesn't work because i have extracted nv data and the code is FFFFFF. now i don't know if it was flashed forwards and backwards, i'm just assuming.
rom 2.1 or 2.2 means the version software? can i update to 2.3? what's the best way to update it?
also i have 2 bin/bak files, 1 is 2mb and 1 is 40mb, which one should i use with the thread you specified?
in efs folder i had nv data bin as 2mb and in sdcard i had nv data bak 40mb
nv data bak file created just yesterday i think as the date says 29march.
his Step 1: Install / Verify that you have a v2.1 ROM or v2.2 ROM installed.
does it mean i can use it on my 2.1 as well?

I have no idea why one of yours is 40mb, but it sounds messed up. Both nv_data.bin and .nv_data.bak are supposed to be 2mb. You can use either, as they're supposed to be the exact same file. There shouldn't be any files in /efs that are 40mb.
You're all over the place. You really need to spend a day or two reading the forums; especially the stickied threads about how to flash a new rom.
And yes, it means you can use that procedure on a 2.1 rom.

it was nv_data.bak inside sdcard folder, not efs.
but anyway, i think i got it. in that thread you specified some people said there's an helroz app does the same thing, unlocking without using a code, so i used it and it worked, network lock is now off and it catches orange provider.
i think the only thing left is to root it to a new version.

I would flash back to stock 2.1 using Odin and do a Master Clear. Then root phone again and and install CWM. After that flash a custom rom.

Have you tried the app Galaxy S Unlock from the app store, worked well for me.

Fixed problem.
Got the phone from ebay was locked, was unable to unlock with most market apps, but helroz app got it unlocked the same way his thread specifies, by replacing the FFFFFFF. my nv data file was bad but imie code was ok. i got it unlocked, then flashed to stock + master clear with odin, then i got unregistered error with kies mini program, the nv_data created by the helroz app wasnt so good and had bad product code, followed the thread at http://forum.xda-developers.com/showthread.php?t=881162 to fix the file, replaced old file, first rooted, then used emulator and busybox with cmd only.
got a good product code, then did once again a master clear, then upgraded to 2.2 via kies mini, got a fresh version and a clear phone.
i spent 3 days on that averaging 10 hours a day. madness.

[HOWTO]Comprehensive IMEI/EFS Backup

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.

Restore backup from other Nexus 5?

I received my Nexus 5 a week ago, and after setting it all up how I like it, I noticed dead pixels. I ordered a replacement which has arrived today. and I'm wondering if I can make a TWRP backup on my old phone, and then restore it on the new one? Both have the same SKU number - LG-D821.AAU3WH.

iPWNtehNOOB said:
I received my Nexus 5 a week ago, and after setting it all up how I like it, I noticed dead pixels. I ordered a replacement which has arrived today. and I'm wondering if I can make a TWRP backup on my old phone, and then restore it on the new one? Both have the same SKU number - LG-D821.AAU3WH.
Click to expand...
Click to collapse
Yes but DO NOT BACKUP OR RESTORE EFS!!!!!!

Absolutely. The trick to this is to make a quick backup on the new phone (backup cache, or something small) so that it creates a folder with your new device's serial number. TWRP looks in /sdcard/TWRP/BACKUPS/<DEVICE's SERIAL NUMBER>/ to find backups.
So, once TWRP has created a folder for the new device's serial number, you can transfer over the backup files from the previous device. You'll need to ADB PULL the directory to a computer from the old device, then PUSH them back to the new one.
It works like a charm. My wife dropped her first N5 during a walk in a park and shattered the screen -- when her new one came, we made it a perfect "clone" of the first this way.
Good luck!

rootSU said:
Yes but DO NOT BACKUP OR RESTORE EFS!!!!!!
Click to expand...
Click to collapse
bcgaynor82 said:
Absolutely. The trick to this is to make a quick backup on the new phone (backup cache, or something small) so that it creates a folder with your new device's serial number. TWRP looks in /sdcard/TWRP/BACKUPS/<DEVICE's SERIAL NUMBER>/ to find backups.
So, once TWRP has created a folder for the new device's serial number, you can transfer over the backup files from the previous device. You'll need to ADB PULL the directory to a computer from the old device, then PUSH them back to the new one.
It works like a charm. My wife dropped her first N5 during a walk in a park and shattered the screen -- when her new one came, we made it a perfect "clone" of the first this way.
Good luck!
Click to expand...
Click to collapse
Excellent, thanks gents! So backup and restore EVERYTHING but EFS, or just Data?

iPWNtehNOOB said:
Excellent, thanks gents! So backup and restore EVERYTHING but EFS, or just Data?
Click to expand...
Click to collapse
You'll need to restore /system and /data if you want it exactly the same. I do not know what modifications / differences between the /system on your old and new phone are, so if in doubt, do both.

You should also do a backup of the EFS partition of the new phone since it's fresh, and keep it in a handy place. You never know when you might need it.

Further information from Dees_troy.

isn't EFS something samsung specific? can't find it on my N4

prulleman said:
isn't EFS something samsung specific? can't find it on my N4
Click to expand...
Click to collapse
Nope. Here is a thread for N5.

Primokorn said:
Nope. Here is a thread for N5.
Click to expand...
Click to collapse
ok thanks didn't know that. good info awaiting my N5

prulleman said:
ok thanks didn't know that. good info awaiting my N5
Click to expand...
Click to collapse
One of the first things you should do after root
TWRP has also a built-in feature as you may know.

prulleman said:
isn't EFS something samsung specific? can't find it on my N4
Click to expand...
Click to collapse
They all have efs but only some phones implement it as a dedicated partition or mounted filesystem.
Sent from my Nexus 5 using Tapatalk

Nandroid backup flash to new tablet?

So I've been using and modding android devices for quite some time now, but I'm never actually tried this so maybe someone can answer this question...
I should be receiving my new shield tablet soon (from the recall program) and I'm wondering if it would be possible for me to create a nandroid backup of my old tablet and then restore that backup on the new tablet? .... Can you transfer a nandroid backup from one device to another as long as both devices are the same make/model?

Im going to do that, actually. Theorethically, you should be able to.
Enviado desde mi SHIELD Tablet mediante Tapatalk

NaminatoR1254jaime.sier said:
Im going to do that, actually. Theorethically, you should be able to.
Enviado desde mi SHIELD Tablet mediante Tapatalk
Click to expand...
Click to collapse
That's what I was thinking... However, from what I understand, a nandroid backup is about the most complete backup you can create. It copies everything from what I understand.
If that's the case, and seeing as how you can change your serial number and imei number with certain apps (I.e. those numbers are in the software) then I wonder if you would end up with two tablets with identical serial numbers?! I could be wrong, it might not copy that info, but if it did that would NOT be good since the serial number is what nvidia uses to remotely kill your old tablet (I think)!!

bluegizmo83 said:
That's what I was thinking... However, from what I understand, a nandroid backup is about the most complete backup you can create. It copies everything from what I understand.
If that's the case, and seeing as how you can change your serial number and imei number with certain apps (I.e. those numbers are in the software) then I wonder if you would end up with two tablets with identical serial numbers?! I could be wrong, it might not copy that info, but if it did that would NOT be good since the serial number is what nvidia uses to remotely kill your old tablet (I think)!!
Click to expand...
Click to collapse
I dont think so, because that type ofmdata is un another partition
Plus, the serial number must come embedded in the hardware
Enviado desde mi SHIELD Tablet mediante Tapatalk

I think it would be better the other way around make a Nandroid copy of your new tablet and install it on old to avoid the kill switch..booomm

Ok, so flashing the TWRP nandroid backup from my old tablet onto my new tablet was NOT as easy as I thought it was going to be!
For anyone else trying this, you will notice that when you try to restore the backup (assume you had the backup on an sdcard, or copied it to the new tablet somehow), TWRP will not show any restore options! It turns out, the reason for this is that when TWRP makes a backup, it is locked to your device serial number.
To get around this, you need to rename a folder... Inside the TWRP/Backups/ there will be a folder name that is a long string of numbers/letters, THIS is the serial number of the device on which the backup was created (i.e. the old tablet). You need to rename this folder to match the serial number of your NEW tablet. The easiest way to do this is to created a small backup in TWRP from your NEW tablet, just backup the recovery partition or something small, your only doing this to create the folder name with your NEW tablet serial number. Now copy the serial number of your new tablet and use it to rename the old tablet backup folder, then load up TWRP and you should be able to flash the backup of your old tablet onto your new tablet!

bluegizmo83 said:
your only doing this to create the folder name with your NEW tablet serial number. Now copy the serial number of your new tablet and use it to rename the old tablet backup folder, then load up TWRP and you should be able to flash the backup of your old tablet onto your new tablet!
Click to expand...
Click to collapse
And possibly cause a software level change/update on your new tablet to the old s/n and potentially making it a target for the kill switch?
Sent from my SHIELD Tablet using XDA Free mobile app

An Droid said:
And possibly cause a software level change/update on your new tablet to the old s/n and potentially making it a target for the kill switch?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
No. Twrp and cwm backup do not copy those partitions of memory. I think the only reason for twrp naming folders like that is so people with microSD cards can create backs of multiple devices and the same chip and never accidentally restore the wrong backup

Clone 2 N5 Phones

So i broke the glass on my n5 but it's working ok, recently i manged to buy a cheap new white one, and basically have 2 working phones.
I want to transfer all my stuff from the old > new, i'm wondering, apart from the usual Titanium path, is there any google service or other method that will make a copy of my old phone on the new one?
What would be the best approach here, if Titanium, are there any shortcomings?
ty

Why not backup in TWRP (make sure NOT to backup EFS) and then restore (once again, WITHOUT EFS) on the other phone? Everything will be exactly the same.
Also make sure they're both on the same bootloader/baseband.

You forget the content of your /sdcard. Use adb pull/push to transfer your favorite folders/files to your new device.

Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone

invisibles said:
Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone
Click to expand...
Click to collapse
I did that,since I asked Google to replace my phone due to abattery charging problem. I installed same bootloader same radio same twrp version on both phones,backup all the "SD card" with a PC,and then made a nandroid backup. Now if you export the whole nandroid folder on the new phone ,you will not be able to install it because the folder name is related to the phone serial (if you look at the nandroid folder is named with many random charters). To solve this I created a nandroid backup on the new nexus 5 ,and renamed the backup of the old one with the name of the new one. This worked for me . I don t know if now you have to do the rename stuff no with last versions, but was like this 8 months ago (don't remember twrp version).
Don t backup efs partition and restore on the new one,it contains the imei and other stuff,and don't try to flash a 32gb nandroid backup on a 16gb model, I don't know if it will work

It worked, i also found out you can migrate stuff from the old nexus using google tap&go through nfc, don't know how much that restores..
Ty all for the help