Database Info

VZW OTA 4.4.4 Just pushed.

Anyone else just get this pushed? Noticed a few cosmetic differences. Foxfi seems to still work, but I will test that fully when I get home. I am not rooted.

I wonder if the bootloader is the same.

I have an update, not sure if it is 4.4.4 but it says it fixes bluetooth media failure or something like that.

jerkules said:
I have an update, not sure if it is 4.4.4 but it says it fixes bluetooth media failure or something like that.
Click to expand...
Click to collapse
That's what it originally stated with mine. I checked the build after the update and noticed 4.4.4.

Were you rooted when you updated?
Sent from my GT-P5210 using Tapatalk

rhodiggah said:
Were you rooted when you updated?
Sent from my GT-P5210 using Tapatalk
Click to expand...
Click to collapse
No. I've never rooted this device.

loonie01 said:
I wonder if the borrower is the same.
Click to expand...
Click to collapse
I'm not sure what that is :-/

@muniz_ri and @open1your1eyes0 I have the ota downloaded here if you want to take a look.... It's pretty big 346 mb. I haven't installed it yet. To anyone else, I would refrain from installing this if you value root. Wait until it's checked out to see if it's safe.
KitKat4.4.4 OTA
MD5: 1ad228f1c2871ddb8b881e4f576216b1
EDIT: This is confirmed safe.

Anyone who has taken the OTA already
Please try this method for now: http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
We will get NHA kernel and flash that later (building it for you guys now).
UPDATE (built): From step 6 from above method use this file instead: G900V_NHA_Stock_Kernel
Anyone who is rooted on NE9 build with Safestrap (and willing to help us out with a test)
Please try flashing this version of SuperSU.zip in Safestrap recovery and enabling "Survival Mode" on your current build, then taking the OTA and seeing if root survived.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Misterxtc said:
@muniz_ri and @open1your1eyes0 I have the ota downloaded here if you want to take a look.... It's pretty big 346 mb. I haven't installed it yet. To anyone else, I would refrain from installing this if you value root. Wait until it's checked out to see if it's safe.
KitKat4.4.4 OTA
MD5: 1ad228f1c2871ddb8b881e4f576216b1
Click to expand...
Click to collapse
Thanks for the file, I will check it out. Also, I may need help with testing a solution to keep root so pm me if interested.

I got the same Bluetooth update, earlier today and noticed that it was Android 4.4.4 too. Phone appears to run snappier too. Haven't really noticed any cosmetic changes.
I'm also getting this annoying "Voice Mail Update: Your Voice Mail service has been updated. Tap here to set up your service." in the notification tray. Haven't found a way to get rid of it completely.
I would use it, but I have Google Voice setup for voicemail.

tformed said:
I got the same Bluetooth update, earlier today and noticed that it was Android 4.4.4 too. Phone appears to run snappier too. Haven't really noticed any cosmetic changes.
I'm also getting this annoying "Voice Mail Update: Your Voice Mail service has been updated. Tap here to set up your service." in the notification tray. Haven't found a way to get rid of it completely.
I would use it, but I have Google Voice setup for voicemail.
Click to expand...
Click to collapse
Any chance you can help us test this? http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For step 6 use this file instead however: https://www.androidfilehost.com/?fid=23622183712469066

open1your1eyes0 said:
Any chance you can help us test this? http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
For step 6 use this file instead however: https://www.androidfilehost.com/?fid=23622183712469066
Click to expand...
Click to collapse
I just tried it and it didn't work. After flashing NHA the phone rebooted and stayed at the Samsung boot screen. Thankfully I was able to Odin back to NE9.

Misterxtc said:
I just tried it and it didn't work. After flashing NHA the phone rebooted and stayed at the Samsung boot screen. Thankfully I was able to Odin back to NE9.
Click to expand...
Click to collapse
Did you take the OTA and were able to get it rooted before flashing NHA kernel back (step 6)? At which step of that method did it pass/fail?

