[I9003][Help] Unknown Phone - Samsung Galaxy SL i9003

Hey guys! After flashing to xxkpe, the phone and csc both showed "unknown". After repeated flashes the csc problem was fixed but even after flashing 5 times the phone still showed unknown and it wont recognize the sim card. any suggestions???

what did you flash? more details please...

Oh sorry i forgot to add i flashed XXKPE!!!

Is your IMEI visible

No IT IS NOT. I flashed back to xxkp9 and same problem!

Open phone and dial *#06#
If it doesn't show the imei number and you don't have the back up, your only option is samsung service center
Sent from my GT-I9003 using XDA App

1. Try flashing XXKPE twice. Use the latona file before the first flash only. Then factory reset after flashing the firmware for the first time. You probably placed the files wrong.
2. You can always try to use someone's nandroid backup of CWM and restore on your phone and test and check.
3. Service center.

how to make the back up of IMEI

tarunagg said:
how to make the back up of IMEI
Click to expand...
Click to collapse
Backup IMEI
Basically the method is almost alike. Just flashing it is an issue that I don't know how.

I think you post in wrong forum

I just used Root Explorer and copied my "/efs" folder to my external SD card (i.e copy "/efs" folder as a whole to "/mnt/sdcard/external_sd/backup").
But it sounds like you hadn't done this backup before you flashed. I think the only option is to go to the service centre and have them recover it for you. Before you go, take a Nandroid backup using CWM and a backup using TitaniumBackup. Make sure all the backups from Titanium go to the external SD card.
Also it is probably best to flash back to your original firmware (or something close from here) before giving it to them, and try to act innocent (---> "What's a firmware!?! I flashed who?!?!")
BTW @ Misledz: Here is the original post. Also contains a compressed efs attachment. Do you think it would be too complex to modify that and flash it (find the IMEI from the box and manually input)?
Cherio!

Can anyone please upload a copy of the efs folder?

Related

[HOW-TO]Prepare your phone to send into Samsung/AT&T

This Guide is for any user that has a Rom installed. This will back-up almost everything the user has put on the phone.
So, here are some things you need.
Heimdall One Click KB2 - http://forum.xda-developers.com/showthread.php?t=1266172 (thanks to AdamOutler)
1) First, make a nandroid backup.
2) Make an /efs backup (adb pull /efs) (also can use an app called nitrality available in market)
3) Now, you will need to Plug in your phone to the computer. Take ALL the folders on your SD card and copy them to your laptop. (Mine was user/android/sdcardbackup)
4) Remove Micro-sd card, and SIM card
5) Open up your dialer and dial this code *2767*3855# THIS WILL WIPE YOUR SD CARD and /DATA
6) Reboot the Phone
7) put your Phone in download mode, open heimdall One Click and insert the phone and make sure that heimdall recognizes it
8) Flash the new firmware Bootloaders not required
9) Have the Phone Boot up Completely (takes a long time)
10) Check to see if your /efs has been edited. Use this thread http://forum.xda-developers.com/showthread.php?t=881162 (and your efs backup) to get it back.
11) You might want to dial *2767*3855# Just in case if there is anything left.
12) You should be running KB2, have your SD cleared, and ready to be turned into samsung.
Post Questions and comments below!
i decided to save this one, no clue why, just wanted to feel important...
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
bigbooty said:
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
It isnt supposed to erase the /efs but ill include it, thanks!
sepherian said:
It isnt supposed to erase the /efs but ill include it, thanks!
Click to expand...
Click to collapse
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
When my cappy messed up, my imei got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs. Product code was different also. Flash enough roms and it can mess up something as someone might be a novice coder and mess your device up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: fixed Imei
Nucleartx said:
When my cappy messed up, my meid got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
meid? i think you mean imei?
bigbooty said:
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
Click to expand...
Click to collapse
Yes, I know. This Flash is not intended to mess with the /efs AT ALL, i have checked the package and it has no reference to /efs in the scripting. The post including the package also says this:
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Click to expand...
Click to collapse
So as you can see the number i have them call wipes the data and SD but they have their nandroid and SD backups. The number i have them call also doesnt touch the /efs. Trust me, I tested this method before i posted it and i didnt make an efs backup and my IMEI was perfectly fine afterward. I assume that nothing here messed with my /efs at all.
The only thing that would change the NVdata.bin would be an unlock tool. And i doubt that it even changes it.
OP was updated with more accurate steps.

