So my phone is being the weirdest. Updated from an older nightly of CM11 up to a newer one (9/22 i think) which changed modem from what was MB1 to NE1. As a result, I got data very occasionally, but at least half, if not more, of the time I had "Emergency Calls Only" status.
I tried flashing the older radio, MB1, onto CM11. Still didn't work. I tried going back to CM11-SNAPSHOT-M7 from July. Still didn't work. I tried a full data/cache wipe and tried installing PA. Still didn't work. Tried PA with NE1. Didn't work.
I just ODIN'd back to 4.1.1 stock - surely bone stock will work, right? nope. Signal is okay, but right now i'm at half/half getting signal and being stuck on emergency only. Battery stats list cell standby on top, and my "time without signal stat" is at 43% right now. It was around 70% earlier. I tried flashing MB1 to stock 4.1.1 again, since it was on a older radio, didn't work.
I have no idea what is going on - something with the radio that would continue to persist after a full ODIN to stock - I have the modem/radio files but none seem to fully work (MB1/NE1/NL1), i'm constantly getting some signal sometimes but most of the time i'm on "emergency calls only" and SMS messages flat out don't work.
I am currently running:
Android Version: 4.1.1
Baseband Version: I535VRBMB1
Build Number: JRO03L.I535VRBLK3
I am rooted, with custom recovery. What should I try next?
flyingpenguin said:
So my phone is being the weirdest. Updated from an older nightly of CM11 up to a newer one (9/22 i think) which changed modem from what was MB1 to NE1. As a result, I got data very occasionally, but at least half, if not more, of the time I had "Emergency Calls Only" status.
I tried flashing the older radio, MB1, onto CM11. Still didn't work. I tried going back to CM11-SNAPSHOT-M7 from July. Still didn't work. I tried a full data/cache wipe and tried installing PA. Still didn't work. Tried PA with NE1. Didn't work.
I just ODIN'd back to 4.1.1 stock - surely bone stock will work, right? nope. Signal is okay, but right now i'm at half/half getting signal and being stuck on emergency only. Battery stats list cell standby on top, and my "time without signal stat" is at 43% right now. It was around 70% earlier. I tried flashing MB1 to stock 4.1.1 again, since it was on a older radio, didn't work.
I have no idea what is going on - something with the radio that would continue to persist after a full ODIN to stock - I have the modem/radio files but none seem to fully work (MB1/NE1/NL1), i'm constantly getting some signal sometimes but most of the time i'm on "emergency calls only" and SMS messages flat out don't work.
I am currently running:
Android Version: 4.1.1
Baseband Version: I535VRBMB1
Build Number: JRO03L.I535VRBLK3
I am rooted, with custom recovery. What should I try next?
Click to expand...
Click to collapse
I've never had any issues with ML1 myself. Didn't I send the links for SOKP to you recently?
From my Wicked S3 on SOKP
Related
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Update
I was trying to flash via Clockworkmod. I used ADB FASTBOOT and the radio is now on J1.
So, if Clockworkmod isn't working, use ADB FASTBOOT.
metalgeek said:
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Click to expand...
Click to collapse
What recovery and what version are you using?
I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>
If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.
Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.
I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app
thanks for the help -
gonna try latest baseband and see how it goes
bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.
That's good to hear
I then flashed other modems, versions of CM10.1 and no luck. I odin'd back to stock 4.1.1 and I am still disconnected to the mobile network. What do I do
Please Help
jbjarko said:
I then flashed other modems, versions of CM10.1 and no luck. I odin'd back to stock 4.1.1 and I am still disconnected to the mobile network. What do I do
Click to expand...
Click to collapse
I am also having the same problem I went from MOAR rom to CM 10.1 and my phone says roaming. I try to call and it tells me to call Verizon. SO I went back to MOAR rom and I still have the same problem
zavala_android said:
I am also having the same problem I went from MOAR rom to CM 10.1 and my phone says roaming. I try to call and it tells me to call Verizon. SO I went back to MOAR rom and I still have the same problem
Click to expand...
Click to collapse
Same issue here. Had to restore to previous.
Check Q&A and Dev threads.
The .1 breaks data. Either go back to release, RC5 or go to Nightlies.
I went to nightlies and i'm working fine now. (and get the new features)
My problem is I flashed back to stock via odin and I still have no data, at all. It's roaming...Will attempt to reflash tonight.
Alright I'm on the latest OTA build, MF1 I believe, still roaming only. Where should I go from here, what should I flash to hopefully get rid of this. *228 doesn't work. *2767*3855# says my phone is not authorized to make this call, etc...I'm stuck.
Nevermind, I did a full reset and have all my data back. I'm on the latest OTA, can I root, unlock, and proceed as normal from this build?
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
TheCing said:
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
Click to expand...
Click to collapse
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
XdrummerXboy said:
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
Click to expand...
Click to collapse
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
TheCing said:
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
Click to expand...
Click to collapse
Hmm... ML1 should be new enough.
That's a bizarre issue.
For me, I mainly get 3G. It seems as if either Verizon pulled some LTE towers near me, or my data antenna doesn't have very good contact. Maybe you're having the same issue.
Do you EVER get 4G? Or literally never?
So after running multiple lollipop roms for quite a while i thought about switching back to 44S just to see what it was like.
So i downloaded the fastboot images of 44S and flashed them to my One. After rebooting into the OS i immediately saw that i had no signal, atleast it said 'No signal' but with my carrier name next to it. I fiddled around with it changing to different kitkat modems and changing my APN settings but nothing seems to work! I think i've tried everything now so far.
Just for a giggle i though flashing a lollipop modem and booted back into the OS and bam there it was! full signal bars. But this is weird, why would the kitkat modems not work, or atleast dont give me signal at all but a lollipop, which is designed for lollipop do?
Anyone knows why my kitkat modem won't allow me to get a signal?