[Q][SOLVED] Sim card not detected after installing TWRP - Galaxy S III Q&A, Help & Troubleshooting

Hello all. I'm fairly new to rooting and installing ROMs and what not. I've done a lot of research, checked many many threads, but this is the first time I've had an issue that I just can't find the solution to. I have a rooted i9305 with everything stock except recovery. I recently flashed TWRP 2.8.7.0 with Odin3 v1.85 over CWM Recovery after I couldn't copy backups made with CWM to my computer because it hides it or something and TWRP doesn't apparently. Anyway after I booted it up after making sure the recovery flashed properly (it seemed fine) my phone booted straight in to the home screen and I couldn't connect to mobile data. Normally it asks me to input my pin to access my sim card. Now when I select mobile data it tells me to insert a sim card. Anyway I couldn't figure out how to access my sim card and I'm fairly sure it has something to do with TWRP or the install processes.
I flashed CWM back but the problem still persists. I read it might have something to do with mounting? CWM only says unmount /cache, meaning everything else is unmounted I think? Before I reflashed CWM, TWRP said only two things were mounted and it wouldn't let me tick the box for sd card.
Please help. My phone is basically useless at the moment. Any advice will be appreciated.
EDIT (SOLVED): After trying almost everything else I gave up and decided to flash stock, even though I never flashed another ROM. Anyway I found a copy of stock with the exact same android version (4.3), same CSC and same PDA/AP. I flashed it with odin and it seemed to fix everything. We are going to backup efs folder now just encase anything goes wrong. Some symptoms apart from not being able to connect to the network/sim card not working include the IMEI number being null (see below for how I did that) an unknown baseband (in settings, under about phone, under status) and missing /nv_data files in the efs folder (found with a root explorer/adb). Search for these symptoms when you are looking for solutions. There are a lot of other things I tried before trying this that just might work for others who only have some of these symptoms (e.g. no IMEI number but a known baseband).

Did a some more research after I had some rest. Now think it might have something to do with the IMEI number being lost. I checked my IMEI by entering *#06# in the keypad on in the phone app and it opens IMEI / MEID with a popup saying IMEI null / null. This seems like a serious problem . While researching no where mentioned this could occur just by flashing a recovery. Can someone with more experience tell me what to do from here please?
EDIT: Done some more research with a friend. We checked the efs folder with adb and found stuff in there and backed it up. I think that's a good sign, since apparently that's where the IMEI number is located. Also we found the baseband is unkown. Not sure what that means. In our backup of efs there is no ".nv_data". Apparently most people say that its basically screwed. I did find one post from a user saying he fixed it using advice from another user. He couldn't link it though cause he was new like men. He said to download SGS3 QCN Generator and QPST 2.7. Does anyone know what this could mean?
Still don't know where to go from here though. Any advice is appreciated.

Solved
Okay I solved the problem. See the OP for how I solved it. I'd like to thank everyone here for the enormous amount of help and support they gave me.

where have I to check for the solution?

Another way to solve this
If this helps anyone, I made a backup of a stock rom (4.4.2) with TWRP and when I restored it, the SIM card was not detected at all. In MTK Engineering Mode/CDS Information/Phone 1 (or whatever number yours is) everthing was at null or unkown. AND i FOUND A WAY TO SOLVE THIS! Flash a ROM that detects the SIM card and enter the IMEI numbers. Then, go to TWRP, DON'T FORMAT ANYTHING and then restore the backup selecting the options to restore that you want (for example boot; nvram; system;... those ones). In my case, I restored all of them and I got it to work! This because the phone memory needs to be installed and with android 4.4.2 kitkat the phone storage is not in the backup, only the system storage. I hope this helps the KitKat users and others (because I've never tested this in other versions)!

I install twrp and my mobile not deacting sim card

Ravimahapur said:
I install twrp and my mobile not deacting sim card
Click to expand...
Click to collapse
Hey, welcome to the forum.
You have to understand, we need more info than that, to help you. So provide at least:
- Phone model number
- Current rom
- The exact files you flashed (if you provide a link is best)
- How you flashed them
- Any other things you have done to your device earlier

Hello, i have this same issue on my samsung G355HN, i followed this guide HERE.
As the guide says i rooted and isntalled the kernel with init.d support, but right after installing it the SIM card is not detected anymore with IMEI Null.
If i restore the boot backup everything works again, but i really want a kernel with init.d, any ideas?

Related

[Q] Very odd problem related to efs

