I bought a Note 3 a few days ago, first thing I did was installed TWRP and Magisk then due to the battery life just draining almost instantly on stock firmware I flashed over LineageOS (Latest Oreo) all works great except for it not working with Sim at the moment, IMEI is also gone (Doesn't show in settings) I've tried a few other Roms (Flyme, etc) but mobile data/sim doesn't work on that also, is there any stable builds that do support use of sim?
IMEI as per the faqs restore your backed up EFS folder.
See multiple identical posts.
Most roms support sim as you call it .
Related
I tried to flash miui 6 (stable and developer) and miui 7 (stable and developer) for fixing this problem. With custom rom the phone don't boot
So you tried to flash miui back but the phone won't boot because a custom rom is currently used?
There are only two accepted ways here.
1. Restore your backed up efs partition.
2. Send to oem to repair. They may charge you for a new board.
In my Redmi 2 i have installed a rom of redmi 2 prime for volte feature but after i have installed my original kitkat rom of redmi 2.After somedays when i insert a new sim in my mobile its not reading in my first sim its of airtel and second is of jio so its reading only those sim if i insert except it any other sim it shows no sim card I visited Mi store they are saying your mother board is damage and advising to replace it. I think its IMEI problem sooo pls provide me information that what to do now .
Go to settings>about phone>status and check both IMEI and both SIM. If they are ok, your motherboard cannot be damaged.
Hi guys,
At the beginning thank you for taking a look and spending your time reading it - I'm just trying to be precise.
Just to clarify - I've spent 11 hours yesterday and 10 hours (and counting) today reading and browsing XDA and different forums, searching/figuring out/trying to find solution,
but I think I gave up on my own and will need your help.
Few days ago I bought myself another same Note 3 SM-N9005 (primarily locked to EE, but unlocked with provider), as my old one (which was factory unlocked).
I had issues with signal (after slight water damage a year ago) - not major, but annoying enough to make me get another one.
So I switched to new Note 3 and decided to check new custom ROMs on my old one.
First I installed stock 5.0 - all worked fine, battery life improved etc.
Then tried Fougat rom and AryaMod - and here the problems began. While using one of those ROMs I inserted Polish SIM card.
Message appeared that I'm on roaming, to switch it on/off etc (don't remember what message exactly appeared as I didn't really pay much attention to it at that time)
I recently ordered new pay monthly Virgin SIM card for my partner. When it arrived I've put it in my old Note 3 and "Emergency calls only" message appeared.
I thought SIM wasn't active yet, so contacted Virgin just to be informed that the card is active on their end (I've put it in my new Note 3 and it was actually working).
A bit confused I put my O2 card into old Note 3 and it connected to the network without any problems.
So I started searching for a solution.
I found out that when I searched other networks on my (modified, old) Note 3 it only found O2 - UK, vodafone UK and 3UK.
I checked the same on my new Note 3 and it found O2, vodafone, EE (whose towers Virgin uses) and 3 UK - so all of them.
I thought that maybe EFS, modem, kernel or bootloader have been corrupted/conflicting, so made TWRP backup of my new Note 3 and old Note 3 (for old just to create serial number folder).
Then I replaced old Note 3 backup with new one, so TWRP could find it and restore the whole image from new Note 3, where everything works (Lollipop EE network version).
That didn't do the trick. Restored AryaMod backup - nothing. Old device still comes with "Emergency calls only" when Virgin SIM card is inserted, but it works with O2 card.
I tried different modems, bootloaders.
I checked the IMEI and it's intact.
At the moment I'm back to Stock Lollipop 5.0 [N9005XXSGBPL6_N9005BTUGBOJ1_BTU] and the problem still persists.
When I flashed the stock ROM and inserted Virgin SIM standard pop-up window appeared with network selection where I've chosen obviously Virgin.
When searching now for available networks it comes up again with only O2, Vodafone and 3 - no EE/Virgin.
For some reason it doesn't find/connect to EE towers.
Baseband: N9005XXUGBOJ1
Kernel: 3.4.0-4540543
Build Number: LRX21V.N9005XXSGBPL6
Network: Unknown
Mobile Network Type: Unknown
Service State: Voice: Out of service/Data: Out of service
Mobile network state: Disconnected
Thanks for reading and apologies for long post.
If I missed anything please let me know.
Hope you guys will be able to help and direct me what to do to get it working again
Very difficult to follow your rambling post .
Step one is IMEI the right one .
Two correct baseband and CSC for your network ??
JJEgan said:
Very difficult to follow your rambling post .
Step one is IMEI the right one .
Two correct baseband and CSC for your network ??
Click to expand...
Click to collapse
Sorry, I know it's long and quite rambling. I'll start new thread with just quick explanation.
Answering your question - yes, tried different modems and used EE and BTU firmwares.
Phone was bought factory unlocked (new), so BTU version should work, but it doesn't.
@JJEgan
https://forum.xda-developers.com/galaxy-note-3/help/phone-doesnt-detect-network-operator-t3661897
Please ask a mod to delete this thread .
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Please ask a mod to delete this thread .
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Who is mod in here? Sorry, not very experienced in forum.
Thread can be closed - phone after couple of days eventually connected to the network itself. Weird.
nadaall said:
Thread can be closed .
Click to expand...
Click to collapse
Done.
Razvan
Forum Moderator
Hi,
So I have only 3G connection on my Note 3, can't connect to LTE. I think it broke down a while ago when I was updating MagmaNX to UX10. ROM was working fine so I decided I don't want to break it down further and decided to go on with just 3G. But recently I decided to switch back to RR N by vidwhal, becuase Magma became laggy so I started playing with different modems and the result was either bootloop on older modems or just 3G connection on later ones. Currently I'm on CP_N9005XXUGBPG1 but I tried almost all of modems and BL from this thread https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
It's apparently not ROM dependant as it's broken on both MagmaNX and RR N. Any other ideas on how to fix it?
Oh, and GPS also became pretty bad, it takes a few minutes to get the first fix.
If it matters I live in Poland.
Usual reply wipe phone flash stock rom .
Wouldn't connect to LTE on stock as well. Finally I found out it was not my phone's fault but carriers. Other SIM card in my phone has LTE and my SIM in another does not.
Hello Guys,
I bought an S4 and I discovered that I was scammed (it was the sprint version and not the GT-I9500 as it was indicated on my about phone tab). It comes with 4.4.2 and everything was working fine (the only things that bugs me was that I was unable to receive updates). Recently I encountered some little issues so I decided to install a new ROM. I tried the Vanir and Commotio ROM and for a moment I was super satisfied (it was an amazing experience). However after putting back my SIM card, each time I try to deal a call, I got the error "mobile network is unavailable". I thought it was an issue from the ROM I used so I tested the LineageOS and same issue. Finally I tested the STOCK ROM Lollipop and the same issue again except this time the WiFi does not work. Now my phone is completely useless, so can anyone help please ?
PS: When I go to settings->about->status, everything about the SIM info(network, my phone number,...) is set to unknown. the IMEI is intact (non null). IMEISV is 00.
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Worry not, I have the same problem on an international unlocked G900F.
The problem is inexistent on latest stock firmware, but it is present on the Oreo custom roms i've tried so far, such as lineageOS, CrDroid, Resurrection Remix.
The Only Workaround i've found so far is to enter the info menu on lineage os, dialing *#*#4636#*#* and turning off radio and On, on the Device Information menu, also updating SMSC proved to work on a few ocasions.
Needless to say, I've tried EVERYTHING this forum suggest, such as full wipe from stock recovery and running latest stock for a few days, or even flashing the latest baseband alone, but it doesn't work. I've read some interesting post about this issue on a Xiaomi Oreo device, and i'ts supposed to be an issue of Oreo roms and the way it measures the signal bars, but no fix so far.
Anyway if anyone finds a way to fix this annoying issue on the next Lineage16 I'd be grateful
Having similar issues with G900V on verizon. I've tried many ROMs old and new, latest LOS16 / RR. also I've tried other network fixes as in original post, and different hardware. I have a few of these, all EMMC15 unlocked bootloaders
Are there any developments here?
Weird thing is, SMS/MMS/calling 'works' two blocks away but I always have the 'roaming indicator off' no matter where I am, and there is a delay in sms IF it work at all. Also, this just started last month. (?) I've been using LOS 16 without network issues for a few months prior. It's is possible Verizon has changed something in the service in my area? I went to verizon to verify compatibility and try a new sim, they were mostly useless but otherwise confirmed that the g900v was on the 2020 list of compatible phones. been trying older builds (including starting fresh on the one that was working last month) but nothing but using stock QL1 magisk rooted ROM works - and that one works very well, reliable, and fast. everywhere. grrr, I'm not ready to retire my fleet of s900v, and I would rather retire them than go back to MM if this can't be fixed.