[Q] And Help With my Null IMEI. FIXED!!

I'm on Valhalla-Final with it's stock Kernel. I had a Bad flash which resulted in my IMEI becoming 0000000000000.
My phone is working fine right now (I can't download Swype Beta. I get can't install Android Emulator Notific) on Valhalla-Final AND I have my (Pre flash) efs folder backed up on my external sdcard and my laptop.
My back up is different than my current efs folder. It has my IMEI #, ect, in it. It is Good.
I have researched and read this thread:
http://forum.xda-developers.com/showthread.php?p=12807550
But a fix for me isn't in it.
What do I do??.. I could delete my Null efs folder and paste my back up then reboot??..
I DON"T WANT TO MESS THIS UP. To me the only thing worse than this problem is a Hard Brick.
Any Advise will be Appreciated.
I ALWAYS Give Thanks!
First take out the battery for 10mins and see if the IMEI is restored after you power it back on.
Sent from my SGH-T959V using XDA App
I've tried that twice already and I'm doing it again right now at your suggestion..
right before the battery pull I copy, pasted and rebooted my backed up efs folder to the efs folder WITHOUT deleting my current and 000000000 efs folder. That did not work.
FIXED!!!
I deleted my 00000000000 IMEI efs folder and copy and pasted my pre-flash efs back up using Root Explorer (Paid version) Then Powered down and Powered up.
My IMEI AND Wi-Fi MAC address are both restored!!..
I guess I knew what to do but wanted confirmation.. I don't have a contract and paid $500 for my phone so Mod with Caution..
If I have Your/THE answer for you I will ALWAYS give it even if I think you should know it or find it on your own.. Probably because I can only help on a few things so I'm proud to and not burnt out helping Members LOL...
Thank God I came here when there was no CWM or ROMS and it was so Dead People were EAGER to Help me. Because I knew NOTHING.. This is my first time Rooting and hacking Andriod. My first Forum..
I Love this Phone, It's Devs, Themers, Modders and Members!!
THANK YOU ALL!
Now that my IMEI is restored I just downloaded and installed Swype Beta...
If you get a " Can't Install Android Emulator" Notification check that your IMEI is not 00000000000..
Menu> Settings> About Phone> Status> IMEI.. check Wi-Fi MAC address TO

[SOLVED] Efs?

What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA
1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium
Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium
Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA
I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.
Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.
you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?
EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!
Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176

Recover your IMEI without a backup!

I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
It works perfect for me even without the .nv_data file. Before this i only get simbols instead the imei number. You save my phone!
recovered IMEI by just flashing the CM10 base
I dunno if it's just me or what. I lost my IMEI on Slim Bean.. so I had this thought. I hadn't had this issue with the CM10 rom, so I decided to do the standard flashing procedure. Once CM10 was installed my IMEI came back. I had full signal and all is good. I decided to go back to Slim Bean to see if it would fix the IMEI issue. I flashed it just like the OP stated and walah! I had my IMEI back and everything worked without having to go back to GB, ICS and then JB again. I don't know if this will help anyone, but just wanted to note other people about it. Why did this work for me?
will this mess up my phone more?
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
mikied12 said:
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
Click to expand...
Click to collapse
This is either a joke or a joke.
Many Thanks
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
I just wanted to thank all of you who have contributed your brain power to the xda forums. This advise worked great and after a lot of self doubt I now consider myself a semi-noob. Thanks again.
A J
Thanks on this. I had a backup of my EFS folder, but the tool I used to create it made a .img file and once I got it into JB, the tool didnt work. UGH.
Just want to say thank you for posting this. I have a friend who had her Infuse stop getting calls, texts, etc. Turns out her IMEI was all question marks and other invalid characters. ATT wouldn't help her at all and either did a full reset.
thank you, this method really works!! finally my imei is back...no more symbols, now is time for a efs back up
Since when do phones lose their imei's? That's a new one on me.
sholsten said:
Since when do phones lose their imei's? That's a new one on me.
Click to expand...
Click to collapse
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
zackdjones said:
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This method didn't work for me :\ Any other ways to solve this issue?
can i use this Efs on galaxy R to repair unknown baseband & Blank imei????
Thank you very much. This is what I need
worked great. thank you.
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Punnyabrata said:
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Click to expand...
Click to collapse
Strange things are happening to me.
About 2 weeks back this problem started and today when I reconnected the SIM and restarted the phone everything was back to normal. Phone is picking up signal/3G etc.
Surprised is the word. Leads me to believe some app must be responsible for all of this.
Thanks,
PC
It is showing invalid mds sum...what I do?
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
sachinppatel16 said:
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
Click to expand...
Click to collapse
Have you tried Odin as administrator ? that's might be the problem

