I flashed a few roms, and I have an efs backup for imei/product code, but for some reason they won't restore, my phone is running fine on stock 2.2 froyo (unrooted), but I was wondering if there is anyway to get a new phone, so I can have an actual imei and use kies.
If you have just flashed roms and not modified your imei I don't see why it would be incorrect. Mine has never altered throughout many flashes. There is definitely some good threads on restoring imei In tthe development forums but If you can't figure it out and really crave your factory imei mobiletechvideos.com has a imei restore service for $30.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
If you have just flashed roms and not modified your imei I don't see why it would be incorrect. Mine has never altered throughout many flashes. There is definitely some good threads on restoring imei In tthe development forums but If you can't figure it out and really crave your factory imei mobiletechvideos.com has a imei restore service for $30.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I tried the technique that mobiletech uses, but I lost my efs backup folder now, and it won't restore without that. I also cannot get the product code to stick. I want a new phone....warranty help please.
When I get home ill look more into imei restoring. With no backup it might be hard. I have an efs backup on my PC in thecase something were to happen to my internal memory. can never be too careful. Curious though, why did you modify your imei? Still not too clear as to why people do this.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
When I get home ill look more into imei restoring. With no backup it might be hard. I have an efs backup on my PC in thecase something were to happen to my internal memory. can never be too careful. Curious though, why did you modify your imei? Still not too clear as to why people do this.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I didn't do it on purpose, for some reason a long time ago I must have performed a bad flash.
Upon further research I see what you mean. Looks like this happens with bad flashes and with no backup it looks like the hex editor method located herehttp://forum.xda-developers.com/showthread.php?t=881162 is your only hope. You say you have tried this on jf6 rooted and no success?
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
I took an /efs backup from my first capitvate. I ended up sending it back to amazon as I had that infamous problem with the first OTA bricking phones. When I got my second, an I9000 rom changed my product type in my nv_data.bin. I saw an /efs backup on my SD card, forgot it was from my first phone, deleted /eft and tried to recover from the backup. I ended up with the test IMEI
I flashed back to JF6, called samsung, told them my IMEI became corrupt from a firmware flash and they asked me to send them the phone. They paid shipping both ways and fixed my IMEI in a week (they simply changed out the mainboard which seems to be a common fix for them).
Provided that your indicator strips are still white and there is no physical damage, I would imagine they would do the same for you too.
z28james said:
I took an /efs backup from my first capitvate. I ended up sending it back to amazon as I had that infamous problem with the first OTA bricking phones. When I got my second, an I9000 rom changed my product type in my nv_data.bin. I saw an /efs backup on my SD card, forgot it was from my first phone, deleted /eft and tried to recover from the backup. I ended up with the test IMEI
I flashed back to JF6, called samsung, told them my IMEI became corrupt from a firmware flash and they asked me to send them the phone. They paid shipping both ways and fixed my IMEI in a week (they simply changed out the mainboard which seems to be a common fix for them).
Provided that your indicator strips are still white and there is no physical damage, I would imagine they would do the same for you too.
Click to expand...
Click to collapse
So should I flash back to stock JF6, and send them my phone?
Related
Two days back I flashed the JPC firmware through Kies and everything was fine. Then I noticed that my Product code has been changed, so I rooted my phone and restored the nv_data.bin and nv_data.bin.md5 from the backup.
Today using registry hacks, I downgraded to an older stock firmware through Kies. My phone is not rooted anymore after I downgraded. Now though my phone boots, but there is no network. When I go to Wireless and network->Mobile networks it says "Insert SIM card to access network services" and activates Flight mode. Mine is an Indian Galaxy S. It's not sim-locked. I checked the IMEI to see if it has been corrupted, but nothing. The IMEI is intact, same as original. Product code, Sales code everything is right.
What did I do wrong here? Why don't I have network now? What am I missing here? Please help
Maybe you didn't install your sim card correctly. The corner with the rectangle "removed " should be in the top down when you face the back of the phone
Sent from my GT-I9000 using XDA App
I flashed JPC again with Odin. Everything's back to normal now. But... how do I go back to the stock rom and get it working? I have the stock rom, but when I flash it I don't get network. Does this mean that I'm stuck with JPC forever?
Thanks to the above poster. The sim is inserted properly. I'm a programmer so I have a good knowledge of what I'm saying, but unforunately not so good with linux kernels.
I faced the same problem, days back... when i was testing with JPC... you cannot move to any of the 2.1 foirmware
The JPC changes the file permissions and few of the properties of NV_data in efs...
Leter i found a way to fix, it... now i am back to 2.1
I had a sam issue, so I just restored nv_data file from backup file and I m good to go. I deleted md5 file as well. Back up file has creation date of before I flashef with 2.2. Hope this will help
Sent from my GT-I9000 using XDA App
I know this is an old post but I just had the same problem after restoring a backup through clockwork mod and I couldn't find a decent answer anywhere.
I fixed it just by re installing the kernal, in my case it was hardcores speedmod kernal.
Obviously this is a better option as you don't have to wipe your phone.
whobeit said:
I know this is an old post but I just had the same problem after restoring a backup through clockwork mod and I couldn't find a decent answer anywhere.
I fixed it just by re installing the kernal, in my case it was hardcores speedmod kernal.
Obviously this is a better option as you don't have to wipe your phone.
Click to expand...
Click to collapse
Someone needs to add this to the OP. Worked like a charm.
I am wanting to flash the perception build. I was wondering if I flash it will I lose my unlock? Im currently on cognition 2.3b6.
Thanks
Probably. I was unlocked and lost mine... if worried, back up your /efs folder - especially nv_data.bin. It takes some work, but it is possible to unlock again.
Wait so if I backup my /efs folder (on 2.2 right now), then I update, can I just replace the nv_data.bin on the i9000 firmware?
probably, I have not tried. But if you roll back, you have the original mv_data.bin (and md5) files to get you back where you were. If you don't have the /efs files, and your original unlock code, you can be stuck with no onluck, even on 2.1.
michael.seltzer said:
I am wanting to flash the perception build. I was wondering if I flash it will I lose my unlock? Im currently on cognition 2.3b6.
Thanks
Click to expand...
Click to collapse
Yes you will lose your unlock but if you have your codes saved then just re-enter them and it will be good to go...if you don't have your codes there are methods to unlock again posted in the Dev forum...
So I have flashed a bunch of regular cognition builds and not lost my unlock , but since this is an i9000 rom its different.
Do I have that right?
Never lost my unlock after flashing any cappy/i9000 roms.
Have you flashed perception?
No but it makes no difference, flashing to stock jf6 and installing any rom won't make you loose your unlock, why would you think that would happen?
Get the sgs unlock app from the market, it'll show you your codes and save them on the sdcard just in case you still think you'll get locked.
already on 2.2 so i can't get my codes. I have flashed many roms not sure why i9000 roms would be different thats why i asked
michael.seltzer said:
already on 2.2 so i can't get my codes
Click to expand...
Click to collapse
Flash back to jp6 http://forum.xda-developers.com/showthread.php?t=731989
Im not sure you understand once u go to 2.2 the codes are encrypted. going back does nothing, still encrypted somehow.
peachpuff said:
No but it makes no difference, flashing to stock jf6 and installing any rom won't make you loose your unlock, why would you think that would happen?
Get the sgs unlock app from the market, it'll show you your codes and save them on the sdcard just in case you still think you'll get locked.
Click to expand...
Click to collapse
It has happened to many of us, so don;t tell people it can't happen.
Some combination of firmwares encrypts the data in the nv_data.bin and the result is that the unlock code that was saved no longer works.
The only solution is to replace or rebuild the nv_data.bin file so that the phone will accept an unlock code. Saving the /efs partition files before flashing is the only way to recover the original files, as flashing back to stock will not restore the /efs partition.
This issue affects all galaxy S phones, but no one has determined the exact cause other then flashing ROMs.
Oh, and SGS unlock just looks in the nv_data.bin for the codes, if the files are encrypted SGS fails, just like manually looking at the files with a hex editor fails.
michael.seltzer said:
Im not sure you understand once u go to 2.2 the codes are encrypted. going back does nothing, still encrypted somehow.
Click to expand...
Click to collapse
There is a thread in the development section about unlocking 2.2 after the nv_data.bin is encrypted. This method works for 2.1 in the same situation:
http://forum.xda-developers.com/showthread.php?t=831569
There are tools that will rebuild your nv_data.bin file for you, I did mine manually (before the tools) but it worked. I was re-unlocked.
alphadog00 said:
It has happened to many of us, so don;t tell people it can't happen.
Click to expand...
Click to collapse
I guess i was lucky, never happened to me, thanks for the info.
I was just thinking, is there a chance that the phones that AT&T sells without a contract are factory unlocked and this is the reason some of us don't get relocked after this procedures?
At least it would be a good explanation
So i'm still a little confused on this subject. Is it the i9000 rom that can cause relocks or it just roms in general?
rastanthology said:
I was just thinking, is there a chance that the phones that AT&T sells without a contract are factory unlocked and this is the reason some of us don't get relocked after this procedures?
At least it would be a good explanation
Click to expand...
Click to collapse
No, there is only one model of the captivate and AT&T will not unlock the phone even if you buy it off contract. There have been a few exceptions, but not many.
If they were factory unlocked, no one would need to unlock to start with.
michael.seltzer said:
So i'm still a little confused on this subject. Is it the i9000 rom that can cause relocks or it just roms in general?
Click to expand...
Click to collapse
Again,
I don't think anyone has determined the exact cause. No one has taken an unlocked phone and methodically flashed ROMs to see what order of events causes it to relock.
Many of us experimented with many different ROMs and at some point realized we were relocked.
i wnat relock my i9000
i want relock (carrier lock) my samsung i9000 any solution??
I have two captivate I987's. Both are 2.2 and running firefly 3. On one phone I backed up stock froyo with nandroid via cwm. I also backed up the stock kernel via sgs kernel flasher. Can I take the nandroid bu and kernel bu from one phone, put it on my pc, compress to zip, then place in the sd card of the other phone and flash via cwm? Getting me back to stock 2.2?
Also, i use the free version of TIBU. I copied my back up to my pc. When I try to put the backup on my new captivate, TIBU doesn't seem to recognize it. I've placed it in the root of the sd as well as the TIBU folder. Any way to make this work?
1. No.
2. Hit the "problems?" Button in tibu and make sure busybox is installed.
Busy box is installed. Maybe something else not right? Do I have to use paid version? Since I got ur attention, is using odin one click with any build higher than 1010 an almost guarantee of brick. Does anyone know? Currently I have a 1010, and an 1101.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cdub3 said:
Busy box is installed. Maybe something else not right? Do I have to use paid version? Since I got ur attention, is using odin one click with any build higher than 1010 an almost guarantee of brick. Does anyone know? Currently I have a 1010, and an 1101.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I hear it depends on the phone, some do brick but some don't, I've used one click on my 1012 and didn't have any problems but that's just personal experience
Sent from my captivate running Speed and Looks Ginger Style
You don't need the paid version.ummm Make sure it's pointed to the right folder and that it didn't get corrupt copying over from your pc.
I flash and mod 3 captivates: 1 a 1010, and 2 are 1012 all I've used is one click. no problems.
You can have a bootloop issue not a un recoverable brick. Go check the last few pages of the one click thread ... I described what to do when that happens. It's not a huge deal.
And this works for I897 ? Couldn't find ur post in the thread. There seem to be hundreds of replies
Sent from my SAMSUNG-SGH-I897 using XDA App
Cdub3 said:
I have two captivate I987's. Both are 2.2 and running firefly 3. On one phone I backed up stock froyo with nandroid via cwm. I also backed up the stock kernel via sgs kernel flasher. Can I take the nandroid bu and kernel bu from one phone, put it on my pc, compress to zip, then place in the sd card of the other phone and flash via cwm? Getting me back to stock 2.2?
Click to expand...
Click to collapse
That won't work.
And I think you will run into issues with the efs directory if you try it. Your IMEI number will be converted to the IMEI of the other phone. What will AT&T do if two sims are logged on to the same IMEI phone? Don't know. There may be a way to backup everything but the efs directory, but if not, I'm guessing the phone will balk at restoring a backup with four images from one phone, and the efs image from a second phone.
Just used odin one click on my 1101 build. Worked perfectly, which is good, cuz I'm gonna return this thing soon. Since it worked once, with this build, it should work all the time now, right? (unless something else occurs, like bad connection, usb probs etc). If i flash 2.3 roms will it still work, or will the new boots screw it up. read some posts, but wondering if any of you have personal experiences.
Cdub3 said:
Just used odin one click on my 1101 build. Worked perfectly, which is good, cuz I'm gonna return this thing soon. Since it worked once, with this build, it should work all the time now, right? (unless something else occurs, like bad connection, usb probs etc). If i flash 2.3 roms will it still work, or will the new boots screw it up. read some posts, but wondering if any of you have personal experiences.
Click to expand...
Click to collapse
I have a 1008 batch, so I can't speak about model issues, but I have used Odin One Click to flash back to stock JF6 (Eclair) from a 2.3.3 ROM. The new bootloaders should not create any adverse effects for your phone. Odin One Click will flash both bootloaders back to stock Eclair.
I'm on Captivate #4, which is replacement #3 because the geniuses at AT&T believe the last phone I had was the cause of poor signal. The others were replaced for different reasons and I'm not convinced a new phone will help the signal but it looks like I'll wind up re-flashing it and returning the one I'm sending back AT&T back to stock. I've noticed after flashing the last two phones that it breaks the IMEI so that it displays a generic one(004999010640000). What's the best ICS based ROM that I can flash that won't break it again this time? If I knew what to back up I could do that too and just back it up before flashing to SlimICS. I tried following some guides to restore it on the other phones, but it didn't work for whatever reason. I know the /efs folder gets backed up, but then what?
dreamersrevenge said:
I'm on Captivate #4, which is replacement #3 because the geniuses at AT&T believe the last phone I had was the cause of poor signal. The others were replaced for different reasons and I'm not convinced a new phone will help the signal but it looks like I'll wind up re-flashing it and returning the one I'm sending back AT&T back to stock. I've noticed after flashing the last two phones that it breaks the IMEI so that it displays a generic one(004999010640000). What's the best ICS based ROM that I can flash that won't break it again this time? If I knew what to back up I could do that too and just back it up before flashing to SlimICS. I tried following some guides to restore it on the other phones, but it didn't work for whatever reason. I know the /efs folder gets backed up, but then what?
Click to expand...
Click to collapse
does this help? > http://forum.xda-developers.com/showthread.php?t=898387
Hello,
I've had my cappy for almost 2 years now... I could be just lucky, but never had a problem and I flashed all sorts of Roms.
Anyway it wouldn't be a bad idea to backup your whole EFS folder and there is also a couple apps to backup and restore your IMEI.
I'm currently on Ics Remix and love it... No IMEI problem smooth as butter... No sleep of death and battery is really good. I'm using the Roms kernel devil.... Which is what you want anyway.
Sent from my SGH-I897 using Tapatalk 2
I'd always made a backup but always forget where I put it or what I called it.. I think my luck it was on the phone itself and got wiped out, go figure. Not too sure though.
Hi,
I bought a Galaxy S i9000 from someone for cheap because they said it didn't work. Anyways, after getting into ODIN on it and flashing a custom rom, I got it to boot. Problem now is, I think the IMEI number on the phone is screwed up (I get a message on phone startup) and can't connect it to the cell network with my SIM card.
Is there anyway to restore the IMEI number back into the phone, so that I can get it to register properly again? Also, then unlock it?
Thanks,
colhavoc said:
Hi,
I bought a Galaxy S i9000 from someone for cheap because they said it didn't work. Anyways, after getting into ODIN on it and flashing a custom rom, I got it to boot. Problem now is, I think the IMEI number on the phone is screwed up (I get a message on phone startup) and can't connect it to the cell network with my SIM card.
Is there anyway to restore the IMEI number back into the phone, so that I can get it to register properly again? Also, then unlock it?
Thanks,
Click to expand...
Click to collapse
My IMEI got invalid too a few months ago when i flashed a custom CM10 JB Rom.
I got my IMEI back when I flashed back to GB via Odin.
Custom Rom developers advise flashing a CM9 ICS first before a Custom JB to avoid an invalid IMEI.
That's what i did, I got my IMEI back and currently using a custom JB Rom.
To unlock your phone, try to search in General Forum, there are some threads that discusses how to do it.
Yup, had the same thing with an upgrade. It's like the ROM upgrades but the IMEI bits don't.
You need to downgrade to get your IMEI back. Once you have it back DO A NANDROID!!
Then you can try to upgrade again.
It usually happens when you skip a version of android.. eg froyo to JB.
Just downgrade via Odin to stock firmware and upgrade each version in order.
Simple as that.
sent using my fat fingers from the robot eating the apple...
Well, restored to 2.3.6 and worked fine. I then installed CM 7.1 (Worked) then went to CM7.2 (Worked) and when I went to CM 9.0, it then stopped. No message about invalid IMEI or anything, just no bars.
Not sure, reverting back to CM7.2 for now.
You can try doing this process again but now backup your /efs library with Nitrality or some other /efs backup app.... make another copy of the backup in your pc and just restore it when needed...
Sent from my GT-I9000 using xda app-developers app
Before trying to flash, get into recovery and format these partitions:
/datadata
/data
/cache
and delete dalvik cache as well
Reboot phone and let's see if it starts up this time.
When you go back to gb using this app backup your imei
https://play.google.com/store/apps/details?id=com.nfye.insanity.toolbox
If someone help me i definitely HIT THANKS....
VIP1 said:
You can try doing this process again but now backup your /efs library with Nitrality or some other /efs backup app.... make another copy of the backup in your pc and just restore it when needed...
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Hi,
Tried this. I restored back to factory default image, worked.
Upgraded to CM 7.1, worked
Upgraded to CM7.2 Worked. Used Nitrality to backup /efs folder
Upgraded to CM 9.0, did not work. Restored /efs from backup. Did not work. Reboot, did not work.
So, for now it's back to CM7.2. I gave it to a friend to test out, if it works then he will be keeping it for a while and i'll try something else to upgrade it when he wants to. Thanks again for the help, seems it wants to be stubborn.