Related
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
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??
Hey Guys,
My Samsung Galaxy S3 is killing me, the problem is the following:
It was working fine one day and the next day, it started giving the error message "Unfortunately, the process com.android.phone has stopped." along with network and wifi going off and on every 5 to 10 seconds, overheating from the sim card and sd card side, and rapid draining of the battery, i have tried all the solutions i found but nothing worked for my case, so i had to go to the ultimate fix which is to recover factory settings, so i have restarted the phone, done the factory settings, and that solved the problem, the phone started fine, i started installing my apps again, and everything seemed ok, after the battery went dead, i replaced it with a charged one (i have a major problem with my charging port, its damaged beyond repair, so i have 2 batteries, using an external charger) then i started the phone, and the new problem happened, the phone is stuck on samsung logo, naturally i went for the factory reset again, but this time (to my great luck) that did not solve it, and i can see the error " E: failed to mount /efs (Invalid argument)" two times.
i have tried copying the md5 file to the sd card and done "apply update from external storage" but it did'nt help.
could anyone help me solve this problem by using the sd card? because i can not us usb cable to use Odin, or all that stuff
by the way, my phone is stock not rooted, jelly beans 4.3
In a twist of events, i actually managed to repair the charging port at a repair shop, the phone is charging normally and detected by windows, now, i have noticed that both samsung kies and smart switch give the message that my device is unsupported, no idea how, so i started using Odin, i have managed to flash twrp recovery to the phone successfully, tried to root the phone while in this state but no luck, got a stock rom from sammobile and i was successful at flashing it to the phone using Odin, but that did not solve the problem, i still think that the problem is the efs partition, its corrupted somehow, i don't know why, my phone was not rooted and never flashed it with a custom rom to expect such corruption, anyways, now my S3 is not stuck on samsung logo, its now caught in a bootloop, ulternating between samsung logo and the android green gut opened logo, i flashed recovery again with CWM, and now the bootloop is not happening, instead when i power the phone it goes to CWM recovery after samsung logo and stays in recovery, i believe the problem got weirder and weirder, any suggestions? how to fix the efs mounting issue without changing or deleting my IMEI, since my phone is not rooted, i did not have any backup of efs.
HI, I have had a variety of problems with my i9000 and so has pretty much everyone
Instead of going down the Odin root and getting mixed up in PIT files, there's a solution which with enough effort can fix almost everything. Use Samsung Kies. The program will restore your phone, no matter what state its in to its factory settings. Mine was so bad it didn't actually have an OS at one point. Once all the drivers are installed and u have connected ur phone, go to tools>emergency firmware recovery and type in the model and serial number. So GT-i9000 and ur serial number. Then put the phone into download mode and then click next and it will fix in about ten minutes. Be patient getting into D/L mode, because it is quite troublesome.
Hope I helped.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Sorry,after reading, u said u cant use a usb cable. But then how did you copy the file to your sd card. If u cant use a cable at all, like not even at a friends house or something then im sorry. But if you can try what i posted above.
Mihir571 said:
HI, I have had a variety of problems with my i9000 and so has pretty much everyone
Instead of going down the Odin root and getting mixed up in PIT files, there's a solution which with enough effort can fix almost everything. Use Samsung Kies. The program will restore your phone, no matter what state its in to its factory settings. Mine was so bad it didn't actually have an OS at one point. Once all the drivers are installed and u have connected ur phone, go to tools>emergency firmware recovery and type in the model and serial number. So GT-i9000 and ur serial number. Then put the phone into download mode and then click next and it will fix in about ten minutes. Be patient getting into D/L mode, because it is quite troublesome.
Hope I helped.
---------- Post added at 02:46 PM ---------- Previous post was at 02:41 PM ----------
Sorry,after reading, u said u cant use a usb cable. But then how did you copy the file to your sd card. If u cant use a cable at all, like not even at a friends house or something then im sorry. But if you can try what i posted above.
Click to expand...
Click to collapse
Removing the sd card and using a card reader connected to your pc to put the files over the card is not an issue, but the phone's charging port which doubles as data connection is damaged and can't by changed because its motherboard point of connection is damaged by a stupid technician, so any solution to my problem (other than changing the whole board) would have to include the sd card to get thedata to the phone
herculese911 said:
Removing the sd card and using a card reader connected to your pc to put the files over the card is not an issue, but the phone's charging port which doubles as data connection is damaged and can't by changed because its motherboard point of connection is damaged by a stupid technician, so any solution to my problem (other than changing the whole board) would have to include the sd card to get thedata to the phone
Click to expand...
Click to collapse
If the phone is in such condition I would try and get it professionally repaired or get a new one. Butttt, because that's not how we do thing at XDA , i would suggest seeing if you could find a flashable file that consists of either stock firmware or a ROM u know is stable. For the S3 GT-i9300 i would suggest any of the ones in development on XDA, most worked for me, or a touchwiz based one thats stable. I think that might help. Also, try rooting it, if possible, and check the efs folder (i think it requires root to access) Check if files look corrupted or are missing compared to what they should be (google this)
Also, just checked, this might be what ur looking for:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Mihir571 said:
If the phone is in such condition I would try and get it professionally repaired or get a new one. Butttt, because that's not how we do thing at XDA , i would suggest seeing if you could find a flashable file that consists of either stock firmware or a ROM u know is stable. For the S3 GT-i9300 i would suggest any of the ones in development on XDA, most worked for me, or a touchwiz based one thats stable. I think that might help. Also, try rooting it, if possible, and check the efs folder (i think it requires root to access) Check if files look corrupted or are missing compared to what they should be (google this)
Also, just checked, this might be what ur looking for:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you for your reply, but you keep forgetting the dark and gloomy fact that the phone won't start cannot be connected to pc, so rooting the phone is not possible, and correct me if I'm wrong, flashing the rom needs pc as well, I'm guessing if i can restore the efs folder with a stock one that should solve it, but is it possible to navigate to that folder in recovery mode?