Update:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
AUAnonymous said:
So yesterday I got the odd 'Encryption Unsuccessful' error (phone only boots into screen saying: Encryption Unsuccessful, you have to reset...) after my phone ran mysteriously low on battery, rebooting, everything crashing, pulling out the battery and rebooting again.
I did a factory reset/data wipe from within CWM, and the phone would boot up normally, but I got no cell service. I checked in settings, and the baseband was listed as 'Unknown' as well as the IMEI. I had a look in the /efs folder and it was empty except for two more empty folders, 'bluetooth' and 'wifi'.
My problem now is that regardless of what I add or remove to /efs, or if I restore it from a backup, it always resets itself after boot to just contain those two empty folders 'bluetooth' and 'wifi', and the baseband and IMEI are still unknown.
Any help would be much appreciated!
Click to expand...
Click to collapse
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
ctomgee said:
[GUIDE] Recover your IMEI in 9 steps.
(Found in the General section via a Google search...)
Click to expand...
Click to collapse
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
AUAnonymous said:
Oh sorry I should have mentioned I've tried that as well as many other efs recovery tools. I can't follow that guide because step 4 is "go to EFS folder using root explorer, and delete 'nv_data.bin', 'nv_data.bin.md5'", but there are no such files automatically generated like it says. Thanks though.
Click to expand...
Click to collapse
Did you read the whole thread? Specifically, check out pages 5 & 6.
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
AUAnonymous said:
Well, I tried flashing a GB official ROM (I was on CM9) and Odin got stuck on "NAND write start", and any other ROM I try does the same thing. I now only boot into download mode or a screen that says something along the lines of "Firmware update failed, use Kies recovery mode". Is my phone completely screwed? If so what are my repair options given that I'm in the US and I bought the unlocked international version off of Amazon through a reseller (I believe it was originally a French phone) last July?
Click to expand...
Click to collapse
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
ctomgee said:
Nothing you say here convinces me you read what I had to say, and actually read those pages. Because they would have led you to tools you don't mention, that could have helped you.
Click to expand...
Click to collapse
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
AUAnonymous said:
Trust me I've tried using GSII_Repair, HC-k Tool, EFS Pro, reformatting 'mmcblk0p1' via adb and via an on the phone terminal emulator and doing a bunch of other stuff, and while I really do appreciate your help (no one else has even suggested anything , and it's understandable that you're probably used to dealing with idiots, 11 year olds and people that barely speak English), it seems like my problem goes deeper than simply the efs folder being messed up somehow (which I think the original "Encryption Unsuccessful" error points to as well). At any rate, the problem now is not being able to flash a ROM using Odin, and the more I try the more I'm thinking that I'm basically screwed. And before you ask, I've gone through a lot of this thread already, as well as tried other random purported solutions, but any suggestions are definitely welcome.
Click to expand...
Click to collapse
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
ctomgee said:
Yeah, sorry. Unfortunately, for the most part, I do find myself dealing with the group you describe.
Well if you've done the "fix unflashable" thread already... Hmm. I don't know then. When you say you're not able to flash, what do you mean, exactly?
Click to expand...
Click to collapse
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
If it keeps failing at NAND write, NAND is stuffed. Service centre job. JTAG repair won't fix it & a person who normally does JTAGs won't be able to fix it at all unless they're able to swap out the NAND.
Well thanks for the confirmation at least :/ looks like I might be getting the GSIII seeing as I can get it on contract at the discounted price. The only downside being that I'll have to get a limited data plan and that the $700 I spent on this one go down the drain unless I can repair it...
AUAnonymous said:
Well everything is fine in Odin until it gets to "NAND write start", which it never gets past (I've left it overnight). I've tried different ROMs, repartitioning, a different USB cable and everything else I could think of but I've really given up all hope now .
Click to expand...
Click to collapse
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
centuriondan said:
Hi, I had a similar problem with not being able to write a kernel, and ending up with the logo and thebn black screen.
The way I fixed it was to use the Recovery Mode to reflash the rom that I had last working. (in my case it was wannamlites stock ICS). After that I was able to then flash back to my previous Gingerbread Custom rom using CWM's restore function.
Q) You didn't happen to use CWM Touch recovery did you?
*** there is a known issue with CWM touch recovery (which is built on an ICS base) and certain emmc (internal sdcard) firmware id
which could result in the flash being corrupted in a way that can't be fixed outside of the factory.
See http://forum.xda-developers.com/showthread.php?t=1648362
By the way, if your phone does boot, can you dial *#1234# and tell me what the H/W is reported as. Mine currently says "unknown"
Click to expand...
Click to collapse
Thanks for the advice but unfortunately I can't boot into recovery, only download mode., and I wasn't using CWM touch beforehand. It didn't even break when I was flashing a ROM, just when I was using the phone normally. I'm going to be in Europe in a couple weeks and I'll be able to take it in to a repair center where it's still under warranty. All I need to do is to use a USB Jig to reset the counter back to 0 so they'll work on it.
Have you tried Heimdall:
And I'd suggest reinstalling CM9. I found that when I had issues re-installing the kernel that I had to go back to the last working rom (ICS based) b4 I could downgrade.
The fact that you can't get into recovery indicates that either the primary or secondary bootloader is corrupted. Try flashing them again with the CM9 versions. Use the USB jig to get into download mode everytime you do flashing so that if you trash it further the counter is always zero. Also use the original USB cable with no hubs in between the phone and computer, and remove any other usb devices plugged in too.
BTW What was the result of *#1234* HW version?
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
aznboix said:
i've read through all the posts from this topic. mine situation is slightly different.
I"m able to flash to any ROM. I can jump from gingerbread to ICS or vice versa with Odin.
When i type *#06#, it always show "unknown imei" no matter which firmware i'm on.
when i checked in EFS folder, i only have 2 folders : bluetooth and wifi.
I've tried to copy EFS files from people from this forum and paste into the phone's EFS. As soon as i restart the phone, back to 2 folders in its again.
any solution?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17587351, but I see you claim to have tried this already. If it didn't work, you'll need to take it to service.
BTW, the efs folder from another phone won't help you. IMEI is unique to each phone.
i dont have any files in EFS excepte the two folders that i mentioned above. Can't even start the procedures.
Service centre job, or contact Odia via PM & he might be able to recover it for you (for the cost of a case of beer).

