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
Related
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.
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
I
DrunkWithAGun said:
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
Click to expand...
Click to collapse
That new efs folder you're talking about still contains the IMEI number specific for that device. Any act pushing or copying that efs folder to your old phone is illegal.
However since you can still boot to Download mode on your old phone you can try flashing a new stock firmware via Odin and see if it boots properly. If it fails then better wait for a more expert answer since I haven't experience your issue on mine yet (and I hope i won't).
DrunkWithAGun said:
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
I
Click to expand...
Click to collapse
I don't understand why you would want to do that? You have purchased a new phone, which has a new IMEI. Putting the old IMEI on there is a) pointless and b) not possible (I think).
Unless you have purchased a stolen phone?
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one?
As said no
Suggest you ask in the IMEI?EFS thread instaed of starting yet another ,
None of the phones are stolen, but if i could get the old one working again i could either sell it for more than just a faulty phone or give it to my wife, anything. It's just an annoying paperweight.
My intentions was just to get phone in a better state then it is in now, meaning putting an original efs-structure from my new phone on it. And if it that way could jumpstart it so i could atleast get TW running, and from there switch out the new contents in the folder with the contents from the old phone i put on my pc.
And i am sorry for starting yet another efs-thread :\
Mod Edit
duplicate thread
Thread Closed
malybru
Forum Moderator
Ok, first of all, I take full responsibility and made some really stupid mistakes. I consider myself an experienced Android user and have been flashing ROMs and radios since the OG Droid.
I am, however, new to Samsung/Touchwiz, and made an error I'm trying to determine if I can repair.
I have not flashed any custom ROMs on the Note 2, but I was unlocked/rooted with CASUAL. I was having some issues with my proximity sensor and my capacitive button lights, and decided to ODIN back to stock. Here is where I screwed up, I think. Instead of flashing like normal, I think I want a completely clean slate, and I checked Nand Erase. I know, please don't bash me, the brick sitting on the table is punishment enough. I was thinking of erasing backups, as in Nandroid (Nand) backups.
Well, everything flashed as normal and the phone bootlooped. No biggie, booted into Recovery, and it gave the warning it couldn't mount the /data partition. I did a factory reset from stock recovery, and everything seemed fine. The phone booted correctly, but it wouldn't activate on Verizon. It finally allowed me to skip set up, and I found the dreaded "Unknown" IMEI.
No, I didn't have a back up of the IMEI. I began reading and studying on ways to fix this, and it seemed simple enough, but I couldn't get QPST to recognize my phone so I could repair the IMEI. The computer could see it on COM5, but QPST kept saying No Phone.
I tried a few other methods, including EFS Professional and NV Item Reader/Writer. But everything said it couldn't communicate with the phone. I made sure I had it in the correct mode in the Phone Util hidden menu, checked USB cables, ports, and drivers a hundred times, with no joy.
Then on a whim, I checked my /efs folder with ES File Explorer, and the contents are empty. Not sure how I erased all the contents, but now I'm pretty sure I'm screwed.
I wanted you to know my steps, before I started asking questions.
1. If I can get another working Note 2, is it possible to use a copy of that phone's /efs folder on mine? If I can get QPST to work, I could then use it to inject the correct IMEI back into the folder.
2. Is there anyway anyone here could upload their /efs folder so I can try it?
3. Any suggestions on QPST and getting it to recognize my phone?
4. Am I just completely hardbricked and out of luck?
Thank you.
I know there are other similar threads, and I have searched...a lot. I'm just trying to figure out if I'm missing anything.
Also, I've found some IMEI repair services online that will fix a missing or corrupt IMEI for about $25 plus shipping. Does anyone know of a reputable repair service for this issue? I'm getting somewhat desperate to get this fixed. I'd be willing to pay someone here to fix it as well if you have the know-how and equipment.
Thank you.
Hi,
There are success stories on this issue in xda...would suggest you to read xda articles on this issue.
Thanks,
Nikhil Dhand
[email protected]
Hope your problem is solved
Thanks,
Nikhil Dhand
Email/chat: [email protected]
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??
Hi guys,
So, i have a big problem with my Galaxy s3. I dont know what happened, but at one time was home and your battery has ended. So I went to charge the battery and for my surprise, when I switch on the phone, it could not make calls.
I took it for Technical Service to solve the problem, but I got the information that they could not fix, because the telephone broke.
Dissatisfied, I came home and tried to fix it, and found that the IMEI listed as "null / null". I searched on various websites that could do to fix it. I installed the original 4.3 version of the S3, I ROOT your phone, tried to repair the various ways that the EFS folder could be corrupted, but i just get a generic IMEI.
I just want to know if I have any alternative to put again on phone my unique IMEI, and that can make calls again.
Please, help me with that.
EFS might be corrupted, if it was not rooted you should stay that way and get it for warranty repair, now you have to get your efs repaired, it is around 15$ in service centre, i had to do so, and in future try to make efs backup so if something happens again, you just restore and you're good to go.