open1your1eyes0 said:
Did you take the OTA and were able to get it rooted before flashing NHA kernel back (step 6)? At which step of that method did it pass/fail?
Click to expand...
Click to collapse
I didn't take the OTA. I Odined back to stock NE9, then to NCG to root and then to NHA. Odin didn't fail but rebooting did. After Odin flashed NHA it rebooted but got stuck at the boot screen. It just sat at the Samsung boot screen, even after another reboot. Than I Odined back to NE9 and all is good again.

Misterxtc said:
I didn't take the OTA. I Odined back to stock NE9, then to NCG to root and then to NHA. Odin didn't fail but rebooting did. After Odin flashed NHA it rebooted but got stuck at the boot screen. It just sat at the Samsung boot screen, even after another reboot. Than I Odined back to NE9 and all is good again.
Click to expand...
Click to collapse
As per the steps on that method you should take the OTA first (the full NHA OTA on stock unrooted), then flash the NCG kernel just your can reroot and flash the NHA kernel kernel back after you have root.
I'm not sure you can run NHA kernel on NE9 build, that may be why you're getting stuck.

open1your1eyes0 said:
As per the steps on that method you should take the OTA first (the full NHA OTA on stock unrooted), then flash the NCG kernel just your can reroot and flash the NHA kernel kernel back after you have root.
I'm not sure you can run NHA kernel on NE9 build, that may be why you're getting stuck.
Click to expand...
Click to collapse
Ok, seeing that I already flashed the NHA kernel and flashed back to NE9 should mean that NHA isn't incremented?

Misterxtc said:
Ok, seeing that I already flashed the NHA kernel and flashed back to NE9 should mean that NHA isn't incremented?
Click to expand...
Click to collapse
If you're referring to the bootloader update that's included in the OTA, unfortunately without testing we have no way to tell at the moment. Someone needs to just be brave enough to take the OTA for us and see if they can flash back to NE9 after.

Okay folks, you all are super lucky today as I decided to be impatient and personally test this out for you guys. Confirming the below method fully works for me.
Make sure you are on stock unrooted NE9 build (if not flash this NE9 firmware in ODIN)
NOTE: If you are on a newer firmware just flash the stock firmware for the version you are running instead - if needed
Take the NHA (Android 4.4.4) OTA and confirm all is working
NOTE: If you are on a newer firmware just take the OTA for whichever is next version instead until you get to the latest
Flash the NCG kernel in ODIN: http://www.androidfilehost.com/?fid=23578570567722142
WARNING: After flashing this kernel you may get lots of crashes and hanging but try to push through to next step below little-by-little.
Root using Towelroot: https://towelroot.com/
Install/Open SuperSU and let it update the binary normally
Flash the NHA kernel (I provided earlier) in ODIN: https://www.androidfilehost.com/?fid=23622183712469066
NOTE: If you are on a newer firmware just flash the kernel for whichever version you are on
Reboot and you should be all set
Video guide courtesy of DroidModderX:

open1your1eyes0 said:
Okay folks, you all are super lucky today as I decided to be impatient and personally test this out for you guys. Confirming the below method fully works for me.
Make sure you are on stock unrooted NE9 build (if not flash this NE9 firmware in ODIN)
Take the NHA (Android 4.4.4) OTA and confirm all is working
Flash the NCG kernel in ODIN: http://www.androidfilehost.com/?fid=23578570567722142
Root using Towelroot: https://towelroot.com/
Install/Open SuperSU and let it update the binary normally
Flash the NHA kernel (I provided earlier) in ODIN: https://www.androidfilehost.com/?fid=23622183712469066
Reboot and you should be all set
Click to expand...
Click to collapse
Cool. I'm surprised vz didn't blackball the ncg kernel to run on the new firnware but good for us!

G900P MM downgrade

HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?

I just flashed the OK4 tar via odin to go back to stock and take the MM update again. I wiped everything but internal and external storage in TWRP first. It's currently downloading the MM update.

i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.

