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
I updated to the new firmware (4.4.4) this weekend. Everything is working great, except the g-sensor seems to be a bit wonky... Often, the screen does not auto-rotate. Also, I use Screeble Pro app to keep the screen on when not laying flat and it consistently thinks the phone is laying flat when it is not (did that make sense?). I've tried the basic calibrate function in the settings, but that did not help. Also, flashed the new firmware with both the RUU. and SD card methods... Even went back to 4.4.3 firmware with no change... Anyone else having this issue? Any ideas? Thanks for the help.
Sent from my HTC6525LVW using Tapatalk
OK, update... The sensor info to Screebl seems to be working, but the auto rotate (can't even force it to landscape) stopped working at all.
Sent from my HTC6525LVW using Tapatalk
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Freedom First said:
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Click to expand...
Click to collapse
Flashed it twice... via fastboot RUU method (as well as with the SD card method) I am currently running a 4.4.3 based ROM (ViperOne 2.5). Am hoping that when that ROM gets updated to the 4.4.4 version and I do a clean install maybe the problem will go away...
Hello,
I am facing a weird problem regarding the proximity sensor on all CM11 roms.
I was using lollipop roms for a long time now, and have been following latest builds, until I decided that I liked KitKat more. I already had a backup of temasek's last CM11 build, so I reverted to that one, after flasing the cm11 firmware. All was working perfect until I reverted a backup of my 5.1.1 rom, to try xposed. Again, before doing so, I flashed the latest cm12 firmware. After a couple of days experimenting with xposed, I eventually went back to my kitkat rom. After boot, I noticed that the proximity sensor wasn't working. I had already flashed the cm11 firmware before restoring, but I went and flashed it again. Problem was still there. I then tried cm11s 44s firmware, 05Q firmware and 05Q modem only. The proximity sensor problem was there in all cases. (Shows 0.0cm, like I always have my phone in my ear or pocket). I then tried flashing a complete cm11s rom (05Q) with no success.
This is not a hardware problem, as the sensor is working FINE on ALL lollipop roms. I used sensor box in all my tests. I even tried proximity fix from play store, but it did nothing. I also tried to install it as secondary on multirom, then flash the firmware, but again, no success.
I really really need some help on this one, I can't troubleshoot it on my own, I am out of ideas.
Thanks in advance.
(My device is OnePlus one - always using boeffla kernel on both lollipop and kitkat roms.)
EDIT: Solved. Look at my last post.
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
chazxt said:
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
Click to expand...
Click to collapse
Hello,
Which modem did you flash from that thread? I have only tried the 44s from there but it was a no go.
Thanks in advance.
XNPH44S for me it worked
Hello,
Finally found a fix for my problem.
It seems that I had to flash from fastboot the CM11 nightly modem from here: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
The process doesn't wipe anything in case anyone is wondering, it just flashes the modem ( NON-HLOS.bin)
I flashed Euphoria-OS 1.1 (June-29 build, Lollipop v5.1.1), everything was great except non of the sensors work - accelerometer, orientation, proximity etc. I then downloaded a sensor app and it said "sensors are not present on your device".
The Euphoria Lollipop was a clean flash from PA v4.45 (Kitkat 4.4.4), I wiped everything and did factory reset. Flashed cm12 firmware before I flashed ROM and Gapps to avoid problems. Because I only noticed sensor issue after several hours, I thought it might be caused by an app I installed, went back to the drawing board and did a another clean flash, still no dice. Went on and flashed other Lollipop ROMs like CM12 nightly and XenonHD, still the same problem.
I've now done a Nandroid restore and back to PA Kitkat, all the sensors are working fine. So no hardware issue, definitely Lollipop specific.
Any help would be greatly appreciated, desperately wanting to bring my OPO to lollipop. Maybe I should flash a new radio? not sure if that'd do anything to the sensors :crying:
mickey4mice said:
I flashed Euphoria-OS 1.1 (June-29 build, Lollipop v5.1.1), everything was great except non of the sensors work - accelerometer, orientation, proximity etc. I then downloaded a sensor app and it said "sensors are not present on your device".
The Euphoria Lollipop was a clean flash from PA v4.45 (Kitkat 4.4.4), I wiped everything and did factory reset. Flashed cm12 firmware before I flashed ROM and Gapps to avoid problems. Because I only noticed sensor issue after several hours, I thought it might be caused by an app I installed, went back to the drawing board and did a another clean flash, still no dice. Went on and flashed other Lollipop ROMs like CM12 nightly and XenonHD, still the same problem.
I've now done a Nandroid restore and back to PA Kitkat, all the sensors are working fine. So no hardware issue, definitely Lollipop specific.
Any help would be greatly appreciated, desperately wanting to bring my OPO to lollipop. Maybe I should flash a new radio? not sure if that'd do anything to the sensors :crying:
Click to expand...
Click to collapse
Haven't ran CM12.1 so I'm not sure if they're having any issues with the sensors but have you tried OxygenOS or CM12S?
I know those 2 lollipop builds by far are the most stablest as I use them as a base for my ROM and all works fine. But to reduce the hassle, you can always stay on kitkat
Side note: Do you have a link for AOSPA KK?
Are you sure, you flashed the latest firmware? What is your baseband version in Settings>about phone?
Okay I finally got it resolved after reading through the thread about non-working proximity sensor. What I did was extracting NON-HLOS.BIN file from firmware and flash it with fastboot. Apparently flashing firmware in TWRP did not update at all, wired.
I can not use my s5 censors. release him using ssu.apk on OD3 with 4.4.4 kernel NK4.then update to 5.0 OD3 whit kernel stock, in 4.4.4 that the camera did not work well, but I have no censors: accelerometer, gyroscope, gravity, linear, rotation, just proximity, light, pressure, magnetometer I have only those
Does it work on a stock rom? Make sure it is working on stock first, if it doesnt work there might be a hardware issue.
Right. Odin a stock tar and see if it works. If it does then it isn't a hardware issue. It's your rom. Use a different one. Chances are one that old isn't going to be worked on again...ever.
www.sammobile.com/firmwares is the most reliable place to get the tar.md5 files. If you need help with instructions on how to flash the tarballs in odin, let us know
Mine is doing the same! I guess it's hardware
bayron_olaff said:
Mine is doing the same! I guess it's hardware
Click to expand...
Click to collapse
Have you flashed the stock firmware via Odin? That fixes tons of stuff, hardware issues aside