Related
UPDATE: So I just finished finals and drinking and have gotten around to my phone. I downloaded Galaxy S Unlock, but a beta version (it has a 'Signal Fix Problem' tab) that I was (and still am) and bit worried about. Well, my fears were quelled and I used it with an internet connection while on Bionix 1.3.1 and it didn't work on the initial reboot. Said the phone wasn't registering on the network. Didn't work on the second reboot. Didn't say anything, but data didn't work. I rebooted again and OMG OMG OMG OMG OMG it worked.
Glad to be back! Time for the latest CM7 nightly!
OLD:
The quoted posts fully explain my issue.
UPDATE:
Hung0702 said:
So I can confirm that the phone works for T-Mobile SIMs and gets 3g to boot. I relocked and unlocked my phone (both by manually changing the nv_data.bin and then with 'Galaxy_S Unlock'). Neither helped. In fact, Galaxy_S Unlock returned FFFFF as the SIM unlock code.
This leads me to believe that this is definitely not a hardware issue and definitely an issue with the EFS. I'm assuming that a proper EFS would not return a SIM unlock of 'FFFFF'.
If anyone has an intimate knowledge of our phones' EFS, please tell them that I need help in that regard. Or RIL, although I think RIL is in the EFS partition.
I'm on JFD via Odin and checked EFS Clear.
Click to expand...
Click to collapse
SUMMARY: I am currently bone-stock. JFD with root and nothing else. I usually get 3G (I live in the city) and excellent reception and speeds. Right now, I get good reception, but absolutely no data, nor can I call or text. It's stuck on GPRS and occasionally switches to EDGE for some reason, but it doesn't make a difference because I still can't call or text on either. IMEI shown in the settings matches that which is labeled behind the battery. My two fears are that the radio itself is somehow physically broken or that AT&T blocked my IMEI (tried other AT&T SIM cards and none of them would work). My SIM worked in other phones). Talked with an AT&T rep, he assured me that it is not AT&T's policy to ban IMEIs. Also, it may have to do with the EFS, but I'm not sure how to access it. Can't download ROM Manager right now because there's no WIFI around.
Does anyone have any suggestions? I'm pretty desperate right now. I'm borrowing a dumbphone and it's absolute torture to text on a 10-key num pad.
Hung0702 said:
MAJOR PROBLEM:
So right after I left such a sterling recommendation of this kernel last night, I started listening to some music, hit pause, left the ear buds plugged in, and went to sleep.
I awoke this morning to no missed calls, no texts, no emails. I was confused and looked at the signal meter and saw a small 'x' next to the bars. I installed the new CM7 (from scratch), and my signal problems persisted.
I just used Odin to get back to JK2 (Froyo) and still I have NO SIGNAL!!! I normally have full bars.
Does anyone have any recommendations? I don't know if everything I wrote is significant, but hopefully the extraneous details could help someone give better insight into this issue.
Click to expand...
Click to collapse
Hung0702 said:
Definitely not the SIM card. It works in other phones. I just wiped everything on the phone using CWM and the problem still persists. My fear is that the radio may have been in full-use all night without my knowledge and burned itself out. Although I'm not even sure if that's possible.
Strangely, I received 1 text message not too long ago. Couldn't reply, however; and still can't make/receive phone calls or access the internet.
Anyone aware of a way to do a complete reset of my phone? I don't think CWM and Odin are doing the trick. It needs to be absolutely bone-stock.
Click to expand...
Click to collapse
Hung0702 said:
nickmcminn60 said:
A simpler way is to:
1) odin to JFD with Repartition and efs clear checked and auto reboot UNCHECKED
2) unplug and replug usb then load ''Eugenes Froyo'' in PDA
3) Load same 512 file you used for JFD
4) Uncheck...auto reboot, repartition, and EFS clear
5) Hit start
6) when complete unplug the usb and plug it back in
7) load JFD and 512 pit into ODIN
8) Check repartition,efs clear and auto reboot
9) Hit start
Click to expand...
Click to collapse
Ok, you got me there. It doesn't do anything. Auto reboot has to be checked. Otherwise it just hangs at SetupConnection...
Thanks for the advice, but it didn't help.
Click to expand...
Click to collapse
Have you tried to flash another modem? or a factory reset? Have you toggled airplane mode and data connection? I had a very similar problem not too long ago. I flashed 4 or 5 roms and they all had the same problem. Flashed a few modems and nothing. Then I flashed one of Eugene's roms and it wiped my phone and it seemed to work after that. It could have been a coincidence, I'm not sure. I spent a whole day working on and it seemed to fix itself when it wanted to. Just keep flashing roms and tinkering and see what happens.
Hung0702 said:
The quoted posts fully explain my issue.
SUMMARY: I am currently bone-stock. JFD with root and nothing else. I usually get 3G (I live in the city) and excellent reception and speeds. Right now, I get good reception, but absolutely no data, nor can I call or text. It's stuck on GPRS and occasionally switches to EDGE for some reason, but it doesn't make a difference because I still can't call or text on either. IMEI shown in the settings matches that which is labeled behind the battery. My two fears are that the radio itself is somehow physically broken or that AT&T blocked my IMEI (tried other AT&T SIM cards and none of them would work. My SIM worked in other phones). Also, it may have to do with the EFS, but I'm not sure how to access it. Can't download ROM Manager right now because there's no WIFI around.
Does anyone have any suggestions? I'm pretty desperate right now. I'm borrowing a dumbphone and it's absolute torture to text on a 10-key num pad.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1045713&page=4
Refer to my post #33
Sent from my SGH-T959 using XDA App
deadpass said:
Have you tried to flash another modem? or a factory reset? Have you toggled airplane mode and data connection? I had a very similar problem not too long ago. I flashed 4 or 5 roms and they all had the same problem. Flashed a few modems and nothing. Then I flashed one of Eugene's roms and it wiped my phone and it seemed to work after that. It could have been a coincidence, I'm not sure. I spent a whole day working on and it seemed to fix itself when it wanted to. Just keep flashing roms and tinkering and see what happens.
Click to expand...
Click to collapse
rubbamade said:
http://forum.xda-developers.com/showthread.php?t=1045713&page=4
Refer to my post #33
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks for the directions, but it didn't help
I've flashed many different modems. Tried KA7 and stock for 2.3; JK2 for 2.2; and JI5 for 2.1. Nothing helps. Does anyone know how I would go about checking my EFS partition if I had a root explorer? How would I know that it was normal? What symptoms would suggest a problem? I wouldn't be able to browse it right now, but I may be able to tomorrow.
@deadpass
Could you try a tad harder to recall which of Eugene's ROMs you used? I tried his JK2 base to no avail. Do you know if his 'Froyo that doesn't brick' is any different?
Hung0702 said:
@deadpass
Could you try a tad harder to recall which of Eugene's ROMs you used? I tried his JK2 base to no avail. Do you know if his 'Froyo that doesn't brick' is any different?
Click to expand...
Click to collapse
It was Eugene's 2.2.1 rom, GCR3.
Bumping. I hope everyone understands. Going from Android to a dumbphone (DURING FINALS, TOO) is terribly inconvenient and disheartening.
Looks like I'm giving up. I'm really busy with Finals and don't have time to learn everything required to figure out how to fix my phone. No one is informed enough about EFS or RIL to point me in the right direction. I've really enjoyed having this phone since August, and I'm definitely going to miss the ROMs and enthusiastic community. Not sure what to do now. I planned on keeping the Vibrant and selling whatever I upgrade to in August. Still going to have to sell, but I don't get to keep the Vibrant
Good luck with your Vibrants!
Before you give up, do you mind trying my Back to stock guide verbatim... it's in my signature. Would like some feedback. It certainly would not hurt. No reason I can see why we can't fix your phone.
Shoot, send it to me and I'll send it back if you can't find time.
Wait, so this will get you to stock JFD on the Vibrant... but you said you are on AT&T... are you unlocking it again after you go back to stock?
I do not do this, but first google result:
s15274n said:
Before you give up, do you mind trying my Back to stock guide verbatim... it's in my signature. Would like some feedback. It certainly would not hurt. No reason I can see why we can't fix your phone.
Shoot, send it to me and I'll send it back if you can't find time.
Wait, so this will get you to stock JFD on the Vibrant... but you said you are on AT&T... are you unlocking it again after you go back to stock?
I do not do this, but first google result:
Click to expand...
Click to collapse
Hey! Kind of in awe to see you in my thread! Followed your guide ~10-15 time I had to flash. I've actually flashed via Odin probably 25-30 times since Saturday. Played with ALL the settings and your guide is good. No room for improvement!
Anyway, I've been using essentially the same procedure. Used Repartition and EFS clear on a few runs, but nothing different that I didn't intend to have a purpose. I used the files posted here; the MD5 sums check out.
People have been telling me it's a hardware problem (i.e. my modem is dead). While fully possible, I find it unlikely since I haven't seen a single dead modem post in any part of the Q&A, nor have I heard any suspicions of possibly failing modems. I could just be the lucky one, but again, that sounds unlikely.
Took my phone apart just to make sure all the connections are solid. SIM card board is securely connected to the antennae. Need to get an ammeter to ensure an electrical connection, though.
So I can confirm that the phone works for T-Mobile SIMs and gets 3g to boot. I relocked and unlocked my phone (both by manually changing the nv_data.bin and then with 'Galaxy_S Unlock'). Neither helped. In fact, Galaxy_S Unlock returned FFFFF as the SIM unlock code.
This leads me to believe that this is definitely not a hardware issue and definitely an issue with the EFS. I'm assuming that a proper EFS would not return a SIM unlock of 'FFFFF'.
If anyone has an intimate knowledge of our phones' EFS, please tell them that I need help in that regard. Or RIL, although I think RIL is in the EFS partition.
I'm on JFD via Odin and checked EFS Clear.
if you did the efs backup to flash cm7 shouldn't you be able to put that back on your phone??
Nothing will work until you follow this thread:
http://forum.xda-developers.com/showthread.php?t=761045
It helped me when I cleared my EFS
EFS contain network information like network lock, etc...
Good luck.
Exactly what I was getting at, odin and then unlock.
neobuddy89 said:
Nothing will work until you follow this thread:
http://forum.xda-developers.com/showthread.php?t=761045
It helped me when I cleared my EFS
EFS contain network information like network lock, etc...
Good luck.
Click to expand...
Click to collapse
Thanks for replying. That's actually the thread I followed in order to pull the nv_data.bin and use Galaxy_S Unlock. But like I was saying, it's as though the EFS is not working properly. I pulled the nv_data.bin and it looked like the phone was already unlocked (I'm assuming it is, because it never asked me for the SIM unlock code). I changed the nv_data.bin to locked (by changing the hex value at 181469 from '00' to '01', after which it did begin asking for the SIM unlock code), then used Galaxy_S Unlock to unlock. I also tried to retrieve the unlock code using Galaxy_S Unlock and all I got were a bunch of F's, not what I was expecting.
s15274n said:
Exactly what I was getting at, odin and then unlock.
Click to expand...
Click to collapse
Please read above.
^ really unknown territory for me. Did you restore your EFS, I assume you can since you backed it up.
I saw this great thread from BT... maybe someone has an answer in there.
http://forum.xda-developers.com/showthread.php?t=1000962
I'll keep checking in to try and learn... EFS/unlocking is really not common to me, hopefully someone can chime in and well all learn something.
Hung0702 said:
Thanks for replying. That's actually the thread I followed in order to pull the nv_data.bin and use Galaxy_S Unlock. But like I was saying, it's as though the EFS is not working properly. I pulled the nv_data.bin and it looked like the phone was already unlocked (I'm assuming it is, because it never asked me for the SIM unlock code). I changed the nv_data.bin to locked (by changing the hex value at 181469 from '00' to '01', after which it did begin asking for the SIM unlock code), then used Galaxy_S Unlock to unlock. I also tried to retrieve the unlock code using Galaxy_S Unlock and all I got were a bunch of F's, not what I was expecting.
Click to expand...
Click to collapse
Dont use Galaxy_S unlock app. It gave me same bunch of F's.
Try unlocking again changing 01 to 00 and adb push.
Look up a youtube video on unlocking your device!
exchange it
neobuddy89 said:
Dont use Galaxy_S unlock app. It gave me same bunch of F's.
Try unlocking again changing 01 to 00 and adb push.
Click to expand...
Click to collapse
Yeah, I did unlock it again but there's still an issue with AT&T SIMs. T-Mobile works fine, but AT&T SIMs don't work and it doesn't ask for an unlock code.
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
pnz said:
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
Click to expand...
Click to collapse
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Benko111 said:
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Click to expand...
Click to collapse
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
EDIT2: And another correction. IMEI and serial showed fine after losing service, but I then rebooted the phone. Still no service, baseband is now unknown, IMEI is null and the serial number is non-zero but different than it was. However, I'm sure if I reflashed the ROM again I'd have service for a few minutes, so it doesn't seem like the EFS is entirely corrupt. I'm scratching my head a bit at this one.
pnz said:
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
Click to expand...
Click to collapse
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Benko111 said:
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Click to expand...
Click to collapse
Not generic IMEI but null IMEI. Not sure about generic serial, not sure how to tell the difference. And I'm now seeing the same on the NZ stock firmware after a reboot.
Is a Philz Touch EFS backup sufficient? Anything else I should backup as well?
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Benko111 said:
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Click to expand...
Click to collapse
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
pnz said:
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
Click to expand...
Click to collapse
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Benko111 said:
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Click to expand...
Click to collapse
Sorry, just meant that I thought somebody might have seen this exact problem before.
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
pnz said:
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
Click to expand...
Click to collapse
No, not fixed. Worked fine for a few days then the problem came back. Just tried a non-stock ROM (Omega) and same thing. Trying a CM-based ROM now (ParanoidAndroid), but not too hopeful.
Still don't understand why it works for hours/days, then suddenly stops. Rebooting it fixes it the first few times, then that stops working as well (and I get baseband unknown at this point). Flashing a new ROM always fixes it, for a few hours/days anyway.
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Any workarounds you can suggest? Just had the problem happen again on cyanogenmod, so that didn't fix it.
Try reading the freezing thread in general forum, see if the memory test tool will compete after a full wipe and fresh install of a stock firmware.
Other than that only a new motherboard, as the emmc chip is damaged.
Hello all,
My partner bought a Galaxy S3 (GT-i1900) International (I live in the UK) off a friend .
We noticed that the network connection periodically failed. I noticed that the software was some of the earliest on this phone, and so i thought I'd better update it, as it was suggested that sometimes if the phone is running some of it's earliest software it can cause problems with the network connection, and as it works 95% of the time, surely it can't be the antenna? I went to software update and tried to update it there, it's then I realised the phone had been rooted, and even Kies would not update it. I came to the conclusion that perhaps my friend had tried to mess with the phone some how, and may have caused this network problem, or perhaps was trying to cure it? Who knows
I decided to flash the latest stock rom (i9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5) I found on Sammobile. Everything went well, the phone booted up perfectly, the only minor worry being that the first screen was in Polish, quickly remedied by changing the language to English UK. All seemed fine, until we tried to make a call. it was then we realised that there was no network connection whatsoever. I tried other sim cards with other networks - still no connection. It only shows the signal bars.
I read the forums for a couple of days and tried:
Going in Network Settings and searching for my network, 3, which it found amongst all others. it said 'Registered on Network' but then immediately flashed up '3 network not connected' or similar. fail.
Installing CWM recovery, then flashing the 2 modem zips (DDEMG2 & XXDME4) all went fine, but the phone still says 'disconnected' under Device settings Mobile network state
Using the Ariza patch. I tried this, but on the last step where it says 'just click patch' mine gets stuck on a downloading state, possibly as I'm using a stock rom I read some kernel has to be changed first? - Beyond me.
It was then I decided to scrutinize every difference between my working S3, exactly same phone on same network, and my partners.
The IMEI number was correct, something I see people have problems with. The signal strength reading are the same, suggesting the antenna at least is fine.
The serial number - Now this is the ONLY thing I can see that seems to have been changed, from the correct format, to one starting with 4df1 ...... Is this the problem, that has made the phone not register with network? In the UK phones are not locked into a specific phone number /contract and so I don't see how the network would decline a differing serial number?
Anyway that's where I'm at a phone that has no network connection, with a differing serial number.
Any help would be GREATLY appreciated.
extra[/ATTACH]
Screenshots of the device status in case that helps . SCREENSHOTS REMOVED DUE TO PRIVATE INFO
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
ricrea said:
extra[/ATTACH]
Screenshots of the device status in case that helps .
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
Click to expand...
Click to collapse
Go to Samsungmobile and download 4.3 BTU ( it's for Uk,simfree phones.) Flash via Odin,maybe that will help
Sent from my GT-I9300 using XDA Free mobile app
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
ricrea said:
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
Click to expand...
Click to collapse
I don't think so since setup started in Polish
Sent from my GT-I9300 using XDA Free mobile app
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
ricrea said:
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
Click to expand...
Click to collapse
You mean Pda,Csc and Modem are the same? Or md5 is the same?
Sent from my GT-I9300 using XDA Free mobile app
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Report back if you get your network back:thumbup:
Sent from my GT-I9300 using XDA Free mobile app
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
tallman43 said:
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
Click to expand...
Click to collapse
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
ricrea said:
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
Click to expand...
Click to collapse
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
tallman43 said:
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
Click to expand...
Click to collapse
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
ricrea said:
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
Click to expand...
Click to collapse
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
tallman43 said:
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
Click to expand...
Click to collapse
That was my thinking, the IMEI isn't corrupt yet so I thought best to back up what I have. Ive also backed up using CWM.
Im now trying to flash the proper version of 4.3 for my unlocked uK S3, so im at least using the correct os.
Im flashin zip from cwm, but when i select it on my sd card, it says the following:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Any ideas why it won't install? Iv'e been Googling it
for 2 hours.
cheers
update - I spent ten hours downloading the proper rom 4.3 btu uk unlocked one, finally flashed it using mobile odin.....
started in Polish again - with no network. I think that this is standard.
Next, I am going to try to flash the patched modem.
tallman43 - do you think my strange serial number needs to be corrected? Is this possible or necessary?
Many thanks - one very tired migraine creating finger-nail biter.
Update:
I finally got the phone to work by following the instructions on the page below;
http://forum.xda-developers.com/galaxy-s3/help/guide-fixing-gt-i9300-network-4-3-stock-t2609635
The patched kernel didn't work on it's own, but the kernel I installed from this thread, along with the other two files, seemed to work, and though the phone is now registered using a much better Android 4.3, it still disconnects every now and again forcing a restart. I really wish I could work out why it does this, I'm starting to believe it may be a hardware issue now.
Is there a program that I could use to test the part of the phone that malfunctions and loses signal completely, to try and work out what is happening when the phone suddenly loses all signal and shows only a circle with a line on it (no sign)
Many thanks to all the people who helped me with this I really appreciate it.
I want to close this thread now as what I require now is off topic from the original post so many thanks for your help people.
Hy everybody. I'm here to took with you about a common problem on samsung s3. One week ago i notice that i can't receive calls, messages etc and i found the "not registered on network" problem. What actually i want to say, is the fact that it appear suddenly, my phone always have 4.3, i didn't upgrade nothing....the problem persist, i changed sim, modem.bin, flash 4.1, modified network connections from setting....nothing work!!! I always have signal but that's all....what can i do more? (and my imei has changed to this: 00499*******
international variant
Perseus said:
Can you please let us know if you have international variant or US Variant ? If US then which carrier please ?
Click to expand...
Click to collapse
My phone is a international variant, made in Vietnam, i also tryed to flash 4.1.2 I9300XXEMG4, so then i can flash MG4 modem which can still read the modified EFS...if it is modified, but didn't work.., i think i need to send the phone to a gsm/service, but maybe you guys can help me without cost me money..
Perseus said:
I will request to have your thread moved to appropriate forum.
Click to expand...
Click to collapse
thx man, i hope someone knows how can i solve the problem.
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
I suspect he allowed the battery to run out, which corrupted the efs partition, as he says his phone was on 4.3 and didn't change anything until after the problem happened.
Flashing latest stock firmware is the first step, as suggested above, but I think the OP may have to pay for a repair. Make sure it works on 4.3 before you accept the bill.
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
contactmsd said:
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
Click to expand...
Click to collapse
I was on 4.3 version, i didn't do nothing, i even not installed the root/cwm....the problem appeared from nothing...right before i change my battery. I tried with my region stock rom (4.1.2;romania) and with 4.3 stock ROM but didn't work.
Today i let the phone on a service....i told her what is the problem and i hope there's nothing to do with motherboard. Anyway, please let me know if there's something else to do while i wait 3-4 days for the answer
Spike97 said:
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
contactmsd said:
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
Click to expand...
Click to collapse
I already replaced it.
Fixed
Hi everybody, i finally sent the phone to service and they fixed it for 17€; everything ok, no problem occurred...i flashed stock 4.3 ROM, then CWM and SU, but....then....after one day of use, i forgot to shut down the phone and, again, removed the battery with the screen on....i connected quickly the battery and the phone started without press any button.....and then, surprise!!! Me trying to make a phone call: "Not registered to network"...fu**...but IMEI was still alright(w t f?). Third day i sent again the phone to the service and they told me that i am playing whit the soft (what man? just because i flashed CWM and SU? damn), i told them again what i do with the battery and they said is not true (now what i am supposed to do? they don't trust me) but fixed it again free..for first and last time. Now here is the question: what i need to back up in case that will happen again? It can't be fixed with a backup of IMEI/Modem file...
Go read the sticky thread in general forum.
Hi,
I have the Verizon LG G3 on Android 6.0 and it frequently loses connection with the SIM card, saying "SIM Card not readable" or "No SIM found" in the notifications. A reboot can temporarily fix the problem, but the phone always encounters the problem while booted. I don't know if this is a hardware or software problem or what can be done to permanently fix it.
Thanks for any help or input!
Hi!
You've probably already thought of this, but have you tried taking the SIM card completely out and then re-inserting it, making sure it's in all the way?
Are you rooted or non-rooted? If rooted, try restoring to 100% stock unrooted. If you plan on rooting after confirming if that fixes it, stick with the 10B TOT and then confirm if the problem still occurs. You might want to try the 10B TOT anyway because flashing TOTs can fix weird problems that flashing KDZs or ROMs can't. TOTs flash more partitions than KDZs.
Lastly that I can think of, a few others on this phone have had the same trouble and found that when they took the phone/SIM card to Verizon and they replaced the SIM card with another one for them, the problem was fixed. So the trouble might be a flaky SIM card.
Good luck! Let us know how things work out.
I too have the same issue. Got a replacement sim card sent to me last week. That didn't fix the problem. LG sent me a replacement phone Monday June 27th 2016. Worked flawlessly those 2 days I had it. Now this morning in wake up to. "Sim card not found" a simple shutdown and remove the sim card and reinsert it worked. But this is exactly how this problem started before. Could get by with doing that for about a week. Then my old phone wouldn't even recognize there was a sim card installed. Help if anyone has any answers. Verizon can't seem to figure anything out.
I have the same problem as well. Exact same. Haven't got around to buying a new sim card and I am glad.
JTlane16 said:
I have the same problem as well. Exact same. Haven't got around to buying a new sim card and I am glad.
Click to expand...
Click to collapse
From what I've read of others' experiences, Verizon users were able to exchange their faulty one for a good one at a store. Of course if you're not using a Verizon SIIM or you're out of the country...
I'm having the same issue. I have tried different modems/bootstacks and that hasn't worked. I guess I'm going to try the TOT and report back if that fixes it.
Also,I haven't tried a different sim. It actually hasn't recognised the sim in a long long time. I've used an LG V10 as my DD since January so haven't needed my G3 to work but I really want to get this thing working again.
imucarmen said:
I'm having the same issue. I have tried different modems/bootstacks and that hasn't worked. I guess I'm going to try the TOT and report back if that fixes it.
Also,I haven't tried a different sim. It actually hasn't recognised the sim in a long long time. I've used an LG V10 as my DD since January so haven't needed my G3 to work but I really want to get this thing working again.
Click to expand...
Click to collapse
Good luck! Keep us updated. If the TOT doesn't work are you going to try exchanging your SIM? If you're using the same SIM in a different device and it's fine, then in your case it might not make a difference unfortunately.
roirraW "edor" ehT said:
Good luck! Keep us updated. If the TOT doesn't work are you going to try exchanging your SIM? If you're using the same SIM in a different device and it's fine, then in your case it might not make a difference unfortunately.
Click to expand...
Click to collapse
Actually i just got it working again. I'm on the latest release of Bliss and started on the 35b modem. I flashed back to the 24b and the sim still wouldn't work. So then I flashed back to the 35b, wiped dalvik and cache, and now it's working. Not sure if it's going to stay working but I made some calls and everything seems in order so far.
My G3 started doing the same thing about a month ago. Tried flashing about 3 new roms to no avail, and the final ROM hard bricked my phone. Had to JTAG to get back to soft brick then TOT recovery to get back to system. IMEI is null (all zeros) and I still receive SIM error. It all started a few weeks after flashing a custom marshmallow rom (don't know if it was related directly). I had to get a replacement in the meantime but I would really like to get my G3 back in working condition. Any suggestions?
mc1175 said:
My G3 started doing the same thing about a month ago. Tried flashing about 3 new roms to no avail, and the final ROM hard bricked my phone. Had to JTAG to get back to soft brick then TOT recovery to get back to system. IMEI is null (all zeros) and I still receive SIM error. It all started a few weeks after flashing a custom marshmallow rom (don't know if it was related directly). I had to get a replacement in the meantime but I would really like to get my G3 back in working condition. Any suggestions?
Click to expand...
Click to collapse
If you don't have a TWRP backup of your EFS (which includes the IMEI) then you'll have to search XDA and/or the G3 sections for the directions, which involves proprietary software used on Windows, and you'll have to know what your IMEI was (on the original box, might be on some paper record, your carrier might know the old info).
roirraW "edor" ehT said:
If you don't have a TWRP backup of your EFS (which includes the IMEI) then you'll have to search XDA and/or the G3 sections for the directions, which involves proprietary software used on Windows, and you'll have to know what your IMEI was (on the original box, might be on some paper record, your carrier might know the old info).
Click to expand...
Click to collapse
I do have a few TWRP backups, do full backups include EFS? I still have the IMEI (on sticker in phone) so I can do some searching for a tool to reset it. What I've seen seems fairly in-depth (hex editor) but if it'll work I'll have a go at it.
mc1175 said:
I do have a few TWRP backups, do full backups include EFS? I still have the IMEI (on sticker in phone) so I can do some searching for a tool to reset it. What I've seen seems fairly in-depth (hex editor) but if it'll work I'll have a go at it.
Click to expand...
Click to collapse
That's why TWRP is the easiest way to restore.
I don't know what you consider "Full". When you do backups and restores it lists all the partitions and defaults to whatever you backed up last, but you can select and deselect partitions as you wish.
I keep a backup of only the EFS for all three of our devices on Google Drive for just in case.
Just try a restore and see if it lists EFS as one of the partitions you can restore. If not, don't bother. If it does, deselect all other partitions and only select EFS to restore that.
roirraW "edor" ehT said:
That's why TWRP is the easiest way to restore.
I don't know what you consider "Full". When you do backups and restores it lists all the partitions and defaults to whatever you backed up last, but you can select and deselect partitions as you wish.
I keep a backup of only the EFS for all three of our devices on Google Drive for just in case.
Just try a restore and see if it lists EFS as one of the partitions you can restore. If not, don't bother. If it does, deselect all other partitions and only select EFS to restore that.
Click to expand...
Click to collapse
Really beating myself up, I could have sworn that when I took backups I selected every single box. I had 3 TWRP backups and none had EFS partitions included. I guess I'll have to find another way.
mc1175 said:
Really beating myself up, I could have sworn that when I took backups I selected every single box. I had 3 TWRP backups and none had EFS partitions included. I guess I'll have to find another way.
Click to expand...
Click to collapse
Oh, sorry to hear that! For what it's worth, you could take a look at the new thread posted in the General section with "DIAG" in the thread title. I've never had to restore my IMEI by any method, but the OP says that his findings might help with restoring the IMEI, although I know he mentions QPST which I believe is what others used to manually put their IMEI back in too, so I have no idea if there's a difference or improvement to it with what he reveals. I know there are other threads in either the Verizon G3 General and/or Q&A sections or the non-Verizon sections having to do with restoring IMEI using the Windows software. Good luck in your quest.
roirraW "edor" ehT said:
Oh, sorry to hear that! For what it's worth, you could take a look at the new thread posted in the General section with "DIAG" in the thread title. I've never had to restore my IMEI by any method, but the OP says that his findings might help with restoring the IMEI, although I know he mentions QPST which I believe is what others used to manually put their IMEI back in too, so I have no idea if there's a difference or improvement to it with what he reveals. I know there are other threads in either the Verizon G3 General and/or Q&A sections or the non-Verizon sections having to do with restoring IMEI using the Windows software. Good luck in your quest.
Click to expand...
Click to collapse
That article worked like a charm! IMEI restored just like it said. Oddly enough the SIM card still seems to eject randomly (no sim error), but the phone can now make calls and when the error does occur a reboot usually fixes it. At this point it's seeming like a hardware problem, but the only method I have of testing that is sending it back to LG which is an idea I'm not particularly fond of. I've done a bit of looking around and it seems I'm not nearly the only one with this issue on the G3:
https://www.reddit.com/r/LGG3/comments/4edhs1/sim_not_readable_and_no_sim_found_vs985/
https://community.verizonwireless.com/thread/832587
Both of those were just for the VS985, let alone dozens of others for the T-mo and ATT variants. Not sure whether to be relieved or disappointed but I suppose I'm at the next step. Any other info would be helpful.
mc1175 said:
That article worked like a charm! IMEI restored just like it said. Oddly enough the SIM card still seems to eject randomly (no sim error), but the phone can now make calls and when the error does occur a reboot usually fixes it. Any other info would be helpful.
Click to expand...
Click to collapse
A lot of people with this trouble solved it by exchanging their SIM card at a Verizon store. As far as I know it was free to do so. However, there have been others for whom this didn't solve anything.
It's funny, this thread was started by someone else and others besides you had commented with the same issue but only one of the four others has followed up after suggestions are made.
Make that EFS backup and store it securely!
well if someone solved the SIM problem i would love to hear it,i have been thru 4 SIM cards,2 brand new vs985 and all of them have the exact same problem,i was soo worried i screwed up my phone(was rooted) that i unrooted,stated all over again with 10b,in between rerooting i lost the SIM signal,long story short,im on my 4th phone and have the sdame problem again,,yes i am stock 48a,and verizon claims only the lg4 has been troubled with the SIM card....still got 1 more year of the vs985 so kinda searching for a solution.as i said i was worried it was my flashing too much or anything to do with that but since this phone is 4 days old,with a new SIM i am at a total loss...thanks...
same probblem here...started few days ago on my G3....wtf
bad news from lovely verizon, told me the update added security which conflicts with the SIM, so today i got my 5th phone in 10 days, honestly sick of the guess game from verizon, 5 SIM cards, 5th phone, dont even know who to trust, i spent 3 days wiping my phone from jasmine thinking i messed up, down graded to 10b,then took ota updates all the way to 48a,so verizon wouldnt bag me, and then they give me 4 more phones with the exact problem, now todays phone lasted 4 hrs and i list SIM again...
fropalace said:
Hi,
I have the Verizon LG G3 on Android 6.0 and it frequently loses connection with the SIM card, saying "SIM Card not readable" or "No SIM found" in the notifications. A reboot can temporarily fix the problem, but the phone always encounters the problem while booted. I don't know if this is a hardware or software problem or what can be done to permanently fix it.
Thanks for any help or input!
Click to expand...
Click to collapse
I had same issue, but i could fix it by doing this