pyrochance said:
i've successfully taken the PCA update twice, and used ODIN to go back to OK4 and update once again.
the bootloader does not appear to lock firmware.
Click to expand...
Click to collapse
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk

djxn40 said:
So you just odin back to ok4? No other steps required?
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.

pyrochance said:
Correct, because when you odin OK4 it restores the stock recovery and everything else etc, so everything is stock again, system status is official etc. then you can either download the OTA as normal or take the zip from your thread and update from stock recovery. i've done it both methods.
Click to expand...
Click to collapse
I assumed you couldn't revert. That's awesome though thanks
Sent from my SM-G900P using Tapatalk

I can also confirm that too, I just did a downgrade to OK4, after I unsuccessfully tried to downgrade to OA6. I assume that pyrochance (http://forum.xda-developers.com/showpost.php?p=66266625&postcount=138) is right.

If i was helpful, feel free to hit the thanks button on those posts

Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.

ZedDedd said:
Are you rooted? I'm not rooted, and from BOK4 I was not able to downgrade via Odin to an earlier firmware that supports towelroot. I am now on Android 6 (OTA). Question - on Android 6 is it now possible to downgrade to an earlier firmware (without root, and without tripping knox)? If so is it only to BOK4? Thanks in advance.
Click to expand...
Click to collapse
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?

Kreatur3 said:
Yes. You can only downgrade to OK4. If you weren't able to go to a previous version when on OK4 why would you be able to once beyond it?
Click to expand...
Click to collapse
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?

ZedDedd said:
Thanks Kreatur3, was thinking that with the new firmware they might have relaxed their restriction on downgrading. I would think that with any new official firmware, they could pretty much do whatever they want, like even take out all protections and allow you to root without tripping knox (which I know they wouldn't), or am I misunderstanding something?
Click to expand...
Click to collapse
They could allow it but won't. It's obvious with the direction they are going with the s7. I can see why maybe providers don't want you to have that power but don't know why the manufacturer cares. Beyond the pressure from cell phone companies. I don't care about knox personally. I'm way beyond the warranty period and trip it every time the day I gety phones.

highspeedfelon said:
HI I was wondering if anyone could help verify that the downgrade is possible from 6.0 to 5.0 OK4. I used Odin to flash the stock OK4 firmware to my phone when I was on the 6.0MM firmware and I just want some one that is willing to test what I did just to verify that I wasn't just lucky.
What I did was while on 6.0 I setup ADB for the phone, rebooted to download mode and used Odin3-v3.10.6 to flash G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar (got this from sammobile). When phone rebooted it got stuck at the boost logo screen for longer than I liked so I used "ADB reboot recovery" command and in recovery did a factory reset and then booted into system and I am having no issues. So can some one else test this so that I know it is a 100% way to downgrade?
Click to expand...
Click to collapse
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You

alphadude said:
You are a life saver it feels like i have been searching for a fix for ages and then my path led to here.
I am confirming i have downgraded successfully and i was on 6.0.1 MM tried OA6 and few more nothing worked but the OK4.
Thank You
Click to expand...
Click to collapse
You are welcome.

I'm having a bit of trouble. I was on MM, then the phone started freezing up. So I went back to OK4 but I can't get past the Samsung boot up logo. It stays on there forever and doesn't move past it. I even tried to replays through Odin multiple times but still not working. I'm stuck.

Soft Brick S5 Software Update Failed message

Was on NCG with root, unlocked the Developer mode http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..

ProSeriesRacing said:
Was on NCG with root, unlocked the Developer bootloader http://forum.xda-developers.com/ver...king-galaxys-s5-bootloader-t3337909?nocache=1 , installed PD1, device restarted with Verizon screen waited 20 mins pulled battery wiped cache, restarted and than tried to go back to NCG with odin. Now I have Software Update Failed message. Still can get into download mode
Not sure what to do now or what file to get to fix this..
Click to expand...
Click to collapse
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.

smokerbond said:
Ouch... If you were on NCG with root your bootloader was not locked.
I hope you verified your eMMC was not an 11xx or you may have just locked your bootloader for good (as of this writing).
Your best bet is to restore to a stock tar- although given your situation I am unsure of the best action. When you installed PD1 did that include the bootloader? If not, you should be able to just flash a stock NCG tar with odin. If it fails though, like you are saying- your bootloader might be locked to OG5+ so you may have to flash a stock OG5/PB1. If I recall correctly, PD1 can still downgrade to PB1 where you can reacquire root. From there you could verify your eMMC and proceed to re-attempt the bootloader unlock and then go to custom rooted MM roms.
Click to expand...
Click to collapse
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.

smokerbond, Thank you . Back up & running again

ProSeriesRacing said:
Yes eMMC was 15. After doing the Developer , it was verified with Mode: Devoloper. The bootloader was not included but after it failed to restart, I odin the bootloader and that is when I got the message. I have tried to install the stock NCG with odin but it fails. I try and get OG5 and flash that.
Click to expand...
Click to collapse
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?

al50 said:
You can unlock your bootloader if you're on KK. You just have to take the appropriate steps to get to PD1(MM). Pretty sure it's a simple fix. Just go to the unlockedbootloader thread and read throughthe OP and do a search within that thread. There's a fix for your mishap. Just don't "flash" things thinking it'll "fix" your problem because that will just dig you deeper into your problem. What does it say when you go into DL mode as far as system?
Click to expand...
Click to collapse
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.

ProSeriesRacing said:
Yes, on PB1 now. Read jrkruse, OP on rooting PB1 now. System is Official.
Click to expand...
Click to collapse
Ok. Glad to hear that you've gotten your device up and running.

DISCONTINUED_[VZW_Stock TW Rom][6.0.1 MM QA1 Build Odex For Locked Bootloader SafeStrap Only]

Do Not Flash This On Unlocked Bootloaders Or You Will Relock Your Bootloader!!!​Once your on MM 6.0.1 you cannot restore a Lollipop Backup using SafeStrap or vice versa. Follow the link at bottom of post for guide and files to downgrade back to Lollipop
Ok the first thing I want to make clear is YOU WILL NOT HAVE ROOT! You will still have the use of Safestrap Recovery even though phone will not be rooted. What this will allow you to do is boot the non rooted rom back into safestrap. While in Safestrap you can do what you have always done, Flash Zips, Make Backups,Etc. This will also make it easy if you want to go back to PB1 rooted rom.
You must be on A rooted rom preferably A PB1 rom running SafeStrap
If Running FlashFire
Make sure latest busybox is installed
Install MM_Safestrap.apk
Reboot to safestrap
Wipe Data,Cache,System
Install VZW_QA1_STOCK_SAFESTRAP_ONLY_V2.zip
Roms will take a long time to boot up be patient!
This will put you on pure stock rom MM QA1 rom but from here you can get to safestrap to flash other roms or mods
To return to Safestrap you will need to flash a kitkat kernel NI2_stock_kernel.tar.md5 using odin then when phone reboots click on enter safestrap recovery. When leaving safestrap you must flashMM_KERNEL_SS-FF_Flashable.zip. Which will be located on your internal storage In a folder called MM_KERNEL_SS-FF_Flashable
If you want to flash other custom roms a guide can be found HERE

Useful zips
View attachment ADBlocking_2_5_17.zip
View attachment DebloatScript.zip

Thanks Jkruse!
Question... I tried your stock PB1 before and it worked well. I however hosed myself flashing the incorrect firmware and USB bulk mode occured when I attempted to go back to PHX11 5.0 ROM. I flashed firmware as when I reloaded the backup of PHX 11 I had no data or wifi.
I saved the phone however and need to know what is the correct procedure to go back to LP backups if I try this and decide not to stay? I want to avoid bulk mode again!
Thank you!!

ridenickel9 said:
Thanks Jkruse!
Question... I tried your stock PB1 before and it worked well. I however hosed myself flashing the incorrect firmware and USB bulk mode occured when I attempted to go back to PHX11 5.0 ROM. I flashed firmware as when I reloaded the backup of PHX 11 I had no data or wifi.
I saved the phone however and need to know what is the correct procedure to go back to LP backups if I try this and decide not to stay? I want to avoid bulk mode again!
Thank you!!
Click to expand...
Click to collapse
Once your on this rom The link at the bottom of the OP has a guide and files for going back to lollipop BP1 build without having to reroot. It's in the second post of that guide

jrkruse said:
Once your on this rom The link at the bottom of the OP has a guide and files for going back to lollipop BP1 build without having to reroot. It's in the second post of that guide
Click to expand...
Click to collapse
I'll read up! Thank you!!
Would this be the same procedure for OG5 just substitute the PB1 caution firmware with OG5 caution firmware? I assume just match the ROM you go to with the caution zips that don't contain the bootloader.
Pretty sure I didn't use the caution firmware before and that what caused my issues.

ridenickel9 said:
I'll read up! Thank you!!
Would this be the same procedure for OG5 just substitute the PB1 caution firmware with OG5 caution firmware? I assume just match the ROM you go to with the caution zips that don't contain the bootloader.
Pretty sure I didn't use the caution firmware before and that what caused my issues.
Click to expand...
Click to collapse
If you goback to lollipop it will need to be PB1

Added debloat script to post 2 that can be flashed with safestrap

jrkruse said:
If you goback to lollipop it will need to be PB1
Click to expand...
Click to collapse
OK thank you for clarifying. I use PHX 11 and always need to flash the OG5 kernal from safe strap so I assumed I'd need OG5 firmware for that particular situation.
Also thanks for updating the OP about using backups to and from MM - that will help others avoid issues.
I'll stop clogging the thread now! Appreciate all the information and work you do!!

Hey, thanks for this great site and all of your guides. It really helps.
I just rooted my s5 g900v and Im still on KITKAT NK2. Would it be possible for me to update from that version to this one following your guide?
Sorry for asking really basic questions. My phone at the moment is sim unlocked and rooted, but CID starts with 11 so I cannot unlock the boatloader, right? Then I assume this ROM is my best option. I want to be really sure that I will still be sim unlocked on the new ROM, its got nothing to do with it, right?
Many many thanks in advanced!

nachoalt said:
Hey, thanks for this great site and all of your guides. It really helps.
I just rooted my s5 g900v and Im still on KITKAT NK2. Would it be possible for me to update from that version to this one following your guide?
Sorry for asking really basic questions. My phone at the moment is sim unlocked and rooted, but CID starts with 11 so I cannot unlock the boatloader, right? Then I assume this ROM is my best option. I want to be really sure that I will still be sim unlocked on the new ROM, its got nothing to do with it, right?
Many many thanks in advanced!
Click to expand...
Click to collapse
Yes you can update to this rom and also verizon phones are all sim unlocked so it will rermain sim unlocked. Just remember if your still on kitkat when you flash anything with safestrap do not use rom slots flash on the stock rom slot. If you dont know what this means then dont worry about it

jrkruse said:
Added debloat script to post 2 that can be flashed with safestrap
Click to expand...
Click to collapse
Thanks for the hard work, unfortunately my cid 15 just took a nice fat swim and i had to get a replacement and got a cid 11 instead (##$$%@@@!#[email protected]). Your guides have been great to get to this point but got a couple questions:
Any link to what the debloat script removes? I just ran it and it doesn't seem to remove anything (ran it at same time as addblock). Going to reboot and flash it again see if it does. Any way we can remove the stuff we don't want? (all the VZW junk)

New Update - QI2

According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.

so its safe to say that the new modem ql2 is pretty much the same sa the previous update?

Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.

Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse

For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse

I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.

You will also have to re-flash TWRP via Odon.

kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.

I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.

I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!

purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.

bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??

purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:

Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks