Database Develop

[Q] (i9000)Deleted efs folder without backup!! Possible to restore?

Unlike other cases posted previously...
All files in efs were deleted, including all hidden .bak files
Now, kies displayed my phone have a product code of XXXXXXXXX and a fake IMEI...
Is it possible to restore the nv_data.bin and other files??
Please help! Thanks....

I have the same problem, is there a solution for that?? Please answer!

Did you install sgs toolbox and used it's check product code function before you deleted your efs? If yes, there is still a chance. If no, there are currently no public fix available yet.
Sent from my GT-I9000 using XDA App

We are on the same boat, as what francis posted. No public fix yet but pretty sure there will be.. its just a matter of time.

the same thing happened to me yesterday when i flashed Cyanogenmod 7, got fake imei but everything worked just fine (call, data, market).
today i deleted everything from efs folder using Root Explorer then installed i9000XWJS5 then, surprise, i got my original imei back.
do not know how and do not know if it will work on you but it worth a try

The same thing happened to me.
If I dial *#06# no imei appears.
In order to use the phone everytime I boot up I have to give r/w permission to system folder. Otherwise it doesn't recognize the sim card.
It seems to me that that the device is not anymore able to recognize itself.
If I try to install CM or other AOSP rom I have status 7 error.
In Rom manager I have a window where I should select wich kind of device it is.
In fastweb installer there is a list of devices and I have to choose wich of them I am using.
I know that there is nothing to do with warranty. But is it possible to go back to a stage where it is possible to install AOSP rom?
Thanks

don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...

Normallary Not

hellboy2703 said:
don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...
Click to expand...
Click to collapse
Thanks.
I have checked, but there is no backup.
I know the only one to blame it's me.
Do you think that there is anyway to make possible installing AOSP rom?

Watch out! That guy below me is spam! (User @yankee86)

restore nv-data.bin

So. my IMEI is jacked up. I made a copy of /efs when I got the phone but instead of making an archive I did a straight copy, Seems like the fat filesystem owned the permissions.
I am trying to restore from that backup but I am not having luck. People say you can just drop those files into place but it seems that they are replaced after every reboot. What do the permissions need to be? I see that ownership needs to be 1001:1001. Also, can I do this on JH7 with any success?

If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo

I used the CWM flashable zip to get back to JH7, didn't use odin (im not at home yet, and this was eating away at me at work, heh).
Ill flash back with odin and then see where that gets me. For my own sanitys sake, could you tell me what the permissions are on your files in /efs?

i have a fix that worked for me posted in the dev section

bames said:
i have a fix that worked for me posted in the dev section
Click to expand...
Click to collapse
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply

z28james said:
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
Click to expand...
Click to collapse
once in jf6 if your imei isn't corrected then delete everything but the nv_data.bin and .nv_data.bak.md5.
use android terminal emulator to execute following (must have busybox installed)
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot

avgjoegeek said:
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
Click to expand...
Click to collapse
fyi android id is different than the device id. Device ID = IMEI.

I see my problem, the efs directory I have is from my OLD captivate. Arrrg....I have no backup of my current /efs. The random nv_data.bin it creates has the correct product code already.
There must be something in the phone that knows the imei as this is why it was not accepting my dropped in files (the files from my old phone).
Ah well...ill use it till ATT blocks the test IMEI "lose" mine and go get a refurb as I have insurance.
FYI, the stock original firmware does not create those .bak files from what I could see. I bet your files had jacked product IDs but perhaps the part that went with your IMEI was still intact. This would be why my phone wont accept my old phones nv_data.bin?

once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.

bames said:
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
Click to expand...
Click to collapse
None of those files get generated for me or exist. If I remove everything, a generic nv_data.bin and .imei get created. Thats it. If I copy over the files from my old captivate, I believe they do get created but since the IMEI in that file does not match whatever is being checked in the phone, new files are created anyways.
I suppose nobody as of now knows how to generate the string that is in the nv_data.bin based on an IMEI so it seems that I am out of luck.
Perhaps some shady place in town can help me repair the IMEI or something

