[G3 Q&A, Help & Troubleshooting] Williquah:
NeatAndClean,

Thank you for providing the detailed information in this thread, so let's get to business.

First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.

If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.

However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.

To start out, my questions are:

1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)

2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.

Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:

I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:

is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.

Mine is:

and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.

Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:

1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.

2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)

3. Open the extracted files folder

4. Open "META-INF" ==> "com" ==> "google" ==> "android"

5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.

6. Delete this line of code:

7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.

8. Overwrite the edited "updater-script" back to it's directory (the android folder)

9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))

10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"

11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)

12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"

13. The edited one^ is the only one you need now, and is the one you will be flashing

14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.

This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.

I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.

However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM

AND

the GApps file

at the same time

in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.

To answer this, no it is not a problem, you were correct.

1. The LG G3 is an ARM device

2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps

3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.

The procedure you did to flash the ROM was all good:

This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.

1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup

2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.

3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.

I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.

Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.