Database Info

Got a OTA for my ADP1!

Just received update notification (running jf's adp)
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.

Its adp's update. No its not cupcake lol

Uh oh, if it's a new bootloader, could this mean trouble for us in the future?
doesn't sound good to me

Just installed the bootloader without the "complete system update" and... surprise. The original T-Mobile G1 bootloader (RGB). After seeing that i downloaded hard spl, then installed it and that's all. I'm not going to complete the full update, because there is a chance after the update to be stuck to normal bootloader, and I don't want to prove it

Good morning!
I was just checking out the market when I got a popup message on my ADP1 (v1.1) telling me a baseband update was available.
I cant remember which version I had before, but it my Baseband version is now:
62.33.20.08H_1.22.12.29
Anyone have the same thing?

Untouchab1e, what was the use of reporting this post? it's only to report Spams, advertisments and other abusing stuff to the Mods and Admins, please use it wisely the next time or you'll get a ban!

yes you called
we came running....please use the report button as it should
thank you

My apologies? I either clicked the wrong button or I dont know, as I cant remember clicking any report button (havent noticed any report button at all really)..
Anyhow, sorry for the trouble
EDIT: A second update is being installed now, described as a "Full system update".. will be interesting to see what it is!
EDIT2: Its apparantly the ADP1 equivalent of the RC33. Latitude, Voice Search.. its all there!
Thank you Google

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the Report Post Button its right besides the post number

ADP OTA update = no more Wifi Tethering??
I go ahead and did the update.
I checked the bootloader and it's still the modded one.
although, there's other problem. I can't do wifi tethering from the terminal emulator. I don't know if the OTA update take out Root access or not. is there a way to check root status without using Terminal emulator? (I know on the terminal emulator you just type su for superuser to get root, and # on the prompt means you have root access)
So, When I typed "tether start" after running the .tar file from the terminal emulator, I got this message
Code:
insmod: init_module '/system/lib/modules/wlan.ko' failed (file exists)
then when I typed tether stop, I get this message:
Code:
rmmod: delete_module 'wlan' failed (errno 11)
any info on this probleM? I need the tether function because it is the only internet access for my laptop at home because my cheap ass aunt disconnected the DSL for the house.
please be nice to me as I am a linux noob and has fairly little understanding using the terminal command line.
Edit: Nevermind. I found the problem. I had the Wifi radio on before I run the terminal code for tethering. Sorry for freaking out guys.

mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I just got this exact same update notification (im in the netherlands), im also running JF's ADP1 1.41 but im doing so on a devphone......... I really dont want to install anything on my phone unless i know specifically what it does or changes.....

mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
EDIT: JF's got a new release to fix this problem: http://forum.xda-developers.com/showthread.php?t=475381 (or check out the top sticky post).

Did it...
... i also got this message and i did the update.
Nothing changend after update. Everthing is the same.

Does this mean, we are all getting ota-updates in the future, even if we are on JF (RC33 or RC8)?
I thought JF deactivated this in his versions...???

kanisdragon said:
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
Click to expand...
Click to collapse
Here's the news....
First part of the update was no problem, all still worked..
Second part installed, phone rebooted, got the nice little blinking android and nothing happened for 15 min :S SO i got bored and tried to turn if off but this didnt work, pulled the battery and the same thing happened; phone hangs on bootup..... So its fooked haha, ill update to JF 1.42ADP1.1h, see what happens. I do need to find a way to disable this update stuff 'cuz its annoying!
So BEWARE when using these 'ota' updates on modded firmwares!!
[edit] And no, i do not have anything Tmobile on my phone because Tmobile sux! [/edit]

...same..
after the second update (part 2) my phone got stucked too.
What can I do now?

Hanneskitz said:
after the second update (part 2) my phone got stucked too.
What can I do now?
Click to expand...
Click to collapse
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....

maarten82 said:
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....
Click to expand...
Click to collapse
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?

kanisdragon said:
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?
Click to expand...
Click to collapse
Probably..... but setting back the complete backup(s) would not fix anything because you would still get the annoying update window telling you to install the stuff that will in turn crash you phone back to where you started
But then from your old backup you could try to install JF1.42 without wiping, that might work!

maarten82 said:
But then from your old backup you could try to install JF1.42 without wiping, that might work!
Click to expand...
Click to collapse
The JF1.42 update worked for me without wiping. I haven't been offered the Google update in the last hour.

[Q] Apply security patch w/ rooted device?

Hello world! This is not my first run with android (by far) but it is the first time something like this "security patch " has come out.
I have a rooted N5 and im running 6.0 build MRA58K and continue to get prompted to install a security update.
My question is, is it safe to install this update, will i lose root or have to reroot? If i "unroot" the system with supersu and then install it after, would that work too? Also i would like to update my kernel to the newest version. Im running blu_spark build #30. Would i just reflash the kernel or do i have to jump through hoops by reflashing the rom first? I dont remember how it works
Thanks

[GUIDE] Update stock rooted/modified rom to last 6.0 Marshmallow w/o losing your data

Razvan said:
[GUIDE] Update stock rooted/modified rom to last 6.0 Marshmallow w/o losing your data
Click to expand...
Click to collapse
Couldnt i just use NRT to do all this? Thanks btw

0xicl33n said:
Couldnt i just use NRT to do all this? Thanks btw
Click to expand...
Click to collapse
Take a moment to learn how to properly flash a Nexus. You will forget toolkits very soon... You should also take a peek at kernel threads and SuperSU.
Learn and flash instead of flash and fix

NRT just does all of the fastboot commands for me instead of having to copypaste address locations by hand. However something did go wrong when i flashed supersu while booted into the wrong recovery (apparently i was in the temp one). So now im stuck with a boot loop, i guess i will have to reflash everything, its not a big deal. all backups have been made.
Ive been doing this a very long time

0xicl33n said:
NRT just does all of the fastboot commands for me instead of having to copypaste address locations by hand. However something did go wrong when i flashed supersu while booted into the wrong recovery (apparently i was in the temp one). So now im stuck with a boot loop, i guess i will have to reflash everything, its not a big deal. all backups have been made.
Ive been doing this a very long time
Click to expand...
Click to collapse
If you only knew how to manually use your Nexus, you wouldn't have posted this question:
My question is, is it safe to install this update, will i lose root or have to reroot?
Click to expand...
Click to collapse
Toolkits do "everything" for you and it doesn't help users to think for themselves.

I ask because i never know what kind of godamn changes happen between android versions.
Sometimes A LOT OF THINGS CHANGE which would make a previous known method of doing x not work.
I had to manually install TWRP, but its all done.
Android 6.0.1 build MMB29K
Root
TWRP
Blu_spark r47
0 USER DATA LOSS
MOD EDIT: Disrespectful comment removed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, I don't know about Primokorn, but personally I wouldn't take kindly to anyone calling me "a$$face" - not the ideal way to make friends in a community where you're asking for help...
Primokorn makes a perfectly valid point. If you read up on the changes, as most of us appear to do, you would not have to rely on Wugfresh keeping NRT up to date.
Primokorn 8,606 posts Thanks Meter: 5,059
0xicl33n 50 posts Thanks Meter: 17
Show a bit of respect for experience...

So you make a thread asking for help, then you carry on like this...when help and guidance is given. Next time just say thank you and leave it as that, or better yet do more reading than posting. And consider this your warning, and the only one I will give, now that you have resolved your issue, you can read the Forum Rules on conduct/posting.
0xicl33n said:
I ask because i never know what kind of godamn changes happen between android versions.
Sometimes A LOT OF THINGS CHANGE which would make a previous known method of doing x not work.
I had to manually install TWRP, but its all done.
Android 6.0.1 build MMB29K
Root
TWRP
Blu_spark r47
0 USER DATA LOSS
Now move along assface
Click to expand...
Click to collapse

Really confusing softbrick (small reward offered for fix)

TLDR: LGUP will just straight up not recognize my G5 no matter what. I'll give you five bucks on Paypal for a solution, if that means anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi guys, I try to avoid posting, but I've searched high and low for an answer and I really can't find it.
I've got a T-Mobile LG G5 H830, that I have recently rooted and installed TWRP on it. Last night, I decided to try changing a value in build.prop, stupidly without making a backup first and after I changed the value and rebooted, stuck at T-Mobile bootscreen, go figure. All I did was change a value from false to true for adoptable storage..
Anyway-- I tried factory resetting, I tried flashing that FLUENCE rom I found somewhere here on XDA, I've tried just about every thing I could, before I gave up and decided it would be easier to just revert back to stock and unroot. I wasn't really utilizing root for more than Titanium Backup anyway.
To the point; I've got the LG UP program installed, I've got the DLL for it installed and inserted, and the appropriate .tot file to flash it back to factory default. No matter what I do, no matter how many different COM ports I try, different drivers I've tried etc, I cannot get it to read my phone in download mode. ADB mode works in TWRP still, but this is driving me insane. The only other phone I have is a busted up BlackBerry Priv, and I want this phone working again asap.
If someone can shed some light on whatever the hell I'm doing wrong, it would mean the world to me.
Please.
P.S: yes I've tried just about every USB port on my computer, and I've tried restarting Windows many times.

you have tried jiggling it?

You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.

speedanderson said:
You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.
Click to expand...
Click to collapse
Use the twrp restore file in the development thread it will revert your build prop back, and from there your phone will work again. Editing build prop is not advised on the H830 has been discussed on numerous threads even before root was established. At least it's only a soft brick .

Have you tried jiggling it perhaps?

so did @wolfu11 get the 5 bucks? his solution should have fixed it.

autoprime said:
so did @wolfu11 get the 5 bucks? his solution should have fixed it.
Click to expand...
Click to collapse
I don't know if he's been back on since his initial post.

wolfu11 said:
I don't know if he's been back on since his initial post.
Click to expand...
Click to collapse
Last Activity: Today 12:52 AM
good luck :fingers-crossed:

autoprime said:
Last Activity: Today 12:52 AM
good luck :fingers-crossed:
Click to expand...
Click to collapse
Not holding my breath lol. That's why I declined any of the root bounty.

Try manually pointing to either the lg drivers, or adb drivers had that same problem when trying to root H830.
Sent from my LG-H830 using XDA-Developers mobile app

IDK if u fixed it or not, but i have a simular issue where LGUP does not recognize my phone. i'm guessing it could be the buildprop could have broken it. i have factory reset my phone, but upon turning on wifi, the phone crashes and i need to factory reset. i am rooted and retain root. My guess is that changing the buildprop causes the phone to be unrecognized. I did backup my buildprop but its stuck in an encrypted backup. Thanks alot gooogle...

Same problem here
I am having the same problem but I never touched my build prop. I rooted and decided to install cm14. When i flashed, none of my partitions are mounting and phone would not boot. I put stock back on and flashed tot and tried mounting partitions and nothing. Now computer doesn't recognize it as well as it will not boot into recovery or android.

I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.

Barsky said:
I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.
Click to expand...
Click to collapse
ill give it a shot, thanks

Setting phone back to defaults for dummies

It doesn't appear anybody knows what to do with this http://forum.xda-developers.com/general/xda-assist/incoming-calls-answered-vener-make-to-t3500914 and I now have to go back to full factory stuff with no custom recovery and stock os to find out if this is a hardware issue. I did a TWRP restore from several months ago when the phone worked fine and it still has the incoming call issue from the link above. Did a factory wipe in Teamwin, same thing.
Rooted Sprint Galaxy S6 on Lollipop 5.1.1 with Teamwin recovery
http://tiribulus.net/pix/Phone/1.png
http://tiribulus.net/pix/Phone/2.png
Please pretend than I am a not particularly precocious ten year old who needs to make this phone as if I just took it outta the box. I have searched here and around the web. All I find elsewhere are paid download sites or 3 hour downloads and here I can't make heads nor tails out of the volumes of impressive information in these forums.
I do have PC skills, and this is my first smart phone and getting it rooted and the recovery installed and all that wasn't too tough back when I got it 15 months ago. It appears restoring it back to stock is quite a bit tougher.
I have to see if incoming calls still don't work when the machine is totally stock. Is there a way to do this without a 3 hour download and a masters in computer science? I sure would be most grateful for any help with this.
Thank you.

You can simply do "Rescue firmware" via Smart Switch.

forumber2 said:
You can simply do "Rescue firmware" via Smart Switch.
Click to expand...
Click to collapse
Thank you sir! I will have a look at this a bit later tonight when possible.

This won't work with Teamwin recovery right?

I have none of the boot options in this video. Not that I don't appreciate it.

I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.

http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448

brenner650 said:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Click to expand...
Click to collapse
I appreciate that sir, but like I say, I never get step 4. It doesn't exist for me. As soon as I click the device initialization tab I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I proceed, I get this:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix. That's what started this whole thing:
http://forum.xda-developers.com/spr...er-make-to-t3500914/post69641921#post69641921

Tiribulus said:
I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.
Click to expand...
Click to collapse
You won't do anything on TeamWin.
1. Open Smart Switch on PC.
2. Turn Off the phone. Press Volume down (not up) & Home button & power button. When you see the warning screen, just press volume up once. If you see "Downloading" screen, plug into PC
3. Do "Rescue Firmware" via Smart Switch.
Thats it.

Tiribulus said:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix.
Click to expand...
Click to collapse
Well they had to write that, because if something happens during flashing it is not their fault, and you have been warned.
You can also uninstal supersu, and download that same fw Smart Switch would install from another internet source, and it will probably be a painfully slow download, but that is up to you.
I cannot guaratee you that Smart Switch emergency initialization would solve your phone issues, but it is the way to unroot and for the phone to become officially stock, offcourse knox will stay tripped if it was tripped during rooting (and probably is, unless you are on 5.0.2. and were using ping pong root).
I used Smart Switch emergency a lot, and it was always succesfull, just follow instructions, connect your phone in dowload mode when it asks for it, and there should be no problems getting to stock.
...I saw just now, in your other topic that you have fixed it /thumbs up!

New Update - QC2

According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip

If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.

I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.

I'm gonna try it out when I get a chance this week. Thanks!

Has anybody tried this?

robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk

Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.

Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.

Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?

I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.

@Dudash QD1 is up, can you upload it to AFH. thanks in advance.

Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.

Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks

J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.

Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?

J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.