Related
My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks
mewikime said:
My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks
Click to expand...
Click to collapse
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants
winosxbuntu said:
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants
Click to expand...
Click to collapse
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!
mewikime said:
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!
Click to expand...
Click to collapse
nice to know you fixed it :laugh:
I have had annoying ongoing problem of my phone needing to restart due to my Sim card being removed. I have not removed my sim card at all and it has been happening since I have updated to the newest modem NB4. My setup is as follows the Insane Kit Kat Rom V5 with the included Kernel. To note this has happened since updating to the new NB4 modem. If anyone has any suggestions I would appreciate it.
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
baseballfanz said:
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
Click to expand...
Click to collapse
Really?? That's great, hopefully it stays working great. What kernel are you using?
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
vinniej said:
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
Click to expand...
Click to collapse
I will try all of these suggestions that I have seen so far. What about Odining back to stock and then rooting again? Like I have stated previously I have started seeing this issue since updating to the NB4 Modem and Insane KK. I am sure it isn't the ROM, so I will stick with Insane KK because it is a nice ROM. If anything changes I will report back.
Well, I'm going to take back what I said about fixing it. Sim card removed error happened again. I managed to get a logcat, and dmesg. I have not seen any smoking guns in the logs so I'm going to try a different kernel.
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
crazyc78 said:
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had Talexop's and switched to Ktoonsez's (TW 4.4.2). I did get another error after switching so I'm not sold on a kernel issue either.
I think I'm going to retrace my steps and start from the ground up. I jumped directly from the MDL modem directly to NB4. Maybe I need to go MDL>MK2>NB4?? Maybe try a different Odin version? Switch USB ports on my desktop? Different cable? I'm going to keep trying different things until I get it fixed. It is quite an annoyance because the error happens at times when the phone is asleep and you obviously cannot get any calls, messages, etc.
I'll keep the thread updated for sure.
Been half a day and no errors yet (knock on wood). I did not change anything as far as kernel, rom, or modem is concerned. I did go into Settings>More networks>Mobile Networks>Network Operators>Search Networks and then tapped the tmo network (manual network selection).
I do live / work in an area where Tmo goes bye-bye and there is only Vzn and ATT. I recall having to switch networks recently in order to make a call in that area for work from the no signal zone (I have a spare "work" SIM and my phone is unlocked). Perhaps doing that jacked with my selected default network and could indirectly be the cause of the no sim errors?
And I've done the SIM switch in the past on 4.3 roms without issue. Maybe it is a KK / NB4 bug?
Sounds like you're on track bro, I have tried a few things and so far knock on wood like you said it seems to have worked. First I thought about going back to stock but Odin couldn't recognize the md5 or tar files I downloaded. So then I decided to reflash the NB4 modem. I flashed it three times!! Maybe to see if that would make a difference. Then I reinstalled Insane Kit Kat V5 and did a clean install then restored my backup. So far I have Been running my set up for almost 24 hours and not one error! I will keep looking out for it and report back after my current battery had drained out.
SENT FROM MY INSANELY SICK S4
So I just wanted to give an update on my situation. I have gone back to stock the original 4.2.2, and then rooted my device and then installed Insane KK V5. I have noticed with the stock tar ball file of 4.2.2 I get the NB4 modem. A couple times I did not get the NB4 modem I had the original modem. So then I flashed the NB4 modem and my phone was saying unknown baseband. The last two times I have went back to stock it has given me the NB4 modem and I am still on Knox free bootloader. I am still getting SIM card removed errors, more frequently than ever now. A few times my phone tells me that there is no SIM card inserted at all!!! Very frustrating, I was on a phone call earlier tonight and the error happened during the call. So I called Tmo for a replacement SIM card and we will see if that helps, I'm optimistic that it will. I'm now convinced it may be the NB4 modem, we will see what happens when I get my new SIM. If anyone has any more suggestions I will be open to them.
SENT FROM MY INSANELY SICK S4
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
vinniej said:
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
Click to expand...
Click to collapse
This was the 2nd post in the thread. I've tried all that and for a while I thought it was fixed. I think I made it 4 days without a problem but then they came back.
_eroz said:
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well...Here is my latest and greatest attempt. I flashed the NB4 modem 3 times (no auto reboot throughout the process), and did battery pulls after the first two flashes. 36 hours and no messages.
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
analogchild said:
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
Click to expand...
Click to collapse
I'll try to explain what I know (which ain't much!). In order to avoid Knox some folks including myself have retained the knox free (MDL) 4.2.2 bootloader. How to tell if you have a knox free bootloader look HERE (credit to @shiamatsu) By flashing a modem.bin (which can only be done via. ODIN) we are able to have the benefits of the newer radio, but keep the knox free bootloader. A few of us like _eroz and crazyc78 have seen issues with SIM errors since going to the NB4 modem with MDL bootloader. And thus this thread. And in case you want the instructions to upgrade to the NB4 modem look HERE
I imagine if you don't mind knox and you did the full upgrade, you probably should not be seeing the SIM card errors. I'd be curious to know if anyone is seeing SIM card removed errors with the NB4 bootloader / modem.
Brain hurts. Time for a beer...
Thank you. I'm gunna give it a go and see if it works
This may be a hardware issue. My wife gets it on stock never rooted.
I am curious to know when you flashed the NB4 modem did you go back to stock first and then reroot your device and then flash a rom and then odin the NB4 modem? I did all that and still got errors. I am going to update to Insane Kit Kat V6 later tonight hopefully I don't have issues after updating. I am going to try your remedy and see if it works, and if it doesn'tjust wait for my new simcard.
SENT FROM MY INSANELY SICK S4
Q&A for [Baseband] ALL T999, T999L, T999V, T999N Modems! w/ MAP and Data Tweaks!
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
modem T999VVLUFNH2
Hi everybody,
I try to find the updated modem for my S3 (videotron SGH-T999v)
I have the modem T999VVLUFNF1 (ROM LS 3.1 stable KK 4.4.4, KT747 kernel)
When I unzip the official ROM of samsung (older like 4.1.2 and the last samsung update from september 2014) , I only find the file NON-HLOS.bin
According to sammobile the last videotron modem is T999VVLUFNH2, but I cannot find the file. This is the first time I try to update the modem because I have a poor reception in my house.
Thank you for your help
I haven't decided if I will post those or not. Too great a risk with the 4.4.2 modems. If you want to try the latest I can only recommend fully updating as a safe way to do so.
If you really want to be the one to test if it's safe, I'll get it uploaded for you, but understand there is a chance it could hard brick the phone beyond repair.
Reason for all of this is because we know if you flash a 4.4.2 modem on 4.3 it'll permanently brick it. I have no idea if flashing an older or newer 4.4.2 modem on 4.4.2 firmware (like you want to do) will result in the same. Normally, I would guess it wouldn't be the case, but it seems a lot has changed in these new builds that no one understands, and there have already been too many bricks for me to be comfortable trying something new like this without exercising great caution.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you for your reply and your advise.
As I don't have enought money to take the risk, I will keep my actual modem.
Thank again
Don't blame you a bit! But don't forget, you can still fully update and that may help. (From what I've seen, flashing older modems on 4.4.2 doesn't brick, so i think if you updated, it should be ok to flash the NF1 modem if the newer one doesn't help. It might not work, but I don't think it would cause any harm. Just food for thought, but again, I can't guarantee anything with these latest modems...)
If it's a bad signal issue that you did not have before, call your carrier and ask if there are any tower/network/account issues they are aware of.
Your carrier probably doesn't do this, but Tmobile will sometimes give customers a signal booster for home use only. You can buy them online too, but I'm not sure how my h they are these days. (Just make sure it boosts the frequencies used by your carrier if you look into this.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just noticed today that my phone is on T999VVLUFNF1 but that there is a newer 4.4.2 release for the T999V phone that is T99VVLUFNH2. Would it be good to update via Odin to this? Is it just a newer modem?
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
abetterlie said:
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
Click to expand...
Click to collapse
Latest baseband is NC2, flash it, and if the device still does not pick up service flash back to MD5 firmware and see if it will pick it up. If not then it might incompatible with your provider..
Thanks!!!! Also Those using T999 switched to ATT
Just wanted to say thank you!!!
Also just wanted to say for those who have a T999 that switched to AT&T this works (I wasn't sure if this would work since it didn't say anything about AT&T working with it. To be perfectly honest I didn't read everything but again THANKS!!!!!!
Hi Guys,
I got the OTA update ( T999UVUENC2 ) about a month back and since then, my Wifi has stopped working. It stays greyed out when I try to turn it on. Just won't turn on.
The logcat says that the "WiFi driver is unstable".
What I have tried so far (with no success):
1) Flash the same build again (T999UVUENC2).
2) Flash the root666_T999UVUENC2 build. (Currently, I am on this)
3) Flash Cyanogenmod 11.
4) Factory reset.
5) Pull the battery out when the phone is on and put it back again.
6) Modify/delete the wpa_supplicant.conf file.
Can someone please give any directions on how the "Wifi driver can be fixed"? I understand from going through the forums that downgrading from 4.3 to 4.2 can cause a brick. However, can I downgrade to the previous T-Mobile 4.3 build (T999UVUEMJC ) without causing a brick? Do you guys think that can help fix the Wifi?
Any help would be greatly appreciated.
Could you point me to what one exactly i need for T999LUVUBNF4
SGH-T999L Will Not Mount Ext Sd/No root or load file from .zip to root
I always get stuck at the boot screen where I am supposed to Update from Zip, but my phone NEVER lets me Mount the External SD card, I have a 64GB card, failed, 16 GB card, failed, what am I missing. All the good tutorials, ESPECIALLY yours, get me to that point but being unable to load that .zip file from sd just murders me. The Phone is on 4.3 and I believe I loaded your stock 4.3 firmware after failing to get this part done and then trying every single rom possible (didn't realize this had murdered me) until I managed to get back to this stock rom. Why does it not want to load from ext sd? Is it the file system? I've never had any issues with any of these sd cards, and they aren't generic cards, one is a samsung other a sandisk,
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
brianmilw said:
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
Click to expand...
Click to collapse
Sorry for responding late but in case anyone else is wondering, most partial firmwares that you see posted for our device model (even the ones posted in the international snapdragon rom threads that have Lineage, RR, and ported TW roms) do not contain the aboot.mbn file, aka bootloader. So it will not change our bootloader in anyway.
That's not say a dev or someone like myself who's just a beginner couldn't make a mistake and forget to remove it or maybe they don't know that it's supposed to be removed. So it would be best to stick with the tried and true links that have been posted of you're needing to update your modem. I know for certain the ones that have been posted by ripee, hsbadr, and me are safe, but I've never used not have heard anything negative about the other ones posted.
All that being said, you can update the SM-N910V bootloader if you'd like. Mine is updated to where it ends with CQI2 which is the penultimate update. If there is a difference between CQI2 and CPD1 (initial 6.0.1 bootloader) then it is a slight difference. Sometimes I think I just want to believe that tweaks and changes are working, especially if you put a lot of effort and time into it(which is required when you don't have much knowledge).
This was just posted recently;
VZW_NOTE4_EMMC_15_Chipset_Only_Bootloader_Unlock_U p/Dwngrade_Bootloaders_KK/LL/MM by jkruse
I haven't tried it yet but it looks much easier than the method I used, which is below;
For the folks that just like to tinker and break things....... How else you supposed to learn how to fix it?
How-To Update Your Bootloader from CPD1 to CQI2 by this fool