[UNSOLVED] Unknown IMEI/Baseband

LESSON LEARNT (for everyone): Please make sure to do a complete EFS backup before you do anything or you will end up like me!!!
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
Repair IMEI using EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing stock ROM for Malaysia region (Froyo and GB)
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
Restoring Nandroid backup from other SL user (Thanks Rich'Dawg')
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
Some websites said about fixing IMEI for small fees but in cases of blank IMEI (*#06#), chances are only 30%.
And my last resort would be getting it replaced in Samsung service centre or any repair shop, which I suspect that the motherboard would be more expensive than some simple new Android phones.
Leaving this forum for the moment as to collect more money to get a new phone . . . :crying:
Lastly, thanks for all the input. Greatly appreciated.
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
nicsptl said:
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
Click to expand...
Click to collapse
Nope. I totally lost signal and mobile network.
cheeyeen said:
Nope. I totally lost signal and mobile network.
Click to expand...
Click to collapse
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
chongns said:
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
Click to expand...
Click to collapse
Yes I did but nope I couldn't find. sucks.
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
chongns said:
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
Click to expand...
Click to collapse
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
cheeyeen said:
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
Click to expand...
Click to collapse
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
chongns said:
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
Click to expand...
Click to collapse
Fixed permission.
I found one .nv_data.bak dated year 1994 , which I think came in when I was trying to flash some efs fixes i found in XDA.
Without much hope I tried what you said, but still nothing happened. IMEI blank, baseband unknown.
Is it possible to have the mobile phone repair shop with RIFF or Jtag or some box thingy to have this done?
i think you must change the motherboard
cheeyeen said:
[Request] Is it possible if anyone could send me a Nandroid backup of a working rom, so I could restore it via CWM? (It is a way I found in the XDA forum).
...
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
And my last resort would be getting it replaced in Samsung service centre??
I don't know how much would it cost in Malaysia to change the motherboard but I'm sure it will be stupidly high...
Or.. does that mean my time in i9003 forum is up..? :crying:
Please help me because I don't want to buy a new phone yet! :crying:
Click to expand...
Click to collapse
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
I would try anything as long as it works! Please do!
Best of Luck
a friend of mine ran through the same same problem and i think he did some sort of repair from a shop but later we came to know that the backup can do the task not sure whether that work or not but u can give it a try,, BEST of Luck with that..... Hopit Fix the Issue
Good luck sir! As far as I know, if you would choose to replace the motherboard from repair center, it would cost you more or less 80% of the original price of the phone. So it would seem that you have to buy a new one. I hope that a nandroid backup (as stated above) would solve the problem. God bless you! Think positive
i have the same problem and tried those solution the TS tested and still no luck, i wan't to try those nandroid backup but can't find any.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Xperia.IN said:
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Click to expand...
Click to collapse
can you share it with me if you have nandroid backup, i will try to fix it with z3x and asansam
never thought deodexing gonna brick the phone.. ive deodex once without any problem.. without any doing backup before that.. lucky me.. huhu
try other people's nandroid and see.. i dont think it needs a specific emei or what so ever.. as long as its a backup.. goodluck..
the problem is we can't find someone to lend us their nandroid backup.
I did it!
Bro, try use Efs Pro, http://forum.xda-developers.com/showthread.php?t=1308546
Try the new version, you can choise Qualcom version, write you IMEI number, go back to initial and do NV Restore.
My SG Fit go back to life (after maybe 4 months with 0000000000000 Imei). :good:
I´m very happy
Hope it work for you! Good luck!

Categories

Resources