S2 IMEI Unkown + No Service PLEASE HELP

Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Shasinda said:
Hi all,
I own a galaxy s2. I'm facing a issue which i've been trying to fix for the past couple of weeks. I tried many threads in this forum, but nothing seems to solve the issue.
This is the issue,
I used to flash custom roms on my device. I used many custom roms including cm9 RC1 and when samsung released the lastest 4.0.4 update i just wanted to chek it out. so I downloaded the generic russian (SER) firmware and flashed it using odin.
After flashing it I was stuck @ boot. i was stuck there for more than 10 mins, so I ended up removing the battery. then I went to samsung recovery(Volume Up+Power+Home) and cleared the cache and user data and rebooted the phone it worked fine. At this time I didn't bother to check whether my IMEI was there but everything worked fine.
After couple of days(without rebooting the device in that time) I droped the phone. battery came off, when I turned on the device again, prohibited mark like thing came in the status bar and there was no service, when I checked the IMEI it was not there.
At this moment I was not sure whether the drop caused the issue or the flashing caused it. I later realized IMEI issue comes because of EFS but sadly I didnt back it up. After diggin for few days I found when flashing one of the custom roms, efs was backed up automatically, I tried restoring it, but it didnt help (Maybe the backup was corrupted )
I followed various threads in this forum but nothing helped me.
Please help me get the IMEI back, I really miss my device :crying:
Click to expand...
Click to collapse
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
fr3nlysmil3 said:
hi there
you said that you have the backup of your EFS Folder, what you need to do is follow the steps in this thread
http://forum.xda-developers.com/showthread.php?t=1264021
its recover your imei in nine steps
my imei was lost as well and i recovered my imei following those stesp, its a great guide if you already have the backup of your EFS Folder
cheers
Click to expand...
Click to collapse
I tried this also, but it didnt solve my issue :crying:
...
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
MistahBungle said:
If you have a backup, then you should be able to recover it. There are tons of threads on here with instructions on how to restore an EFS backup. Search (if you want it fixed, that is. If you don't want it fixed, keep posting to this thread in the hope someone spoonfeeds you. Might be waiting a while tho).
Click to expand...
Click to collapse
I tried almost every thread here in xda about restoring, tried GSII_repair, kTool to restore it but none of them recovered the IMEI. I did not made a backup of efs but when I installed the Hydra H2O ICS Rom for GS2 it made the backup i guess, because a file called "efs-backup.tar.gz" was in a folder called .hydra inside the sd card.
does the drop of the device has anything to do with the erased IMEI?
robdpi said:
I once had a similar problem.
My imei went lost because of a rom upgrade and I DIDN'T have a backup..
I solved the problem by flashing a stock rom (any samsung stock rom will do) with ODIN.
I am not sure what happened, but it looked like that the nv_data folder was "re-generated" and I got my IMEI back.
Now I have a copy of the folder in every storage media around my house
Click to expand...
Click to collapse
I have installed stock roms from samsung using Odin, but then I discovered that efs folder get unmounted everytime I install the stock rom, phone just starts after flashing without android setup wizard, also when I long press power button, menu wont appear, device just shut down, after I restore the efs from the backup i have, and mount the efs using the CWM recovery would bring back the power button long press menu. everything else working except for Mobile Networks. and imei/baseband shows unknown
Drop Caused this problem
Hi all,
Thank you for replying on this thread and helped me figured out my problem, I have contacted Odia and he thinks that dropping the phone damaged the baseband chip inside the main board, not a flashing of the roms or efs folder issue. i have only 2 options either replace the whole board paying LKR 35,000 (New s2 costs only LKR 65,000) or use it as a MP3 player :crying:

"Not registered on network" + stuck in Factory Mode ON - no solution works

Initial state(stock 4.0.4. ROM):
Device was working properly;
Could call, could use 3G internet;
Everything was good.
After CWM zip installing FoxHound ROM:
Simptoms:
Could not call; for every GSM/3G interogation to telecom operator I get: "Not registered on network";
In my pursuite to fix this, I don't know how, now my device ended in Factory Mode(a yellow box with some debug information appears on my screen and the power button now instantly shutsdown the device and no lock screen available).
The IMEI returned by *#06# is different by the one on the back of the device. It's not a generic one "000...", it almost looks like the original, both seem to be valid after some search, but this is odd. I don't know if it was different before installing FoxHound ... never cared.
What I've tried to do:
I've actually feasted on half of internet for a solution to my problems;
I've tried to flash with Odin tons of stock firmwares, modems, CSCs, including well known ones, my operator ones(Cosmote), my country ones(Romania) -> no luck;
I've tried to restore previous nandroid backups -> no luck;
I've tried to CWM zip install custom ROMs -> no luck;
I've tried everytime to wipe cache, factory reset, delete dalvik, fix permissions, reset battery stats -> no luck;
I've tried all the solutions for the "Factory Mode On" problem, including "echo -n ON > /efs/imei/keystr; chown 1001:1001 /efs/imei/keystr" -> no luck;
I don't have an /efs/ backup before installing FoxHound.
Used GalaxSim, everything was green, no unlock needed.
My device is still in the same condition. No one has an answer. Do you have a solution?
Have you tried flashing with mobile odin?
How did you do a nandroid? With s3 toolkit?
Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
Also you may have to flash the insecure image again.
Sorry all could think of.
Sent from my GT-I9300 using xda premium
Samsungnooby said:
1.Have you tried flashing with mobile odin?
2. How did you do a nandroid? With s3 toolkit?
3. Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
4. Also you may have to flash the insecure image again.
5. Sorry all could think of.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
goliathj said:
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
Click to expand...
Click to collapse
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Sad ...
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - http://db.tt/PDH8Bc64 !
IMEI broken restore your backed up EFS folder .
jje
Samsungnooby said:
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I've download it. Great! Also numbering makes you follow up easier
xclub_101 said:
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - !
Click to expand...
Click to collapse
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
JJEgan said:
IMEI broken restore your backed up EFS folder .
jje
Click to expand...
Click to collapse
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
The nandroid ...
goliathj said:
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
Click to expand...
Click to collapse
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
JJEgan said:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
Click to expand...
Click to collapse
Thank you. Leason learned. Will backup EFS from now on.
xclub_101 said:
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
Click to expand...
Click to collapse
Thanks for the info. Good to know.
Finally, my device works. I've contacted a private service.
The Factory Mode problem, which was always on, was fixed by flashing a stock 4.0.4 ROM.
The "Not registered on network" problem had various reasons:
My IMEI had been changed so my modem wasn't accepting any calls. He had rewritten the original IMEI(the one from the back) with "the box".
For unknown reasons for me, 4.1.0+ has some built-in protections and will brick my device everytime I flash it. So, for the moment I'm sticking with 4.0.4.
Some people experienced this problem after updating, so it has something to do with the built-in protections(but the question is "protection against what?"). There's something smelly about our IMEI, we, the ones having this issue. I've bought this device over ebay.co.uk and it arrived unsealed(the merchant told this because he had to check the phone) but with root installed and had 1 count of custom binary flashed, in the download mode screen. This is odd. From now on, I'll ask for IMEI.
I thank everyone for helping me. Best regards!
Stuck on EDGE and in Factory Mode
I have literally over 16hrs trying to get my I747 back working correctly. It all stared when I tried the "Hellfire" rom. I have had my phone rooted running custom roms for over 6 months with no problems. After flashing the "Hellfire" rom I noticed that I was stuck on "EDGE" network, unable to make or receive phone calls or text. After further inspection, I noticed I had "0" for an IMEI#. So I injected my IMEI back on the phone... Still the same problem. I reverted back to stock ROM, Kernel, and Modem... Same problem stuck on "EDGE" network. Several hours later of no stop research, I noticed that my "ERI version Not available". After alot more research I noticed that my "efs" folder was missing the ".nv_data" file. So I backed up the "efs" folder, saved it to my extSD, and then deleted the "efs" folder for the root of the phone. Now I'm in "Factory Mode" even after replacing my backed up "efs" folder with the new one that was created at the root of my Internal sd.
I need help... If anyone has any ideas...:crying:
You might try what they talk about in this thread, don't know if it applies to your situation or not...
I can't post off site URL's, so google "Not registered on network" + stuck in Factory Mode ON - no solution works
It's the thread on androidpit dot com

[Q] S5830i strange rom flash imei issue -Need kind assistance!

Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
Don't consider yourself idiot at all lol. You have explained everything so clearly.
Well,
This problem is so much common with this phone. Don't know why !
Many people including me facing this problem.
Sometimes you just reboot your phone and you will see ur IMEI is gone. Reboot again and its back. -_-
Its really strange issue actually.
You already knew all methods to get IMEI back. This is comman issue with this phone. Suffer it.
Maybe @iamareebjamal have figured this prob out.
Sent from my GT-S5830i using Tapatalk 2
The rom i found was great. It performed so much faster, did not take up much of the very limited memory on the handset, it was the perfect solution to my needs but whenever i use it i cannot make any calls etc due to no IMEI (*#06# shows a complete blank box) and i have tried rebooting the phone so so many times, repeating the process of installing the rom again and again and not once can i ever get it to show IMEI in *#06#. I could understand if the EFS backup also showed that the imei had reset or become corrupt, but it looks fine in Hex Workshop, shows up in device info on Galaxy Toolbox app, i just can't conclude anything from it's behaviour.
Using my original phone's backup the IMEI is restored instantly, and i have taken the EFS backup whilst running the phone on it's original state.
Could it be because something is not right in the rom? Is the rom changing something that i could possibly correct myself? Or something in the rom not suitable for my model and version of the GT-S5830i handset (compatibility issue)?
I really want to be able to use this rom and other's seem to be able to use it without issue which just makes me more determined to find the cause and correct my issue. I also see that many people do lose their IMEI and the EFS backup/restore method seems to work perfectly for them, because they seem to have their IMEI turned to blank values when checking in HexWorkshop whereas mine is still showing as expected.
I cannot make sense of this scenario at all lol.
I appreciate ANY and ALL advice
The rom is was trying was MEHDI ROM v2. I am in the United Kingdom using a GT-S5830i on o2 newtwork with no network locks or restrictions.
Make a new backup of your IMEI(make sure it is lost by once or twice rebooting) . And open via Hex Workshop.
If you see your IMEI in there, then reflash stock ROM and flash this Custom ROM without wiping anything.
If it doesn't solve your issue now too
Try restoring the efs partition before Media Scanning starts and Reboot the phone after media scanning is started.
These all are hit and trial methods. I've myself never found a fully satisfying solution
If nothing works, you'll have to try any other ROM.
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
May these help you..
As about these issue i do flash a Custom Kernel after flashing Rom with no IMEI Number
So After Flashing any Custom Kernel my IMEI Gets back
You can try it with any kernel
I use to flash Rafael.Baugis Kernel flash both its Modules and E3Boot.img
may be try changing kernel..
try any custom kernel...it helps me every time..
i have wiered problem, i can't use custom kernel on stock rom...or stock kernel on custom rom, both of these combination makes my imei disappear every time.
go to this thread for all the explanation
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
Hey, did you solved your problem? i had the same problem once and it was just that the backup made with galaxytoolbox didn't match. So the best solution is to do a backup again and you will have to open the new file and edit it with the HEX editor and input your imei number manually. Here the thread with the info http://forum.xda-developers.com/showthread.php?t=2064034&page=1 and this video is great, but it's in spanish. http://www.youtube.com/watch?v=1kbY0EZYsXE Hope this solves your problem.
I cannot use the galaxy toolbox for my restoring unfortunately as the galaxy toolbox is not working with my current rom, if you know of another program that can help me fix it, i would appreciate it.
Thanks,
Fab
fabiolaec said:
Hey, did you solved your problem? i had the same problem once and it was just that the backup made with galaxytoolbox didn't match. So the best solution is to do a backup again and you will have to open the new file and edit it with the HEX editor and input your imei number manually. Here the thread with the info http://forum.xda-developers.com/showthread.php?t=2064034&page=1 and this video is great, but it's in spanish. http://www.youtube.com/watch?v=1kbY0EZYsXE Hope this solves your problem.
Fab
Click to expand...
Click to collapse
Thanks for the replies, but unfortunately i have not yet resolved the problem.
I have gone over the process again and again, repeating it the same way, trying slightly different ways, the outcome is always the same. Everytime i try i take a EFS backup (taken while the phone is restored to running on it's original stock rom and setup, with the IMEI all working and displaying via *#06#) the EFS file shows the IMEI in Hex Editor. Everytime. It's always there.
Then, as soon as i flash a rom and reboot the phone i have no IMEI. I use the good EFS backup and restore the EFS to the phone (which has the IMEI data intact) but the phone still will not display the IMEI via *#06# and if i check the EFS again it is still showing the IMEI as being in the EFS backup and still good.
So i have no idea why the phone is not seeing the IMEI because apparently it IS still there!
I'm installing roms by using the recovery method to 'apply update', using Samsung basic recovery mode, but could i use the CWM recovery to install? Would that have a different effect? Is it safe to use CWM to install roms as the guide i read said to only install roms using Samsung restore as CWM adds a risk of crashing or bricking the phone?
So many people are able to successfully flash a GT-S5830i and i just do not know enough yet about phone roms to feel confident to do more daring things with different methods for fear of making a critical mistake. So much of the information i have read contradicts itself, and other information neglects to explain certain things or simply assumes you know about bootloaders, CSC files and the like...
I've modified so many gadgets before and am fairly confident with doing such things it's just i can't seem to educate myself correctly over the modifying of these Samsung Android phones.
I just bought a Samsung Galaxy S GT-i9000 today and wanted to remove some of the bloatware so that's my next phone to read up on.
I have been put off a bit because of the issue of losing IMEI. It seems to be a big risk with this model, do other Samsung models have issues with IMEI loss?
Thankyou to all who are taking time to post. I read and appreciate every post, and am enjoying learning about this new topic to me.
Perhaps i shouls restore back to my original working setup, then install the rom using recovery (or via CWM recovery - i have no idea which is safest and the correct method as i read conflicting information) then install the rom without resetting/wiping anything? Would that help?
When i select roms should i be making sure they contain a compatible baseband or something?
I don't understand this area.
DrewKrew said:
Perhaps i shouls restore back to my original working setup, then install the rom using recovery (or via CWM recovery - i have no idea which is safest and the correct method as i read conflicting information) then install the rom without resetting/wiping anything? Would that help?
When i select roms should i be making sure they contain a compatible baseband or something?
I don't understand this area.
Click to expand...
Click to collapse
About recovery use CWM
If you do not wipe then there will some problem occur may be like the phone will not boot after flashing Rom so must do wipe
And about baseband and all don't worry you can use any stock Rom for flashing Roms.
DrewKrew said:
Thanks for the replies, but unfortunately i have not yet resolved the problem.
I have gone over the process again and again, repeating it the same way, trying slightly different ways, the outcome is always the same. Everytime i try i take a EFS backup (taken while the phone is restored to running on it's original stock rom and setup, with the IMEI all working and displaying via *#06#) the EFS file shows the IMEI in Hex Editor. Everytime. It's always there.
Then, as soon as i flash a rom and reboot the phone i have no IMEI. I use the good EFS backup and restore the EFS to the phone (which has the IMEI data intact) but the phone still will not display the IMEI via *#06# and if i check the EFS again it is still showing the IMEI as being in the EFS backup and still good.
So i have no idea why the phone is not seeing the IMEI because apparently it IS still there!
I'm installing roms by using the recovery method to 'apply update', using Samsung basic recovery mode, but could i use the CWM recovery to install? Would that have a different effect? Is it safe to use CWM to install roms as the guide i read said to only install roms using Samsung restore as CWM adds a risk of crashing or bricking the phone?
So many people are able to successfully flash a GT-S5830i and i just do not know enough yet about phone roms to feel confident to do more daring things with different methods for fear of making a critical mistake. So much of the information i have read contradicts itself, and other information neglects to explain certain things or simply assumes you know about bootloaders, CSC files and the like...
I've modified so many gadgets before and am fairly confident with doing such things it's just i can't seem to educate myself correctly over the modifying of these Samsung Android phones.
I just bought a Samsung Galaxy S GT-i9000 today and wanted to remove some of the bloatware so that's my next phone to read up on.
I have been put off a bit because of the issue of losing IMEI. It seems to be a big risk with this model, do other Samsung models have issues with IMEI loss?
Thankyou to all who are taking time to post. I read and appreciate every post, and am enjoying learning about this new topic to me.
Click to expand...
Click to collapse
I'm not sure if you missed this step.
I did efs backup on stock rom and tried to restore with galaxy toolbox on the new rom and IT DIDN'T WORK....
you have to copy your imei number manually (or directly from the sticker) and once you are in the NEW ROM, make a backup of the IMEI. of course if you open it with the hex editor it will be EMPTY.
Then in this new back up file newly created you have to manually input your IMEI number using the HEX EDITOR.
This should work.
Rgds,
Fab
Backup imei of gts5830i
Hi i have just rooted my glaxay ace gts5830i &
want to install custom rom bt i want to first
backup its IMEI bt i don't know much abut
it ....
i heard glaxay toolbox in playstore backup the
IMEI bt in some cases it might no able to
backup ...is there any other way plz tell me i
also tried EFS pro...bt not able to backup bcuz
it didn't show my model name even on
refresh... plz help me to backup its imei...
sahil chandel said:
Hi i have just rooted my glaxay ace gts5830i &
want to install custom rom bt i want to first
backup its IMEI bt i don't know much abut
it ....
i heard glaxay toolbox in playstore backup the
IMEI bt in some cases it might no able to
backup ...is there any other way plz tell me i
also tried EFS pro...bt not able to backup bcuz
it didn't show my model name even on
refresh... plz help me to backup its imei...
Click to expand...
Click to collapse
Don't ask the same question in two different threads.
Galaxy toolbox works almost every time.
Did anyone having a similar issue manage to resolve it or can suggest other steps to follow?
I am having the exact issue but for the life of me can not make the IMEI appear even though galaxy toolbox reports it is fine. Here is my post from another thread, before I found this one.
Flashed ROM, all working fine except as above, no network connection (mobile connection). Wifi, etc all working. IMEI is blank when I do *#06#
Have tried
1. reboots, sim out, reboots, etc
2. tried using galaxy toolbox to backup imei/efs and then restoring after flash. nope no help.
3. tried backing up imei and editing with hex editor but the image already has correct imei. galaxy tool box does report correct imei.
4. just tried flashing rafel kernal using instructions but after doing so, phone does not boot past samsung screen.
5. reflashed back to stock room and crap radio still not working lol
so any suggestions? i need a kernel and then one that works with this rom.
Click to expand...
Click to collapse
Since the above, tried thunderbird kernal and I am still without IMEI.
I would just like to ask. Is it possible, at some point I have deleted EFS partition? Should I be able to see this EFS partition somewhere? Browsing through PC, on SD card or through CW recovery?
My only idea is that I have deleted efs partition so galaxy toolbox has no where to restore to BUT the app itself reports correct IMEI as does the hex value with a backup file.
Ideas, rants and possible suggestions welcome!
Thanks
cyrax.net said:
Did anyone having a similar issue manage to resolve it or can suggest other steps to follow?
I am having the exact issue but for the life of me can not make the IMEI appear even though galaxy toolbox reports it is fine. Here is my post from another thread, before I found this one.
Since the above, tried thunderbird kernal and I am still without IMEI.
I would just like to ask. Is it possible, at some point I have deleted EFS partition? Should I be able to see this EFS partition somewhere? Browsing through PC, on SD card or through CW recovery?
My only idea is that I have deleted efs partition so galaxy toolbox has no where to restore to BUT the app itself reports correct IMEI as does the hex value with a backup file.
Ideas, rants and possible suggestions welcome!
Thanks
Click to expand...
Click to collapse
Follow my restoring guide check my sign.
Hitesh2626 said:
Follow my restoring guide check my sign.
Click to expand...
Click to collapse
Thanks Hitesh but I beleive I have tried all the methods. Check my reply here...
I solved my issue by flashing kernel again...see...
my post

[Q] Help with formated EFS partition

Hey, messed up my phone and could really use some help:
I own a Galaxy Note (GT-N7000). Suddenly the IMEI went null/null and baseband unknown. Tried many things to recover from this but nothing seemed to work. I left the phone with the latest stock rom (Jellybean 4.1.2)
I then installed EFS Professional (rooting the phone first and installing BusyBox) and could connect to the phone with EFS Pro. I tried doing baseband and IEMI repair, and though the log showed it had successfully restores from .bak files in /efs partition, IMEI and baseband were still null.
So then I totally screwed it, hitting the "format EFS partition" by mistake (it was 3am by then) and didn't make a backup first. The phone wouldn't boot, so I flashed the latest stock rom again and now it continually loops when showing the Samsung logo when I turn it on. I can turn it on in download mode and recovery mode. When on recovery mode, it says /efs partition not found so I guess that makes sense.
The question here would be: is there any way I can fix it without sending it to service? Some options that sound possible:
- Flash the phone with some other custom ROM that would repartition the whole phone, thus creating an /efs partition again
- Use some nice software to recover the /efs partition
I'm sure that if a service can fix it, there should be a way I could do it as well.
I know my IMEI number (it's in the sticker on the back of the phone) so there should be a way to restore it into de efs partition, right?
Thank you all and forgive me if I've made some noob comment on this post...just doing my best
javigoile said:
Hey, messed up my phone and could really use some help:
I own a Galaxy Note (GT-N7000). Suddenly the IMEI went null/null and baseband unknown. Tried many things to recover from this but nothing seemed to work. I left the phone with the latest stock rom (Jellybean 4.1.2)
I then installed EFS Professional (rooting the phone first and installing BusyBox) and could connect to the phone with EFS Pro. I tried doing baseband and IEMI repair, and though the log showed it had successfully restores from .bak files in /efs partition, IMEI and baseband were still null.
So then I totally screwed it, hitting the "format EFS partition" by mistake (it was 3am by then) and didn't make a backup first. The phone wouldn't boot, so I flashed the latest stock rom again and now it continually loops when showing the Samsung logo when I turn it on. I can turn it on in download mode and recovery mode. When on recovery mode, it says /efs partition not found so I guess that makes sense.
The question here would be: is there any way I can fix it without sending it to service? Some options that sound possible:
- Flash the phone with some other custom ROM that would repartition the whole phone, thus creating an /efs partition again
- Use some nice software to recover the /efs partition
I'm sure that if a service can fix it, there should be a way I could do it as well.
I know my IMEI number (it's in the sticker on the back of the phone) so there should be a way to restore it into de efs partition, right?
Thank you all and forgive me if I've made some noob comment on this post...just doing my best
Click to expand...
Click to collapse
something like a stock odin flash would fix it: http://forum.xda-developers.com/showthread.php?t=2261598 as long as it flashes a pit file
then once that works, see if efs pro will let you manually set the imei.
if not, then make sure you are stock, and make sure you use triangle away or something and then send it in.
Lgrootnoob said:
something like a stock odin flash would fix it: http://forum.xda-developers.com/showthread.php?t=2261598 as long as it flashes a pit file
then once that works, see if efs pro will let you manually set the imei.
if not, then make sure you are stock, and make sure you use triangle away or something and then send it in.
Click to expand...
Click to collapse
Thanks for the help! I'm downloading the AT&T stock rom from the thread you provided and will let you know how it works after flashing it
javigoile said:
Thanks for the help! I'm downloading the AT&T stock rom from the thread you provided and will let you know how it works after flashing it
Click to expand...
Click to collapse
Whoaaaa You should STOP ASAP! You can't flash the AT&T firmware via Odin since you have the international version.
es0tericcha0s said:
Whoaaaa You should STOP ASAP! You can't flash the AT&T firmware via Odin since you have the international version.
Click to expand...
Click to collapse
I'm from Argentina, this phone is from Movistar carrier. Right now I have the latest stock rom from Movistar flashed, but the rom available does not have any PIT file, so I can't get my efs partition restored and the phone does not boot in normal mode (only download and recovery mode).
As far as I can remember, any phone that works with AT&T in the US works just fine in Argentina with Movistar. I've brought some iPhones from AT&T (not unlocked) and they worked without a problem.
I believe that I have the international version, but what could happen if I flashed the AT&T stock rom?
Thanks!
javigoile said:
I'm from Argentina, this phone is from Movistar carrier. Right now I have the latest stock rom from Movistar flashed, but the rom available does not have any PIT file, so I can't get my efs partition restored and the phone does not boot in normal mode (only download and recovery mode).
As far as I can remember, any phone that works with AT&T in the US works just fine in Argentina with Movistar. I've brought some iPhones from AT&T (not unlocked) and they worked without a problem.
I believe that I have the international version, but what could happen if I flashed the AT&T stock rom?
Thanks!
Click to expand...
Click to collapse
It's either going to fail at trying to install the modem and do nothing, or it'll make it worse. In no way is it going to help anything.
You should be able to find your firmware here:
http://www.sammobile.com/firmwares/
Thanks. I had already downloaded the Movistar stock rom from Sammobile and this time I tried flashing it (using Odin) together with the PIT file and though it said something in the result log about using pit file for mapping, result was the same...still stuck with a bad efs partition that makes the booting loop again and again...
Any thoughts? How can I fix my efs partition? Any help is much appreciated.
Not sure there would be much more to do on your own without the official backup without special tools like SPT, Octopus Box, SRS, etc, but those cost more than the phone, so would have to find a shop that has the equipment and is also competent at using them. Many of the major software tools have repos with files like you need and the correct way to load them. I'd love to have one for my shop, but requests to fix stuff like this don't come often enough to justify the expense when there are more pressing matters...
On another forum they were saying that you can use the efs backup from another clean phone because it does not actually contain the IMEI, so if you could find one of those... I tried to download a couple for you yesterday to test but they either failed to open correctly or didn't pass the md5 validity check in Odin, which is why I didn't repost.
I didnt mean flash the rom I linked. That was an example. sorry guys.
Lgrootnoob said:
I didnt mean flash the rom I linked. That was an example. sorry guys.
Click to expand...
Click to collapse
Desperate times call for desperate measures
I'm still working on restoring the /efs partition, even with a null IMEI, at least to be able to use the phone with wi-fi for other purposes (if I can't find someone to flash a good efs.img and restore the IMEI completely).
Right now it's still a brick. Will post update soon.
Thank you all!
javigoile said:
Desperate times call for desperate measures
I'm still working on restoring the /efs partition, even with a null IMEI, at least to be able to use the phone with wi-fi for other purposes (if I can't find someone to flash a good efs.img and restore the IMEI completely).
Right now it's still a brick. Will post update soon.
Thank you all!
Click to expand...
Click to collapse
I found some links.
http://forum.xda-developers.com/showthread.php?t=1724415
http://www.sammobile.com/forum/showthread.php?t=13564
http://imadn2008.blogspot.com/2013/01/fix-boot-loop-for-samsung-galaxy-note.html

Categories

Resources