I ended up calling Samsung today. I described the problem (damaged IMEI) and they sent me a pre-paid shipping label to send it off to Plano TX to have them take a look (i'm in Austin).
I will let you guys know how this turns out.

My phone is on its way back to me. They ended up swapping the mainboard under warranty.
I suppose if you have a damaged IMEI and can deal with using an old phone for a week, consider sending it over to samsung.

did you have to pay for new mainboard? cause i got the same problem but i am not the orginal owner for the phone.

Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.

Phateless said:
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Click to expand...
Click to collapse
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text

z28james said:
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
Click to expand...
Click to collapse
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...

Phateless said:
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Click to expand...
Click to collapse
Well, the warranty period is a year and so since its been less than a year since the captivates release, you should be good. It would seem the only way it would be out of warranty would be if samsung for some reason deemed it to be at some point. Im sure you could call samsung with the IMEI and verify.
In my case, my product ID had become damaged. My problem is although I had a backup of /efs, it was for my first captivate, not my current. I deleted /efs and moved the backup into place. Seeing that it was the nv_data.bin for some other phone with another IMEI (the IMEI is encrypted inside that file) it instead replaced the files with a generic set of files and the dreaded test IMEI.
Since nobody had a good way to write the IMEI to that file as it expects, I was SOL.
If I could do it again, I would make a .99 cent jig (I did this using a wonderful thread here labeled something like "make a jig without cutting up USB cable) which gets you into download mode if odin or something soft bricks your phone, root, make a backup of /efs and then take a nandroid backup. I THINK I remember reading that sgstools can backup /efs for you but in the sticky there is a method on how to make a .tar of /efs (good as this will retain permissions/ownership as if you straight copy them to the sd card with fat32, the filesystem does not understand linux permissions and blows them away).

Master-Clear did the trick 4 me
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!

TommyZee said:
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
Click to expand...
Click to collapse
Do you know where I can find this ODIN3 one-click and how to do a master clear?

[Q] Things to do/save BEFORE flashing ROM

...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.

efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?

mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.

Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a

I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?

tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy

I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.

Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin

No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.

Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!

OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.

So... let's say that you didn't save your android id before you flashed... will that cause problems?

beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.

How to restore deleted (stock) System Apps?

Let me apologize first of all as I come from 5 years of using Windows Mobile knwoing what I am doing (cooking ROMs included) and now just got my Galaxy /Android a couple weeks ago and am blank at all of it.
After messing up with some system files and (useless) stock applications (like I removed stk.apk and other stuff) I decided to do a full hardware reset as the phone started getting random crashes.
But after the full reset things only got dramatically worse. I quickly realized all the missing system apps are still missing (I thought they'd be "restored") and basically nothing works, just crashes one after the next, cant use anything.
So, a hardware system reset on the galaxy, doesnt really reset anything except user installed apps and settings... amazing
Can someone please tell me (the idiot here, I know) how to do a real full restore where all system files, all missing files and positively everything gets back in the Tab as it was originally?
What a flippin' nightmare... Thanks in advance very much!

deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.

bartito said:
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
Click to expand...
Click to collapse
OK, first of all a big thanks for both file and info. Aside from the Stk.apk, the biggest thing that made me run into problems was trying to update my Contacts.apk:
http://forum.xda-developers.com/showthread.php?t=907399
things didnt work out for me and even after restoring the original files (Contacts.apk and Contacts.odex) nothing really worked again, reason for wich I tried a system reset.
Now, do I need to re-root the Tab or its still rooted, and can I perform the operations easily with Root Explorer like I did before? You mentioned to use adb and set permissions to 644 after push but, sorry again for the ignorance, I have no clue what adb is nor what/how to set permissions. Pathetic to be ignorant huh?
My last 2 questions are, where could I find the original Contacts.apk and Contacts.odex and if needed a full ROM to do a total restore?... hopefully I wont need to get to that point?...
Thanks a million again.

hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom

bartito said:
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
Click to expand...
Click to collapse
Hmmmm thanks again but I think Im beyond all this. I dont have a file manager on my system, just realized I deleted the useless stock one and had repalced it with Root Explorer and ES File Explorer. I have them on my External SD Card to install them again but withou a file manager or an app installer cant get to them. And I tried download an app installer from the Market and get Framework errors non-stop and downloads do not initialize... I think Im beyond a quick fix... how do I get my hands on a stock full ROM to restore everything... and how? What a nightmare... gotta tell you, I love Windows Mobile... I love it... never ran into anything like this in the past 5 years of using it... never...
Thanks again!

use "adb" in order to access to your tab from your desktop pc.

bartito said:
use "adb" in order to access to your tab from your desktop pc.
Click to expand...
Click to collapse
Cant. Dont even know if I need Kies installed or not (I did have it installed) but adb just asks me to connect the phone and thats it... its connected aready... this is desperating...

OK I did manage to connect with adb but, how to I install applications? I can navigate to my SD card where I have ES File Explorer and Root Explorer but dont seem to be able to install them... Also if i try to copy Stk.apk I get immediately an failute message... this is crazy...

OK so I managed to install ES File Explorer and Root Explorer with adb... crazy process. It seems my phone is still rooted after the reset. From the phone I copied Stk.apk back to /system/apps where it was before deleted.
But needless to say nothing got fixed... not sure if Stk.apk is now "actually" installed or just there in the folder. But still nothing works and crashes every 10 seconds... logs provider, dialer, phone, framework, contacts... its all a firework of crashes...

Given that you've hard reset your device already, you are pretty much wasting your time trying to "fix" what you broke by messing with /system, and you should really just flash another ROM.
My suggestion would be to follow the advice on this thread.
Regards,
Dave

Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again

VeEuzUKY said:
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
Click to expand...
Click to collapse
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave

foxmeister said:
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
Click to expand...
Click to collapse
Yes Dave you are right, right and right again!!! Thank you for the wisdom and advice!!!
The main thing I have understood with today's messy experience was that the actual ROM files are never deleted or damaged as long as you dont access them via a rooted tool and start deleting them. Now I understand that Titanium Backup, Sprint Backup (my favorite), My Backup Pro and others, only back-up and restore what the user installs on top of the ROM itself. So a full "reset" wipes all that data but leaves the ROM files as they always were. If they got damaged in the process, they'll still be damaged till a a full ROM restores all system data, now I get it.
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Till I find an app or way to do a simple one-click "backup everything" and then "restore evertything" I always feel vulnerable to changes I make to the Tab that may get it unstable or corrupt and then not being able to be restored properly without a full ROM Flash and then re-installing all from scratch.
With WinMo, I could do all sorts of crazy experiments and tweaking and after that, a registry restore or back-up restore would bring me back my phone to exactly like it was with all my stuff and configuration in a matter of seconds or minutes. Thats what I need to find out with this Tab/Android and then Im ready to be able to explore messing up with this knowing I can always easily go back within minutes to the state I had before with all my apps and settings.
This is what I need to learn next how to do! Trampoline without a safety net is not a good idea. Ive alwways loved WinMo for the ease of backing up and restoring whatever I was doing on my handsets withjout ever worrying to put myself at risk to loose it all. I need to learn this on Android and its definitely more intricate!

just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App

instechgainza said:
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...

VeEuzUKY said:
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
Click to expand...
Click to collapse
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App

instechgainza said:
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Where is the modaco kernel section you refer to? I can search for hours and find zilch... these blogs are endless...

VeEuzUKY said:
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Click to expand...
Click to collapse
What you want is a Nandroid backup, which you can only make from a recovery image like Clockworkmod recovery.
Essentially, this does exactly what you want, but you need to flash a new kernel (e.g. the MoDaCo kernel) which supports Clockwordmod.
Regards,
Dave

bartito said:
deletion of Stk.apk causes FC's in phone and acore.
Click to expand...
Click to collapse
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones

b0ricuaguerrero said:
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
Click to expand...
Click to collapse
When I delete stk.apk (for me useless useless useless) the first thing that happens immediately is that when I hang-up on a call made or received, the Tab vibrates then freezes for about 5 seconds then tells me the phone application has crashed. I tried this with 2 ROMs now as a test and its guaranteed. More even, if you use a program like SYSTEM APP REMOVER you can emulate the removal of an app by disabling it... it only takes me to disable STK and a reboot for the phone not to work. cant get rid of it, that simple

HELP - CM10 upgrade and lost IMEI

Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just today I upgraded to CM10. All seemed to be working well except that I received a warning of invalid IMEI. I pushed through it and had the phone working on CM10 (with low memory /data isses - that could later be rectfied) then realized that the IMEI issue would mean AT&T would likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I also ran into a few issues where I could not download from the Play Market App and think this was the reason.
I nandroid backed up CM10 and restored CM9 but still no dice. As I learned later it doesn't touch the efs folder which somehow the CM10 upgrade modified or had the effect to change it. Uuughh. many others were having the issue.
Anyway, I have verified that there are no /efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10?
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair or 2.3.5 Gingerbread would be a time killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?

tonyo123 said:
Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just tpday I upgraded to CM10. All seemed to be working well except that I received a warming of invalid IMEI. I pushed through it and had the phone working well then realized that this is an issue where AT&T will likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I've also run into a few issues where I cannot download from the Play Market App although not sure if this is the reason.
I backed up jCM10 and restored (CEM NANDROID) CM9 but still no dice. As I learned it doesn;t tough the efs folder which somehow the CM10 upgrade modified or had the effect to change it - although I understadn the ROM is not supposed to do this but I see many having the issue.
Anyway, I have verified that there are no efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair would be a killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?
Click to expand...
Click to collapse
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180

Okay
silvertag said:
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180
Click to expand...
Click to collapse
All right it was a long painful night and day. Found and downloaded Heimdall One Click .jar with UCKK4 GB. Ran it and it restored the correct IMEI. It was unrooted and stock.
Then what was previously easy became an adventure to root and and load a kernel with CWM. I must have bricked the phone 10 times havimg to redo the Heimdall to Gingerbread 2.3.5 numerous times including reloading samsung pc drivers. Eventually with Odin, I found the right sequence using Corn Kernel for UCKK4 703 injected with CWM (not 705 or 706 versions which kept failing) which allowed me to get CWM loaded onto the phone.
I still could not restore my CM9 nandroid backups as the /data restore kept failing having to redo things from scratch. So, then I copied the latest CM9 nightly .zip onto the internal SD then loaded it from the Corn-CWM restore. CM9 booted and things were better but phone nad none of the settings and things still not right. Then rebooted into CWM recovery and restored the last CM9 nandroid backup. Now things worked and everything was back to normal with the correct IMEI.
Man that was a long stressing and scary day...
Made multiple copied of EFS for the future.
Will hold off on CM10 until the /efs issue is resolved as well as the memory management is better understood (while on CM10 I immediately ran into /data out of memory problems (I know I needed to move things to SD but never got around to it once the IMEI issue came up).
So, all is back to CM9 and finally working fine

odin to stock, then you will get imei back, backup efs folder, and flash back to cm10.

I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?

master2828 said:
I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?
Click to expand...
Click to collapse
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.

silvertag said:
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.
Click to expand...
Click to collapse
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?

master2828 said:
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?
Click to expand...
Click to collapse
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)

silvertag said:
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)
Click to expand...
Click to collapse
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess

master2828 said:
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess
Click to expand...
Click to collapse
It sounds like you have the backup that is sometimes made in the /sdcard (or /mnt/sdcard) folder, which is the internal storage you see when it's connected to your machine.
To see the /efs folder (assuming it exists), you would need to use either shell commands from inside ADB, or a root file explorer. If it's not there, you should just be able to dump the contents of that backup folder to a directory called /efs and go from there.