20C Baseband with 10D Radio
SMS Send Bug Fix
!!d800 Only!!​
Edit (2015.05.12) - I have dumped and posted d80020y modem to my website. It seems that 20y might have fixed this issue. I have been using it for a day or so now and have not noticed this bug. You may wish to try that modem before this one.
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: ROMs that require the KK Modem (for rotation to work) cause SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
https://www.gregtwallace.com/lg-g2/d800-modems/
(It is the Modded One - Baseband: D80020C; Radio: D80010D)
Install:
1) Copy .zip and .md5 to the root of your sdcard.
2) Reboot into TWRP.
3) Install -> Select .zip File.
4) Check "Zip file signature verification." (File is properly signed.)
5) Swipe to install the zip. (MD5 and Signature should verify and modem should install.)
6) Wipe cache/dalvik (for good measure.)
7) Reboot System and Enjoy!
Note: In "System Settings" under "About Phone" -> "Software Information" the Baseband version will be listed as ending in ".190034". This is the 10D baseband.
10D & 10O Baseband Rev: M8974A-AAAANAZM-1.0.190034
Default KK Baseband (20c) Rev: M8974A-AAAANAZM-1.0.190082
This Patched KK Baseband Rev: M8974A-AAAANAZM-1.0.190034
Please respond with any issues, etc.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
Reserved
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
c_brown93 said:
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
Click to expand...
Click to collapse
No, this will not work for ROMs based on the old source (e.g. CM11).
This only works for KK based ROMs. It allows KK based ROMs to be fully functional, while still using the old baseband (radio).
This looks promising, I'll provide feedback once I return from work tonight!
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
I'm running Lam Hoang G3 ROM on D800 but it should still be fine
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
bps119 said:
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
Click to expand...
Click to collapse
You're welcome.
XERO_Racer said:
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
Click to expand...
Click to collapse
This isn't anything fancy. It is exactly what it professes to be. All of the KK modem files, except the 10D radio files were swapped in. So if you had any other 'better' things on 10D vs. the KK modem, you might get them in this, but probably not.
Used this modem all day today. No issues. Didn't have the SMS issue at all.
blastagator said:
Used this modem all day today. No issues. Didn't have the SMS issue at all.
Click to expand...
Click to collapse
You think this will help with reboots caused by low LTE signal?
RenderBroken said:
You think this will help with reboots caused by low LTE signal?
Click to expand...
Click to collapse
I've never had that problem, so I have no idea.
blastagator said:
I've never had that problem, so I have no idea.
Click to expand...
Click to collapse
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
The sending delay bug was very annoying, I just flashed it and will report back if there are any issues!
RenderBroken said:
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
Click to expand...
Click to collapse
To be honest, I'm not 100% sure. It's easy enough to figure out though. Usually the ROM post says which to use. If not, you can just flash one of the modems, if your sensors work, you're using a modern that is compatible with your ROM. Easiest sensor to check is rotation. Open Maps and your gps blip will have an arrow showing your rotation orientation (compatible) or there won't be an arrow (wrong modem).
OMG Thank you SO much!
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
I have been waiting for a solution for this problem for so long. Downloading now. If this works I would be more than happy to donate. I love the CloudyG3 roms, but the issue with SMS getting stuck in "sending" has been a complete headache for me.
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori kernel?
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
joeynox said:
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori?
Click to expand...
Click to collapse
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
phatmanxxl said:
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
Click to expand...
Click to collapse
This modem is not intended for CM11. CM11 is not stock KK based.
blastagator said:
I believe the bug is a part of the KK radio and ROM independent..
Click to expand...
Click to collapse
thanky you for responding. will i have any issue if i use this with dori kernel?
blastagator said:
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
This modem is not intended for CM11. CM11 is not KK based.
Click to expand...
Click to collapse
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
joeynox said:
thanky you for responding. will i have any issue if i use this with dori kernel?
Click to expand...
Click to collapse
Kernel and Modem should be independent and thus not cause a problem, but I don't know for sure since I haven't done it.
phatmanxxl said:
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
Click to expand...
Click to collapse
Oh, okay
Related
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?
Q&A for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
its work on validus rom v8 , and i have more stable signal now , thanks
recover from oxygenOS fw.
Reply for script error while in twrp for flashing blisspop after using oxygen modem.
It was happened to me as well. What I did was;
Reflash cm12 firmware updater 21/03 followed by firmware updater 02/04. Then continue installing ROM, gapps, and etc. It worked for me at least.
Modem
I am currently running Blisspop...
Do I flash only the modem since I have the firmware provided by blisspop or I flash with the Oxygen firmware and modem?
Lost MMS
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
JeffDC said:
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
Click to expand...
Click to collapse
About 2 hours on the phone with Straight Talk, and no success. They sent several signals, but ... So tried reinstalling piece by piece and nothing helped. Won't be a show stopper for me as I don't send pictures much (everything else works great). Connection with the Full Oxygen Modem is the best I have ever had, and staying connected in spots I had no signal before.
Thanks for the help, but still a little miffed.
Answer to jasonx3 question
jasonx3 said:
I'm having this issue on CM 12s after flashing. i did a clean install from TWRP. i can't connect to LTE signal keep crashing. look at the signal icon you will see what i meant. will flashing this modem fix this?
Click to expand...
Click to collapse
This is an easy fix. Go to settings>mobile network> APN > select the correct carrier.
I had mine set automatically to T-Mobile and had to switch it to Metro PCS.
---------- Post added at 12:43 PM ---------- Previous post was at 12:37 PM ----------
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
MMS app> settings> auto enable data and auto enable retrieve.
Should I flash only modem or whole firmware on cm-12-20150415-NIGHTLY? If I flash the firmware, will it be overwritten if I update cm12 rom? Sorry for my ignorance.
A great contribution
thanks
OxygenOS modem on encrypted CM12s
I sideloaded the OPO_OxygenOS_1_0-flashable-modem.zip file to encrypted CM12S with TWRP2.8.6. It didn't give me LTE at home where my wife's Moto E 2015 has it, but it did improve signal strength on LTE Discovery from -100 dBm to about -80 dBm but still EDGE. Will keep it until something better comes up.
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Ty29 said:
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Click to expand...
Click to collapse
Update ~ Never mind I figured out how to use Google drive.
Does it work with CyanogenOS and will it fix the signal dropping issue?
Can we backup current modem before flashing the new one ?
Hey can someone answer the question that has been asked a cpl times already if whether or not people on CM 12- or Blisspop like me- have to flash FULL or just MODEM. Sorry but i thought that's what this q&a was for
Revert back to original Modem
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
maxpayne1989 said:
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
Click to expand...
Click to collapse
CM has started to use the same modem as Oxygen OS (that you have) some weeks back. And anyways an update will overwrite your current, if it is newer.
Does the new Cm12 come with oxgenos radio & modem?
Does the new Cm12 come with oxgenos radio & modem? suppose if i have wifi or call quality issues in cm12 do i have to flash the modem or the whole firmware and is wiping necessary?
Not working on moto g xt1033
Hi,
i just flash this zip and after system reboot my phone is not turning on, so what is the issue here?
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
toohsieh said:
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
Click to expand...
Click to collapse
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
silentcovenant said:
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
Click to expand...
Click to collapse
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
toohsieh said:
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
Click to expand...
Click to collapse
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
Well, stock is 4.4, but when you use the stock CM updater you'll be brought to CM12, 5.0.2. You don't have to stay on 4.4
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
toohsieh said:
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
Click to expand...
Click to collapse
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
silentcovenant said:
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
Click to expand...
Click to collapse
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
toohsieh said:
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
Click to expand...
Click to collapse
The stock version they gave me was: XNF9XBS28K
silentcovenant said:
The stock version they gave me was: XNF9XBS28K
Click to expand...
Click to collapse
I can't say I've ever seen that version before but it looks like someone else had the same issue: https://forums.oneplus.net/threads/xnf9xbs28k-ota-updates.315441/
So last night my phones wifi was working fine. That's until I made a few modifications to it.
Things I did:
Installed TWRP Recovery Menu Moto G port
Installed CM13 Osprey Nightly 20160704
Installed SuperSU
Installed Gapps
Right after all that I realized my WiFi wouldn't connect during the CM13 setup. It just said saved after I entered the password. I tried manually connecting it, it went from full bars to one bar then goes back to saved.. When my phone actually connects to the WiFi it is running extremely slower than normal. It also disconnects at random times.
Things I've tried to fix the problem:
Reinstalling ROM w/wo Gapps & w/wo SuperSU
Trying new router
Allowing all permissions that were not allowed
Enabled legacy DHCP client (saw on a forum)
Contacting ISP to see the strength of modem
If anybody has a solution it would be appreciated. I am not sure what to do. Also im in the same room as the router so the connection strength should be solid. If any other information is needed I'll provide it asap. Thank you.
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
acejavelin said:
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
Click to expand...
Click to collapse
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Click to expand...
Click to collapse
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Gravemind2015 said:
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I do not have a case on my phone. But I will try to remove my sim card while I go back to the original Marshmallow image. Hopefully it works out
itzrishi said:
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Click to expand...
Click to collapse
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
itzrishi said:
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
Click to expand...
Click to collapse
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I don't have a backup because I don't have enough storage. But I did follow lost101s guide.
The bad news is I am still having issues with the wifi. It's not as bad though the speed is decent and it disconnects a lot and just shows saved.
Therefore the problem shouldn't be with the custom rom and I tried using a different device to see if it's my internet but it worked fine.
My conclusion is either the wifi/Bluetooth adapter needs to be replaced.
Although my problem was not solved thank you for trying to help me solve the issue! Much appreciated.
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
nikhilsnigam said:
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
Click to expand...
Click to collapse
Make sure you have the latest radio stack installed.
acejavelin said:
Make sure you have the latest radio stack installed.
Click to expand...
Click to collapse
Yes I just downoaded the stock package and flashed modem(Older 1)
Seems to work. Haven't had any disconnects till now.
I've tried a handful of Nougat roms now, and I keep having the same issue with all of them: no call, text, or data. I've tried a few mods that are supposed to fix the issue, and even a ROM where, in the aroma settings, it gave me an option to fix the issue. I'm not sure as to where the point of failure is, but I think it's just an issue with this model of phone in particular. The Marshmallow ROM I currently have is having some issues with app compatibility, so if anyone knows how to flash back to the stock firmware, I'd greatly appreciate it.
BioBelac said:
I've tried a handful of Nougat roms now, and I keep having the same issue with all of them: no call, text, or data. I've tried a few mods that are supposed to fix the issue, and even a ROM where, in the aroma settings, it gave me an option to fix the issue. I'm not sure as to where the point of failure is, but I think it's just an issue with this model of phone in particular. The Marshmallow ROM I currently have is having some issues with app compatibility, so if anyone knows how to flash back to the stock firmware, I'd greatly appreciate it.
Click to expand...
Click to collapse
You cant really unroot because of the knox bug. You can flash back stock firmaware via odin and get recovery and flash the latest super su so the bug will be gone or flash a custom kernel.
N-DroidMod v6
Ohhdayumm said:
You cant really unroot because of the knox bug. You can flash back stock firmaware via odin and get recovery and flash the latest super su so the bug will be gone or flash a custom kernel.
Click to expand...
Click to collapse
I kind of have the same issue, except I can text and have mobile data. I just can't hear calls, and no one can hear me during calls.
I have note 5 SM-N920T, and I am using the N-DroidMod v6 custom ROM (it changed my model number to SM-n920c). I can't tell which kernel will fix the issue, and is compatible with the ROM.
Can you help?
UMAA19 said:
I kind of have the same issue, except I can text and have mobile data. I just can't hear calls, and no one can hear me during calls.
I have note 5 SM-N920T, and I am using the N-DroidMod v6 custom ROM (it changed my model number to SM-n920c). I can't tell which kernel will fix the issue, and is compatible with the ROM.
Can you help?
Click to expand...
Click to collapse
That's the audio bug, try to look in the thread for the audio patch where you flash. Usually provided by the developer if not then you may need to change to another rom that has that patch or a rom that was made for the t mobile version.