Right I'm really sorry to have to burden all you lovely helpful people with this, as I know there's dozens of threads, of which I have sifted and sifted through for the past 2 days. Most of them have been helpful and I am now 95% fixed, but here is the down low:
Mid-last week, I finally decided to stick a custom rom on my old, laggy Galaxy S3. Up until this point I had been running on stock 4.1.2 Firmware, rooted, with things like Bloatfree cleaning the device up a bit.
I did some research and landed on the latest Paranoid Android build, based on 4.4.4. All was rosey for a little under a week with no problems whatsoever until this Monday afternoon. I was doing nothing other than opening Snapchat when my S3 turned itself off, only to get stuck on the bootscreen.
It took me all day yesterday just to get the thing to boot again, I must of tried 4 different stock roms, searching for ages to find CWM that would flash via Odin and any fix just to get it past boot. After finally getting it into Recovery it kindly let me know that "E:Failed to Mount /EFS".
Since that happened I have managed to get the phone booted up into a stock 4.3 rom, exited factory mode and got it rooted with busy box and terminal. It has become a WiFi-only Tablet, essentially.
I am at the last hurdle, where I have no network connectivity and my IMEI is wrong. I of course have my correct IMEI on the back of the phone which I wish to reintroduce to the phone. I do not have an EFS backup.
TL;DR
Phone on Stock 4.3 ROM SGS3INT-XXUGMK6-BTU-20131216, rooted with busy box, root explorer and terminal. Always had stock kernel.
IMEI incorrect, with no backup of EFS.
I have tried:
EFS Professional - EFS Format errors on mount read/write
NVitems_reader_writer, though I can not get my device to stay in RMNET + DM + MODEM mode to be able to connect via COM port as a serial device.
A few of the other simpler methods from the forums
Any help is much appreciated, and while I have read that modifying the IMEI number is frowned upon and illegal practice, I am simply trying to restore it to it's original state, no tom foolery here.
Regards
Dan
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
boomboomer said:
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
Click to expand...
Click to collapse
Unfortunately I have tried that with every local shop, and they don't seem to think they can do anything about it, and there is no other official Samsung repair centres nearby! Seems like a problem that independents don't come across too often.
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Saad_ said:
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Click to expand...
Click to collapse
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Is there a driver I could be missing for it to connect as a USB modem instead of a serial port when trying this?
Dan
I have a similar problem, efs restored, imei is showing right but cant get any signal, saying emergency calls only. After flashing stock.
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
A nandroid does not back up the efs unless you are using philz or twrp and you specifically tell it to. There is no way in CWM.
Not sure if you new that or not since you said a full backup but just thought I would pipe in just incase so you don't have troubles next time.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
hey, i have this similar problem right now. So, what i have to do is rolling back all the way to 4.0.4? will it work? but i haven't coded the right IMEI.. do i have to? btw when you have that failed to mount efs, did you use the tutorial that uses adb shell and mke2fs?
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
vuli111 said:
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
Click to expand...
Click to collapse
Discussion is against the rules, and also illegal.
Changing to rmnet + dm + modem Mode is illegal?
Changing imei, which what your post stated, is illegal -don't ask for help here.
Take it to a repair centre and pay them to restore your efs folder.
I did not ask for help to change the imei.
I asked for help to get in the rmnet mode. Is this illegal too??
Related
Hi XDA and a Happy New Year to everyone.
I recently bought a SGSII from someone, at a very low price, because of some software problems.
I could use it for spare parts, but I`d like to fix it if it is possible.
As far as I know, the phone was used to "test" different roms and tweaks by a kid who thought was a developer, and accidently messed up its efs folder without backing it up, so the phone now has a generic IMEI (0049..)
I found a final solution for this, in case nothing works, from user Odia, who can restore your efs folder without having a backup, and I`ll keep this option as a last resort.
But wait, there`s more.
The phone is acting really weird. Each time I start it, it reverts back to its default settings. From power options, to widget location, everything goes back to their original state.
Further more, while taking photos with it works perfect, when recording a video, it doesn`t save its self on to the flash memory.
I`ve tried flashing a different ROM (at the moment it has a default 2.3.3 Samsung ROM) from 2.3.3 to 2.3.5, using Odin. Everything goes well while flashing, with no errors in Odin. But after the phone reboots it has the same firmware/rom as before. Nothing changes. I`ve confirmed this by dialing *#1234#.
The IMEI problem isn`t that important (at the moment), but I`d like to be able to at least use the phone and to install a different ROM.
I don`t know what could be the problem, it`s like everything on it is on Read Only, or like a computer with Deep Freeze installed - everything looks ok while writing, but after a reboot, nothing was saved.
If you need anymore details regarding the device, please let me know and I`ll try to post them asap.
Hoping someone can help me with it.
No IMEI means your phone will not connect to a network as its part of the handshake process .
Suggestion would be .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery or install CWM and ROOT kernel if needed
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware from stock firmware post
jje
Stuck again.
First of all, thank you JJEgan for your reply.
I`ve tried what you`ve told to, but failed.
Tried installing CWM (GT-I9100_ClockworkMod-Recovery_4.0.0.2 and GT-I9100_ClockworkMod-Recovery_5.0.2.3) from the official thread, using Odin (both 1.83 and 1.85) but after the phone reboots, it isn`t there.
If I try accessing it via VolUp + Home + Power, it goes directly into the Android Recovery System, the default one, and not CWM.
I`ve even installed it via Odin and immediately removed the battery in order to prevent the phone from rewriting itself after Odin said everything is OK, and got the same results.
Dialing *#1234# gives me the following:
PDA: I9100XEKDB
PHONE: I9100XXKDH
CSC: I9100XEKD9
Build Info: Tue Apr 26 09:10:03 KST 2011
Click to expand...
Click to collapse
I`ve tried locating the correct version of CF-Root for it but I can`t find one for KDB in the official thread.
As I said in the first post, when I try to write something on it using Odin, everything goes well, no error, it doesn`t freeze, but after it sends the reboot command, it`s like nothing happened. It reverts everything to stock.
Any other thoughts ?
I do not believe you have an international version of the sgs2, you may have 19100 G or other version which cannot be rooted by using the standard cfroot.
check the label under the battery for which version you have.
I do not trust any of the information from the firmware as it may have been altered as one of the tweaks.
as far as I know the was no XXKDH. the number system used is 2 letters followed by a number
k = year d= month 2011 - april is correct but the H is not.
you may have a chinese rip off of the sgs2.
# = version for that month.
Thank you for your answer Cosmic Blue
The phone isn`t a rip off. It`s a SGS2 from Orange, Ukraine (I believe).
Everything on the device is signed by Samsung. The phone`s specs are exactly what they should be. Kies identifies is perfectly and I can sync everything with it. Samsung drivers also work correctly.
Label behind the battery:
MODEL: GT-I9100
SSN: I9100GSMH
RATED: 3,7V = ; 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
Click to expand...
Click to collapse
Plus IMEI (The original one I`m trying to restore) and Serial Number.
Also, on the bottom rim, next to the speaker, there`s the Orange logo and I9100.
I had a brand new I9100 before, and this one isn`t any different from that one in anyway, except that the OS is all messed-up and the IMEI is a generic one, a problem a lot of people found themselves in around here.
Also, you can find the firmware version I mentioned above at samfirmware.com
As XWKDD was one of the first i would say KDH is probably correct but you are reading wrong info .
Therefore H is correct and phone is i9100 SGS 2 not a Chinese rip off .
First firmware on stock roms thread .
XWKDD
Firmware info
PDA:XWKDD
PHONE: XXKDH
Build date: 26/04/2011
However it looks like you have failed to install cwm and root .
Go to the cwm and root thread and flash the first one as below via ODIN
http://forum.xda-developers.com/showthread.php?t=1103399
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip -
Flash that one via ODIN report back
jje
Same problem with it.
Downloaded the mentioned CF-Root version, flashed it using Odin as PDA, rebooted with no SuperUser app in application drawer. Rebooted and tried accessing CWM with no success. Just Android System Recovery <3e>.
Also, reflashed CF-Root without Auto Reboot in Odin, and when it finished, I removed the battery and put it back in. Tried to access CWM with the same results as above.
I managed yesterday to root it by flashing XWKDD_insecure.tar as PDA and using SuperOneClick v2.3.2. The phone had a SuperUser app on it, but the phone was really lagging and after a reboot, it wasnt` there anymore.
The problem is definite then the read only memory is not holding the flash possible its a part that holds the ram during flash that is corrupt .
Sorry not a clue it looks like service job to me .
A thought have a look at Mobile ODin thread .
jje
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
proone said:
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
Click to expand...
Click to collapse
I have seen this before, basically the NAND controller is toasted so it cant write, only read.
As they said, only way is to replace the motherboard (Where the NAND/controller) is.
Its a shame they wont repair it under warranty, I suppose they noticed that its been flashed and killed
Model: GT-19100, SSN: 19100GSMH, made in korea by samsung, I flashed it back using a rom from Xda forums but now its Android 2.3.5, no super user, I have HC-kTool that I downloaded from new Android market, it says I need root to use HC-kTool. I have Root explorer and Rom manager but I dont have root, how do I fix imie, baseband, my Samsung galaxy s2 works well on wifi, everything works but it doesnt read my sim?????
Hi everyone,
So, I'm way out of my depth here and I've searched high and low for a similar situation to mine to no avail.
I'm fairly sure I have EFS issues. I flashed CM9 onto my S2 and had the RIL issue which caused me to have no reception. After trying about five different modems I gave up and went back to stock.
Unfortunately, I still have network issues. I realised after some mucking around that intermittently I my phone would recognise my baseband and IMEI and then it wouldn't, it would switch on restart. This sent me down the EFS issue, and now I'm freaking out.
I screwed around with my EFS and I don't seem to have done any permanent damage. My phone still recognises my baseband and IMEI, and it can still get a signal. Now I'm getting "Enter Network Lock Control Key" when I boot up though, and can only make emergency calls. The phone came unlocked, it was bought outright, and I have run CF-Root's unlock key finder to no avail.
Any suggestions?
Cheers
BobSwinkle said:
Hi everyone,
So, I'm way out of my depth here and I've searched high and low for a similar situation to mine to no avail.
I'm fairly sure I have EFS issues. I flashed CM9 onto my S2 and had the RIL issue which caused me to have no reception. After trying about five different modems I gave up and went back to stock.
Unfortunately, I still have network issues. I realised after some mucking around that intermittently I my phone would recognise my baseband and IMEI and then it wouldn't, it would switch on restart. This sent me down the EFS issue, and now I'm freaking out.
I screwed around with my EFS and I don't seem to have done any permanent damage. My phone still recognises my baseband and IMEI, and it can still get a signal. Now I'm getting "Enter Network Lock Control Key" when I boot up though, and can only make emergency calls. The phone came unlocked, it was bought outright, and I have run CF-Root's unlock key finder to no avail.
Any suggestions?
Cheers
Click to expand...
Click to collapse
Try these apps.
1. (Try this one first, if it doesn't work, then try the second app).
https://play.google.com/store/apps/details?id=com.helroz.galaxysunlock&hl=en
2.
https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&feature=more_from_developer
Good luck
Swyped from my Samsung Galaxy SII
Jokesy said:
Try these apps.
Good luck
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hi, thanks for the reply. I've tried both those tools to no avail. The problem has regressed to the original problem now. Do you, or anyone else, know the trick to restoring an EFS folder that isn't hasn't been turned into a tar folder? I backed up before doing any of this, but the backup doesn't seem fully functional when I restore it.
BobSwinkle said:
Hi, thanks for the reply. I've tried both those tools to no avail. The problem has regressed to the original problem now. Do you, or anyone else, know the trick to restoring an EFS folder that isn't hasn't been turned into a tar folder? I backed up before doing any of this, but the backup doesn't seem fully functional when I restore it.
Click to expand...
Click to collapse
Sorry about that:
1. Have you ever flashed Siyah kernel before, when your phone was still working perfectly?
2. This should help you manually repair your efs folder : forum.xda-developers.com/showthread.php?t=1264021
Ps: if you have flashed Siyah kernel before, it always backup your efs partition in .tar to external SD /EFS_BACKUP, with time stamp on each backup, each time you flash it.
Swyped from my Samsung Galaxy SII
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
This has been posted before and does not work in many cases .
Although the method can be useful to restore to original firmware .
jje
Yes, flashing a stock rom will sometimes fix the problem of the efs folder not being mounted or read. It won't fix a corrupt partition or damaged files.
The stock rom you flashed didn't contain any efs data so it isn't any substitute for a backup, you were very lucky it worked.
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Same problem
hello guys,
Well I'm to tell the story of how my aunt damaged apparently her phone
At first the phone is a samsung galaxy S3 from movistar (locked), and she bought a freaking iphone 5 to give the S3 to his husband and there it starts the problem he's in another company so she goes to a store to unlock the phone, the guys on the store supposedly unlocked the phone. So when she arrives home, she puts the sim into the phone and SORPRISE it says emergency calls only and not registered in network. After a week she calls me and hands me over the phone.
My surprise was when I put it in recovery mode, it says flash count 3, and then i did all these terrible things with thephone.
1) Flash it to a stock movistar rom 4.1.2.
2) Sorprise the IMEI sayd null.
3) Searching in the web, found the ariza patch, and I patched it without saving the efs (big mistake).
4) The phone imei's became 0049.
5) So I flash it back to the rom they put in the store and the imei went back I make sure it was the one on the back of the phone.
6) I still stuck in the emergency call not registered in the network thing.
7) Now I rooted the phone erased the whole content of the efs directory (this time with a back up).
8) Did the tutorial thing with samsung kies and I'm back with the movistar rom with the 0049 IMEI.
I don't what to do at this point besides going to samsung and send it to repair I really hope they can fix it at a low price.
Sorry for my english, I'm trying to improve it.
Best Regards
Andy Serrato... the spaniard
Start by reading the stickied faqs and guides EFS/IMEI sticky for one or just pay for a repair .
Galaxy S3(GT-I9300) having the same problem! HELP HELP HEEEELP PLEASE!!
Very unfortunately. this didn't solve my problem, the phone's Serial number is still that auto generated junk, and the EMEI is 00499901640000 as before. I had 4.1.2 on my S3 and Kies has updated it to 4.3 without resolving the issue!
can anyone give an idea on how to surely resolve this issue please. its about 3 months now ever since my phone got screwed up!
Pay for a repair
Perfect
I cannot believe this worked, but it did.
I messed up somehow by trying to flash the wrong cwm.tar file (for i9305) I needed i9300 of course and odin stopped halfway and got stuck, i then pulled the cable out and everything got very messy,.. i kept getting lots of errors etc. i somehow managed to install an old cm11 rom which worked lovely. BUT I had no baseband, no imei, no network, no number, nothing, #*06# or whatever it is, wouldn't work. nothing.
I then started to figure out how the efs filesystem worked, then foundout kies has an emergency thing where i guess they look into there database what your imei was when the phone was built. this would not work because I was using a custom rom (i think) but then I stumbled upon this post. thank goodness!!!!!
It's just restarted and internet, signal, imei is back, baseband version is back. all in order.
however, i think i was also very lucky, but for those of you who are in the position i was in, but this doesn't work, I do think there are ways to get an old efs going again and modify it to your "should be" imei,
if anyone needs an IMEI, I can give you one from a phone i had stolen in vietnam, (not sure its even legal to give it out but whatever)
thank you
Nev
EFS recovery
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
kangerX said:
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Click to expand...
Click to collapse
I have tried the method posted in the thread ..... but EFS didn't recovered ........ so i decided to follow your procedure
like making empty EFS folder.... so how can i do that ...and if so will it work .....as someone here mentioned that Download firmware package doesn't contains any EFS contains .... help me out :good:
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
i love u so much right now,.. worked like a charm,.. and after thjat i was able to unlock my phone,... thanks so much i would love to give u 10000 thanks
I cant get past entering my model number,, I read it right from under the battery and it still keeps telling me to enter the model number. G550T1 doesnt change from G550T1 no matter how many times you type it... I give up.. If I could just get a twrp backup for mine I may be able to fix it. It's metropcs! flashing to the T-Mobile twrp backup by mistake thinking it was the metropcs one is what got me in this situation... Should have paid better attention...
UPDATE: It took my numbers and I'm trying it now, wish me luck
Well I got it to take my model number and did the whole software thing. Everything is all back to stock but it didnt fix the problem.. Still no net work and says theres no sim card.
Which shop samsung
Which shop samsung or repair shop bro.
Please tell.?????? me I am facing too problem.
stwischu said:
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 bought in Europe. Today I installed the Paranoid Rom. Unfortunately when going back to stock later today I lost my network and IMEI. I can't believe this happend after al the roms I installed so far.
I read to several tutorials on how to fix this but I am running into several problems before I get started.
When playing with my phone I accidentally made an EFS back up about a year ago, not knowing what is was.Too bad my external HD crashed a while back and lost that so I don't have it anymore.
I read that you can get your IMEI back with sgs3.nv.gen.zip but I can't download sgs3.nv.gen.zip from anywhere because Microsoft Security Essentials keeps saying it's a virus, even after turning it off with msconfig.
When running that NV reader/writer and typing in the number, I only get UART MODEM or PDA and USB MODEM or PDA and no other options.
I really hope someone can help me with this... Thanks so much
Did you actually read general > sticky roll-up thread > IMEI \ EFS - Know this stuff?
If not, do.
SOLVED
I did actually and i understand it. i was lucky enough that i had made some backups so when I used Ktool to make a backup it was just a matter of copy/paste the old files. And it seems to work for now. It also seemed to work with Cyanogenmod but now i am back on stock.
Hello, guys!
I'm facing a real hard issue with a brazilian Galaxy SIII GT-I9300. (international model)
Last night I did the CWM tutorial, and then I installed a custom ROM based on 4.4.4 KitKat.
Everything works great, but I lost the IMEI in this process.
I lost the entire night reading about ways to get my original IMEI restored, and I tried to use some tools from the XDA fórums.
Anyway, I had a serious problem with USB debugging function, and after a few tries, I got the phone being connected with Windows again.
Now, every time I try to use NV-items reader_writer, I can get the phone connected but it still can't read the phone.
the message "Failed....Phone does not Answer" shows up when I click the Read button.
I used the *#0808# in the dial app to get USB settings but when I choose the "RMNET + DM +MODEM" option, Windows says that could not install drivers for my "Unknown Device", and the RV-items reader_writer could not access the phone.
Please, I beg you help me!
I lost an entire night trying to solve this, but I can't get over this point.
I got Null IMEI values right now!
EDIT: If I force the DM mode via USB settings, Windows says that can't install drivers for the device. NV item reader_writer still saying that the Phone isn't responding for the Restoring Process
P.S: I already did the 226.txt with the phone original IMEI for use with NV item reader_writer
EDIT2: I just found is a Factory Mode in the last reboot!!! What it means?
Not even Kies can help me...
Even with Kies, I'm facing problems!
There's nothing in the world that makes my recent installed Kies connect to the Galaxy S3.
I was trying to make a restore with Kies!
But even this is not working...
What should I do? Please, help me guys!
Take it to a service center for repair. Nothing here can fix a corrupted efs.
I had a similar problem last week, and if you don't have a backup there is nothing you can do but take it to the repair service. However, you can try in some phone stores. Some of them has a device called box with which they can restore your IMEI and it's way cheaper than Samsung's service. It worked for me.
Good luck dude.
PD: I've heard that when you flash CM roms it backs up you efs automatically to your internal memory, but I've never found it, give it a try if you want.
vitiin92 said:
PD: I've heard that when you flash CM roms it backs up you efs automatically to your internal memory, but I've never found it, give it a try if you want.
Click to expand...
Click to collapse
No this is not true. CM does not touch the efs or modem so it has no need to.
To backuo efs you need to manually do it from recovery or with apps.