Ok, I have a LS980 that is either always Roaming or only on 2G Edge data connection........
I have been switching between zvc (stock) and zv8 roms (cm12)......requiring the respective radio/modem flash to properly boot.
The reason i've switched soo much is because I was chasing down the CM12 no GPS issue.......which I did manage to remedy by flashing to stock, then restoring my cm backup.
Ok.......so basically......I've seen this phone connect to H+, like it should, only a few times.....and for a few moments then it always ultimately disconnects and reverts me back to Edge.
I thought it was a CM12 issue......but I flashed Cloudy's G3 rom based on ZVC......and it didn't help.
I just so happen to have a second LS980 G2 for a few days........its running the Cloudy G3 ZVC based rom.....no issues.....H+ all the way like normal
Right now I have both G2's running the same ZVC rom (and I have wiped complete and .tot backed to ZVC stock, then flashed the cloudy rom on the weak signal g2)
I can literally take the sim out of the roaming/Edge only G2...put it in the other g2 and pretty much always H+ after a few seconds of booting.
So.......my basic question........would you deduce that: 1. this phone just already had weak radios inside this phone to begin with OR 2. frequent modem flashing caused a weaking/radio issue?
I've worked on probably close to over 5 G2s.......and this is the first time i've seen one with weak/bad radio inside of it and displaying this issue.
Nobody else ever had a G2 with a bad/weak radio/modem??
Your issue could be hardware related. My D802 has had a terrible GPS reception that drove me mad. No matter what ROM, even stock. They replaced some module (radio and/or GPS), now it's accurate.
Flashing *should* have no impact, on the other hand overheating issues with our G2 are known, resulting in screen damage. This may also fry a radio, I don't now.
Regards,
saimonsez
Related
I finally got superuser working by flashing Echoe Illusion, the full touch-wiz version with Android 4.3. At first it seemed like I had everything working but the next day when I left the house (no longer connected to home wifi) I quickly realized it was refusing to connect to mobile data. I also cannot send text messages, and likewise I can assume I can't get them either. I have tried flashing the nightly CM11 build and 3G connected although LTE did not. I wasn't in an area where I expected reliable LTE anyway so that's not even an issue at this point because I'd very much like to use this Echoe Illusion rom, or another Touch-wiz based one. I just can't go downloading a bunch of them because I have a severe restriction on data usage and have already downloaded Echoe Illusion AND multiple other things. If it matters, my baseband ends in MJA.
I have also attempted to flash different modems with Odin, although all of them failed completely to flash at all and at this point I have to honestly admit I don't know what I'm doing. This is most definitely not my first time rooting...I'm just used to HTC phones, the Evos in particular. Thanks in advance if anyone can help or provide useful tips!
oh and P.S. I can't go back to the stock firmware because I must have flashed an incorrect kernel, and it borked the phone. I only got it working again by flashing a separate rom (Echoe Illusion) and have since flashed other kernels with no ill effect. I had a nandroid backup of the stock rom before I borked it, but every time I try restoring it, it stops at the yellow Sprint screen and won't boot.
I used to be on ZV8 radios until about a week ago, when I flashed Optimus ROM and ZVA radios. I then had an issue where signal would drop for a few seconds and then reconnect. My cell standby shows 1% without a signal because of this. I flashed back to ZV8 radios, but I continue to get this issue even on AOSP ROMs. I might try to flash stock and update profile/PRL/etc, but barring that, any ideas as to what could be wrong? Thanks!
I read online that someone had data issues using the ZV7 aboot. They fixed it by using a Zv8 aboot. This makes sense seeing as how all ROMs have issues for me since flashing the ZVA radio + ZV7 aboot. Does this seem plausible?
Also, data dies for me during the cutout as well, it's not just a graphical bug.
I flashed a stock ROM and updated profile/PRL etc, as well as trying the ZVA radios again. No dice...
My signal also dies on AOSP ROMs. I think it's just a bug that has yet to be fixed.
I have two VS980 phones that shipped to me stock with the 26a firmware. I have rooted both phones and have updated to the latest TWRP recovery. They both work as expected as long as leave them as they are. However, as soon as I install any custom ROM, they will both drop phones calls randomly.
I have tried almost every custom ROM available on this forum (Stock, CM, AOSP) and all of them will drop phones calls within a few minutes. I have also tried changing basebands and flashing my EFS backup without success. Data, Texting, Wifi, GPS everything works but no phone calls, even with full signal bars. As soon as I revert to stock, everything works like normal.
I have searched online and on the forums but I can't seem to find an answer to this. I am at a complete loss. I don't want to be stuck on the stock firmware forever. Does anyone have a suggestion?
So I have flashed multiple roms and I keep getting the same error. I will randomly lose my service after a boot and then a few minutes later the phone will say no sim and reboot itself. This has happened on two different roms (one AOSP based, one CM based.) Both time the roms were clean flashed perfectly. I have been forced to revert back to an earlier radio (from 3.61 to 2.15) just to keep my service. Has anyone else had this issue and is there any fix for it?
when did it start? because we have been on the 3.61 radio for about 2-3 updates already..
(cant remember exact date, would have to check my factory images to determine )
messiahfreedom said:
So I have flashed multiple roms and I keep getting the same error. I will randomly lose my service after a boot and then a few minutes later the phone will say no sim and reboot itself. This has happened on two different roms (one AOSP based, one CM based.) Both time the roms were clean flashed perfectly. I have been forced to revert back to an earlier radio (from 3.61 to 2.15) just to keep my service. Has anyone else had this issue and is there any fix for it?
Click to expand...
Click to collapse
The latest Radio doesn't assure a benefit for everyone, and might not be suitable for your region. In my case it has boosted my reception, but that might not be the case for you. So, just roll back to a previous radio that offers better compatibility.
I had latest stock firmware and everything was working fine except it wasn't getting any updates so I decided to flash Linneage. I followed instructions, made sure to flash the copy-file on both slots etc. Everhything seemed fine untill I left my home and didn't have access to wifi, then I noticed that data didn't want to work. It showed having 4g connection (full strength) but it was so slow that I couldn't even check speed because the homepage barely load. There was a connection but since it was so slow I received timeouts almost everything I tried. I also noticed that bluetooth didn't work. It would connect/disconnect every 3 seconds from my bt headset. This was "fixed" by disable google on my phone. Very strange.
I thought It might have to do with Linneage so I tried Pixel experience. Exact same problem there.
I thought maybe the linneage files I flashed to both slots were bad so I reflashed stock rom. Now I have the same problem with stock rom as well. I eventually used the MSM tool and reflashed the latest stock firmware, locking the bootloader and all that. Still having the same problems. These two problems were non existant before any of this.
I've tried my sim in a different phone, even made sure the apns are the exact same on my working phone and my op6t.
Is there any other way to make sure the phone is completely factory restored other than MSM tool? Now I'm running stock oxygen, no root, locked bootloader etc but the problem persists. What is my next step to try?