Related
I have a quick question because I've run into a problem I can't seem to fix.
First, so everyone knows what I'm dealing with:
Phone: i717
Changes: Rooted (Shows super user access), CWM v5.5.0.4, Unlocked (Tested)
Rom: Stock AT&T Rom
Sim Card: Works in a T-mo branded Exhibit II 4G.
I flashed a radio (tried KID, 0331122 from the radio thread in the dev section, and reflashed the original AT&T radio).Even w/ the original radio installed, it cannot seem my T-Mo sim now.
Do I need to flash a new Rom or what? Wipe data to factory reset?
I would rather not change anything w/o asking since flashing radios seems to be a straight forward thing that most ppl have done w/o touching the rom.
Thanks ahead of time.
Mine worked with a rooted stock rom at first it didnt see the sim then i tried searching the network under wireless and networks it took a few minutes but then it came up.
Sent from my SAMSUNG-SGH-I717 using xda premium
don't forget if you are running an ICS based ROM you need an ICS based Radio/modem.
EDIT: i see you're running the original GB rom so you need the GB radio.
give it a few minutes to find a signal or go to settings/mobile networks/network operators. choose manual. then let it search a few minutes. then select t-mobile.
I find the Blaze 4G radio worked best for me, but depending on your area, your results may differ. try em all.
You guys are insanely fast.
I'm currently on the stock radio & I'm still getting the same message after letting the sim sit in the phone for 9 minutes (yes, I watched the clock, lol):
Insert SIM card to access network services
Click to expand...
Click to collapse
Where should I go from here?
Edit: Is the answer flashing another rom? Maybe something has become corrupt? I don't see how as I've read & re-read walk thrus for doing this to make sure.
I've done a little more reading. Flashing the beta ICS rom flashes to the old AT&T modem.
Would this be the best bet?
Edit: After looking through the "about" phone...
I'm on 4.0.3
Baseband: Unknown............. that's really bad.
Edit 2:
After reading, I needed to back up the EFS. No where is this stated anywhere, unfortunately. That contains IMEI and everything else.
Edit:
So, after reading MORE, the IMEI number is on a sticker behind the battery, along w/ the S/N.
Huh? Efs? I dont even know what that is nevermind backing it up. Goto clockworkmod and flash the radio.zip and reboot. Thats all there is to it.
Sent from my SAMSUNG-SGH-I717 using XDA
madman604 said:
Huh? Efs? I dont even know what that is nevermind backing it up. Goto clockworkmod and flash the radio.zip and reboot. Thats all there is to it.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
If you look up EMEI number related to flashing the radio, there's a lot of hits.
XDA has a thread on it here: http://forum.xda-developers.com/showthread.php?t=1352371
I'm quite shocked it's not mentioned everywhere as this happens to people now and again.
I have my IMEI number, i just don't know how to input it into the phone.
As for flashing the radio, I've flashed 2, then back to the original. To no avail.
Sorry never had anything like that. I would almost odin back to stock and start over. You dont need root for the sim to work on calls and edge with tmobile.
Sent from my SAMSUNG-SGH-I717 using xda premium
If you're baseband is unknown don't worry just flash a stock at&t modem and it should go back to normal. Your imei is under a different menu in about phone..the status one.
Also its no ones responsibility to tell you that modifying your phone may break it.
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesd86 said:
If you're baseband is unknown don't worry just flash a stock at&t modem and it should go back to normal. Your imei is under a different menu in about phone..the status one.
Also its no ones responsibility to tell you that modifying your phone may break it.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I did flash back to the stock AT&T baseband as stated in the original post.
If I go to About Phone, the Baseband Version is unknown.
If I go to Status, the following are listed as
Network: Unknown
Mobile Network: Unknown
Service State: Out of service
Mobile Network State: Disconnected
IMEI: Unknown
IMEI SV: Unknown
I've backed up the EFS that I have no just so it doesn't degrade further. I'll try to flash again and see, but I still think the EFS is borked.
I'll see what I can, but I think I'll the EFS is borked beyond flashing it to normal.
My point about the EFS back up is that most ppl here don't seem to know what it is. It shouldn't be that foreign of a topic since flashing a radio is obviously problematic for some. I've seen other posts concerning no IMEI after flashing radios on forums other than XDA. It's odd that it's not mentioned as a sticky everywhere.
Backing up EFS would solve a lot of head aches from unlocking / radio flashing woes. I'm hoping this info will save a few people a lot of time and money.
After more digging, I came across this thread:
http://forum.xda-developers.com/showthread.php?t=1646326
Synopsis: Basically, he followed the same guide I did. The only difference is that I flashed the radio while using a stock AT&T rom. Once he flashed back to GB (saurom), he gained back his baseband / IMEI.
This is what I cannot figure out:
CWM will see and flash any radio file I push to my note. If I push a stock AT&T rom, it won't see it. If I put the rom in it's own folder, it seems the rom, but states there's no files.
Is CWM corrupted? Why would it only read firmware to flash radios, but not android roms? Should I just go back and install CWM?
I've searched all over & used google, but I can't find a thread discussing this.
Fixed.
This problem has nothing to do with any of the radios corrupting the EFS folder. Albeit, it's always a good idea to back it up.
Flashing back to AT&Ts stock rom (2.3.6 or 4.0.3) never fix the issue. You will always be stuck w/o a radio, at least from what I've seen. Even flashing back to the stock radio fails. I don't know if it changes the EFS, but AT&T's rom does not like it and shows no IMEI & a bogus SN .
I had to go back, flash to saurom and a compatible GB (or beta T-mobile) radio to get te work fine. ICS radios work fine on ICS.
Saurom and GB radios dont work in my i 717 trying to connect to wind. I got a CM 9 ICS build and ive tired a bunch of radios. they all failed. i keep getting no sim errors. I can see the operator but when i select it it times out and says it cannot connect to the network at this time. it also says interset sim. Im positive it is unlocked.
Modems(radios) or basebands should have nothing to do with whatever rom you are running. Whether they are GB, ICS, or JB modems, they should all work to a degree, at least for phone call ability. I have flashed many different radios trying to get the best function of my att note on t-mo. The best I got was using the Blaze modem. That got me 3g hspa.
The worst will be just giving you edge speed. My note is unlocked and has been on JB running blaze ICS modem working fine. Maybe you need to start over, evaluate what you have, and go from there. There are great threads on att over t-mobile. Good luck.
I picked my rom, and started flashing 5 or 6 radios, and found what one worked best on t-mo.
Presently, I have switched back to att- sort of- straight talk. I'm not thrilled with the speeds. No higher than 4 mbps DL, and 1-1.5 UL. Thinking about going back to t-mo and dealing with the slow UL speeds. I'm on an ICS rom with the ucle6 modem.
Also, flashing a rom does not change your modem. You have to physically reflash the modem you want. Some modems show up as unknown under the baseband. Blaze is one of them.
Another thought- sometimes a reboot will get your sim recognized by your phone.
sico987 said:
Saurom and GB radios dont work in my i 717 trying to connect to wind. I got a CM 9 ICS build and ive tired a bunch of radios. they all failed. i keep getting no sim errors. I can see the operator but when i select it it times out and says it cannot connect to the network at this time. it also says interset sim. Im positive it is unlocked.
Click to expand...
Click to collapse
This is yet another case of the "no sim" bug ....
Damn I wish we could find the answer to this issue, but none exist .....and for some users the return to complete stock even fails to recover service ..
g
Really what an incredible unlucky glitch.I got my note for only 360CDN good condition but missing the stylus, even still it was a good buy. I'm on Wind mobile, T-mobile here in Canada. I even gave it to somebody who's done a bunch and they ran into the no sim problem. I guess I'll be going back to my HTC HD2 and sell the note .
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
So just to confirm I have followed the process correctly over 20 times and no matter which cm9 cm10 based rom and any ics or gb based radio will allow connection or recognize the sim to the 1700 aws network. With a cm9 based rom I can see my network, but it will not allow connection like the phone is locked, even though i have unlocked and tested the phone on other networks.
same here
Yes, I have the same 'No SIM' issue with a working WIND SIM. I've tried everything, multiple Radios, multiple ROMs. Very strange problem. I wish we had the tools that the SGSIII has for dumping and restoring the NV ram. Even stranger, I do have a the correct IMEI number in Phone, About. I have a feeling it's something to do with how the phones were carrier unlocked.
http://forum.xda-developers.com/showthread.php?t=1804117
I have made a backup of the EFS folder with EFS Pro. I tried restoring the NV ram from .bak but there was none found.
http://forum.xda-developers.com/showthread.php?t=1308546
tweebs said:
Yes, I have the same 'No SIM' issue with a working WIND SIM. I've tried everything, multiple Radios, multiple ROMs. Very strange problem. I wish we had the tools that the SGSIII has for dumping and restoring the NV ram. Even stranger, I do have a the correct IMEI number in Phone, About. I have a feeling it's something to do with how the phones were carrier unlocked.
http://forum.xda-developers.com/showthread.php?t=1804117
I have made a backup of the EFS folder with EFS Pro. I tried restoring the NV ram from .bak but there was none found.
http://forum.xda-developers.com/showthread.php?t=1308546
Click to expand...
Click to collapse
It has nothing to do with your unlock. If you've followed the steps and are still having no sim issue you may have to get a new 32k sim card from wind the older ones won't connect in a phone with lte
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Had to replace the TMo SIM card with a newer one today. Solved the problem of "No SIM".
I know this is old
I have the same problem with "NO SIM." One day i flashed so many things to my phone and one time i turned it on i got ATT on the top right corner and everything was good. I made some phone calls and texts and even browsed the web. I restarted the phone to check if it was just a fluke and it was. Ever since then i cannot get it to read my phone, but i know for sure the hardware works.
New S3 on UK Three Mobile.
I have an issue that mainly only affects N Irish users I suspect.
Just bought a 3Mobile S3 and I love it. However on 3 firmware, network selection is locked to automatic. I can manually change, but the phone sill change again of its own accord if the signal I chose isn't available.
The reason 3 do it is so that if 3 isn't available, the phone will roam onto Orange's network as a backup. That's all fine if you're in mainland UK! If you're in N Ireland and near the border, you will frequently roam onto Irish networks and run the risk of charges for receiving calls.
Last time I had an android phone I got the firmware flashed and this solved the problem. So far, I rooted the phone and installed a custom Rom, Omega. This didn't solve the issue. Am I missing something? Does installing the Rom not also flash the firmware? Or do I have to try a different Rom?
Going to try a stock firmware from here now. Any other advice would be greatly appreciated.
Nobody?
Installed the stock unbranded firmware last night, plus side was the network selection issue is now gone, but the down side is that it seems to have removed my root access.
I I root it again using the threads here, will that overwrite the firmware again?
Flashing a Samsung-ROM will revert all your changes (including root access) and replace the modem. I've heard that Three has it's own modem which works better than the standard on their network, so you might want to flash it (=the modem, not the firmware) on your phone.
Rooting a phone doesn't make you loose any data or change the ROM. Just use CF-Root and you should be good to go.
Thanks. Already used c.f. root again and all is well.
Any Idea where I can fInd the three modem?
Phil Gordon said:
Thanks. Already used c.f. root again and all is well.
Any Idea where I can fInd the three modem?
Click to expand...
Click to collapse
im curious to know too... i've installed a unbranded official rom from three's branded one and if the modem is better i think i'd want to install that too
Every modem has it's own name, so try getting the name from someone who has a stock '3' S3. Then you can google it.
I'm not sure though if they got their own, I _think_ they do
However a network-specific modem must not always be the best.
I've got nearly double throughput over here with the exotic ZNLF2 modem. (Afaik it's Hong-Kong)
So trial-and-error is usually better than just keeping what it was shipped with
For the last two weeks, I've miraculously had 4G LTE working on my vs985 despite using the 35b bootstack and 47a stock firmware (rooted and debloated)
I know it was just on band 4, and the 35b radio disables LTE on non Verizon networks. But somehow, amazingly, it was working anyway even across reboots, cache wipes, flashing zips for xposed, and even TWRP backups/restorations.
But when I removed my SIM card, put it in my old phone, and then put it back in my vs985, I lost 4G LTE!
Here are all the details I can remember, although I don't know what might be relevant or accurate:
Originally, I flashed to 10B stock using the TOT. From there I rooted and installed TWRP and flashed various roms to see what works best. I ended up on CM13, but at that point, my SIM card wasn't being detected at all, and I actually took it to AT&T to check my SIM and it was fine. They told me the phone must have re-locked itself. So I went home and wiped everything but microSD. I flashed the 35b bootstack, vs98547a rooted stock. I set up the phone with my google account and put in AT&Ts NXTGENPHONE APN settings. THEN I flashed a debloat zip (even though it gives you more space if you do it before starting the phone.) When I left the house and my phone disconnected from the Wifi, I had a 4G LTE signal! I had no idea how I got so lucky! When I got home, I made a full backup with TWRP, and kept only the zips I had just used for this setup.
So I got comfortable with the phone for two weeks, and now I'm crushed to have lost LTE! I can still use mobile data if I change my APN settings to "phone" instead of NXTGENPHONE, but it's obviously slower.
I wish I knew exactly why I manged that minor miracle for two weeks. I tried everything again, even flashing TOT, but without luck and I have no idea what perfect storm of events may have affected that magical time.
The zips I saved were: 35b bootstack, rooted vs98547a, and a custom debloat zip. I also saved the 10b radio zip, but I just can't remember if I used it that last time. I can't imagine I did, because obviously it wouldn't work with 47a. But then why did I keep it?
My guess is that somehow I got around the disabling of LTE, perhaps by having something specific flashed to a partition that only TOT can reach? Or maybe an LTEconfig got deleted or modified? Did I somehow hybridize the radios? I heard that maybe autoprime is working on a unified radio that might solve this problem?
Do you guys have any ideas? How did I ever make it work?
I have null imei after update. LineageOS 14.1 for i9300 network services are not running. Is there a solution for this release and post? It is possible to make a development like "Zuluman, ariza", can you do this? I want so much. The only solution to this problem. I live in Turkey. I bought a device IMEI changed from abroad. These problems were solved for 4.4 and before, "Zuluman and Ariza". However, nothing was done for the new releases. Help, thank you
You need a patched modem.
Beamed in by telepathy.
I have it for 4.4. But not for later versions. Required for later versions. I want to install 7.1. Required for 7.1.
I recommend you flash a stock rom and see if the problem still exists.
Lineage os is frequently updated and it is very likely that the build you have has issues with wifi.
Beamed in by telepathy.
I tried to install but I get Error: 7 in the TWRP.
Tried with 3.0.2.2 and 3.1.0
Anyone with this problem too?
I have no cellular data on my Galaxy S3 i9300, with Lineage, though it works fine with Archidroid, which I have installed since. Cell Data worked briefly with Lineage, but now not at all. I believe it might have been triggered by turning off wifi, but not sure. Tried a complete wipe of all caches, data, system, etc. plus a reformat of internal before clean installing lineage-14.1-201727-nightly with GAPPS pico. My IMEI is still intact, so that doesn't seem to be the issue, as cited above.
I have the same problem unfortunately. I just wiped my old stock android from my Galaxy S III and installed Lineage OS 14.1. The installation seems to work well, except that my Sim card is not recognised. When I check "Baseband version" in Settings/Phone Status it tells me "Unknown". I assume it has something to do with the modem driver. Does anybody know where to get the right modem driver?
I tried googling for a modem driver and installing it with heimdall. But then my phone didn't start anymore and I had to reinstall Lineage OS...
Reinstall the stock firmware via odin..
shivadow said:
Reinstall the stock firmware via odin..
Click to expand...
Click to collapse
Do you know where I can find such a stock version? Unfortunately I made a mistake with the recovery backup...
Look at sammobile.com or updato.com for the latest stock ROM.
Thank you! Unfortunately this didn't work... I downloaded the firmware (for Cyprus because the phone was bought in Cyprus) and used Odin to install it but now when I try to turn on the phone it just shows the boot screen (saying Samsung Galaxy S 3) and then goes black... I'm not sure what I am doing wrong here. Perhaps I didn't choose the right firmware, do you know how to find out what exact firmware I should download? I got the phone used, so I am not 100% sure it was bought in Cyprus, perhaps UK but it was bought without a network provider.
audit13 said:
Look at sammobile.com or updato.com for the latest stock ROM.
Click to expand...
Click to collapse
audit13 said:
Look at sammobile.com or updato.com for the latest stock ROM.
Click to expand...
Click to collapse
Is there anywhere I can get a clean unlocked stock rom for the U.S. GT-I9300? I lost mine and had to use a T-Mobile rom from elsewhere. Why is this, or a rom from any U.S. carrier nonexistent on the lists? Thanks!
The gt-I9300 was never sold in the USA so there was never a stock USA rom. The T-Mobile s3 was the sgh-t999.
Is the phone shown as the get-I9300 in download mode?
audit13 said:
The gt-I9300 was never sold in the USA so there was never a stock USA rom. The T-Mobile s3 was the sgh-t999.
Is the phone shown as the get-I9300 in download mode?
Click to expand...
Click to collapse
That statement doesn't make sense to me. I live in California, USA and bought it as an unlocked, no carrier, International GT-I9300 from BestBuy. It never had a carrier logo associated with it originally, but since I had to replace the original rom, it now includes a T-Mobile splash after the Samsung S3 splash.
Yes, it states that its a GT-I9300 in Download mode.
The gt-i9300 international was never sold by T-Mobile USA as it doesn't support LTE in the USA:https://www.gsmarena.com/samsung_i9300_galaxy_s_iii-4238.php.
This is the T-Mobile USA s3: https://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
https://forum.xda-developers.com/galaxy-s3-t-mobile
audit13 said:
The gt-i9300 international was never sold by T-Mobile USA as it doesn't support LTE in the USA:https://www.gsmarena.com/samsung_i9300_galaxy_s_iii-4238.php.
This is the T-Mobile USA s3: https://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
https://forum.xda-developers.com/galaxy-s3-t-mobile
Click to expand...
Click to collapse
Thanks, but I'm not looking for a T-Mobile USA stock rom. I'm looking for the GT-I9300 USA International, Unlocked stock rom that originally came with my USA purchased GT-I9300. From what I understand, local service providers have access to it, but Samsung won't post it publicly, like the others. Hoping someone may have a link to a copy they've found or backed-up from their own USA GT-I9300.
I have never heard of or come across a USA international rom for the gt-i9300.
audit13 said:
Look at sammobile.com or updato.com for the latest stock ROM.
Click to expand...
Click to collapse
I brush three times I9300ZCUBML1, or useless.
lineage-14.1-20180124-nightly-i9300-signed.zip
And brush the rom can not use 5Ghz wifi, but when using the signal I9300ZCUBML1 than my nexus6p weaker, simply can not be used in a stable, so no problem.
Where did you get the ML1 ROM? I don't see it on sammobile.com: https://www.sammobile.com/firmwares/galaxy-s-/GT-I9300/. Since the ROM ends in ML1, it could be a 4.1 ROM. Thanks.
Following is worked for me on my Samsung Galaxy S3 i9300 with LineageOS 14.1:
1. Flash original ROM with Odin. (if at this moment IMEI is not correct use program "Samsung Tool" to manually edit IMEI)
2. In security setting, set SIM card lock to none. (After this you should permanently disable SIM pin request on startup on every new ROM)
3. Flash custom TWRP recovery with Odin.
4. Root phone.
5. Make nandroid backup of EFS using TWRP.
6. Wipe cache, system, boot, data and flash custom ROM (do not reboot system after flash).
7. After flashing custom ROM, restore EFS using TWRP.
8. Flash Opengapps, wipe cache, dalvik cache and reboot system.
9. Set everything up Google account...etc.
10. In options check if IMEI is valid. (If is not, reboot to recovery and try again to restore EFS)
If you don't have working cellular network after flashing custom ROM, read following:
From Play Store install app "Cell Network Reset".
Open app and run "Reset Cell Network". (This step is weird because some times after few minutes i get working network, some times after few seconds. Also some times i need to run "Reset Cell Network" few times in a row to get the network working)
I hope it will work for you
i flashed msm extended and now no matter what phone cant read sim card? all options in settings are greyed out. ive taken out sim card and put back in and not working..ive flashed original stock roms and still nothing. anyone have any idea how i can fix this. tia
bushninja07 said:
i flashed msm extended and now no matter what phone cant read sim card? all options in settings are greyed out. ive taken out sim card and put back in and not working..ive flashed original stock roms and still nothing. anyone have any idea how i can fix this. tia
Click to expand...
Click to collapse
Hey,
Are you certain that you flashed International // EU version firmware with MSM? I'm pretty sure if you're EU, and flashed International, there might be issues with Data providers
i flashed the global version this phone originally was the 1910 Chinese version. would it not have something to do with the efs partition or modemst? ive had a similar issue before on a different phone model it was easy to fix but i just dont know what to do with this one.
if anybody could maybe spare there modem.img files or anything regarding the telephony state that would be so amazing. i think its the modem or the emmc file im not to sure but i need my cell radio services up and running
I have the T-Mobile version and have this issue when I flash any custom rom other than the original Omni rom build. If anyone know how to correct this I would like to know as well
So I had two stock roms both different versions which I always fell back on incase something happened. I've never encountered this issue on this device before so I flashed them and nothing worked and I was looking in this complicated way thinking I'd damaged the EFS partition or the modemst files. After hours I just downloaded another* I think EU stock version and did a flash all.bat and hey presto
Always revert back to original stock ROM