I recently just flashed the .pit and .pda tar from this:
http://forum.xda-developers.com/showthread.php?t=1349895
to get to stock EH03 and work my way from there
My problem is, after booting my phone I have no 3g signal. I tried *228 and reactivating but that doesn't help. I can receive texts and calls but still no data. In my About Phone : everything shows EH03
Could anyone give me some help? I'm a little worried..
EDIT: Found what I did, I accidently had Phone EFS Clear checked when I ran everything... do any of you guys know how to fix this? *228 doesn't help me out
By looking at my MEID from Settings -> About Phone -> Status , it still seems to be there reading
DEC: 268435459603183741
Hex: 0xA000002430947D
This does match the number underneath my battery.
* I am trying to get root access now but SuperOneClick seems to be "not responding" when on Shell Rooting Device Step #7 - WaitforDevice
* I have an old phone lying around, but it's not a smart phone and I don't want to try activating that one and reactivating this - I hear I will lose my unlimited data..
Maybe you can try this link?
http://forum.xda-developers.com/showthread.php?p=17587351#post17587351
or
http://forum.xda-developers.com/showthread.php?t=772949
If you do activate another phone and reactivate your fascinate, you can get your unlimited data back, you just have to call them. I think there's a window where you can reactivate a smartphone and retain your current data plan but I'm not sure what it is, probably 2-4 weeks, so if you're just reactivating it real quick it wouldn't be an issue. Just the hassle of calling and having them fix it.
I have no idea if that would even help your issue though, I've always seen checking the "EFS clear" box in odin highly warned against but I can't say for sure what you did by doing that, maybe someone else knows, or google it?
I finally managed to get root access.. I'm going to look into both of these threads:
http://forum.xda-developers.com/showthread.php?p=17587351#post17587351
http://forum.xda-developers.com/showpost.php?p=7997364&postcount=5
and see if I can magically fix it.. Thanks for your help so far guys.
EDIT: by #06# .. it shows my MEID as 45035996880868477 ..
I've looked for an /efs folder in my phone directory but it seems I don't have one. At this point I think I am screwed. I can't try what any of those links say because they require that you have the EFS.
As of now, I'm stuck with a stock EH03 rooted device with no data only call/text.
I'm guessing you probably already saw this thread? Did you try activating another device on your line, then reactivating the fascinate?
Yeah I already saw that thread, but thank you for the help.
I took my phone in today since I do have the warranty and I got it sent out.
Also, I got a Galaxy Nexus since I was due for an upgrade.
Thank you for all your guys' help though. It really does help.
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
NSingh95 said:
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
Click to expand...
Click to collapse
I've never heard of having to backup the /efs folder after rooting...has anyone else?
I've rooted and unrooted my device a-helluva-lotta times and I've not only never had this problem, but I've never backed up
my /efs folder afterwards.
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
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.
Been using the soldier andriod 9 rom for a while now. was using my phone yesterday when it went off suddenly. turned it back on and got greeted with the black screen of death ((BSoD). I tried every trick available to try and get the screen to turn back on but nothing worked. I was hesitant to reset my phone because i had a lot of important accounts i got my phone logged into that are gonna be a pain in the ass to recover access to should i wipe the phone clean. Eventually i got tired of waiting and instead of just resetting my phone i got the dumb idea to try and recover a full working twrp backup i had made a month ago. After recovering the backup my screen turned back on. I was proud of myself till i realized i had lost my network signal. upon going into my about page in settings i discovered my baseband and imei values were null/empty. I started to panic since i knew what loosing your imei and baseband permanently meant. But i also quickly remembered that the twrp backup i made was a full backup including my efs and baseband folders. so thought maybe trying to recover those partitions alone would solve it. i have tried severally but my network still isnt working and my baseband and imei values are still null. i dont want to panic because i have my baseband and nfs backups. i read online that twrp sometimes can **** up when installing the recoveries and that some simple line codes in the twrp terminal can help correct the error. but unfortunately the code lines they gave in the tutorial i found doesnt seem to work for the s9. Can someone help me out here? at this moment i am out of options. i was thinking of flashing a stock firmware with odin to see if that helps but i dont want to go further without advice from a third arty. been going forward alone for a while now. i dont know if what i keep doing are actually helpping or worsening my case.
drickles said:
Been using the soldier andriod 9 rom for a while now. was using my phone yesterday when it went off suddenly. turned it back on and got greeted with the black screen of death ((BSoD). I tried every trick available to try and get the screen to turn back on but nothing worked. I was hesitant to reset my phone because i had a lot of important accounts i got my phone logged into that are gonna be a pain in the ass to recover access to should i wipe the phone clean. Eventually i got tired of waiting and instead of just resetting my phone i got the dumb idea to try and recover a full working twrp backup i had made a month ago. After recovering the backup my screen turned back on. I was proud of myself till i realized i had lost my network signal. upon going into my about page in settings i discovered my baseband and imei values were null/empty. I started to panic since i knew what loosing your imei and baseband permanently meant. But i also quickly remembered that the twrp backup i made was a full backup including my efs and baseband folders. so thought maybe trying to recover those partitions alone would solve it. i have tried severally but my network still isnt working and my baseband and imei values are still null. i dont want to panic because i have my baseband and nfs backups. i read online that twrp sometimes can **** up when installing the recoveries and that some simple line codes in the twrp terminal can help correct the error. but unfortunately the code lines they gave in the tutorial i found doesnt seem to work for the s9. Can someone help me out here? at this moment i am out of options. i was thinking of flashing a stock firmware with odin to see if that helps but i dont want to go further without advice from a third arty. been going forward alone for a while now. i dont know if what i keep doing are actually helpping or worsening my case.
Click to expand...
Click to collapse
I have same issue after upgrading to UAEGT3 and now signals are gone. Following this thread for resolution.