According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
Related
I have done flashing and rooting in the past on both a Samsung Charge, Nexus and S3, but it's been a while. Ive used Odin, and the TOOLKIT, and am somewhat familiar with both.
I have had my S3 for several years, STOCK, STOCK, STOCK, and liked it just the way it was. I had a WIFI tethering app, SVTP that worked, and didnt take updates for fear it would quit working, well I accidentally took an update, and now it doesnt work.
Id like to reflash the phone back to a previous stock software, I forget which one I had, but currently here is my phone info
SCH-I535
4.3
I535VRUCML1
KERNEL 3.0.31
build JSS15J.I535VRUCML1
hardware I535.10
I believe I had Jellybean, or a 4.0 firmware.
How should I flash this back, and where can I download the files and the correct version of ODIN?
So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?
Nitro169 said:
So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?
Click to expand...
Click to collapse
As long as your not on the NC1 or NE1 baseband/firmware you can indeed revert back to an older version. And you do indeed have to unlock the bootloader to revert to a previous version of Android
In my personal opinion your best bet is the casual root/unlock method which will do both for you
Sent from my Nexus 5
so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.
Nitro169 said:
so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.
Click to expand...
Click to collapse
Because your on a locked bootloader and downgrading now would brick your device
Sent from my Nexus 5
Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?
Nitro169 said:
Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?
Click to expand...
Click to collapse
Check swappa for that. I know brand new ones have the newest firmware, your better bet is swappa
And no they are locked down tightly, unlocking is nearly impossible
Sent from my Nexus 5
what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?
Nitro169 said:
what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?
Click to expand...
Click to collapse
No, you can't get around the locked bootloader. Your stuck on it
Sent from my Nexus 5
I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.
MrBrady said:
I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.
Click to expand...
Click to collapse
You are correct. I did a quick search and those who took the 4.3 ML1 OTA are indeed on a locked bootloader
Sent from my Nexus 5
(From later on in this thread)
Jaxas said:
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
=============== ORIGINAL POST ===============
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Jaxas said:
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
So far, the CDMA versions of the A9 can't run Nougat. As you know, HTC hasn't updated it for Nougat, and our phones run different enough firmware from the GSM-Locked and Dev versions that we can't use theirs. And so far, HTC's Dev Nougat requires Nougat firmware. So... we're boned.
Hopefully this won't be forever; HTC should eventually update American phones, so we'll just have to factory reset from system image (and maybe RUU) and OTA. For now, we can only hope guys like Captain_Throwback figure out how to backport Nougat to the 1.60.651.4 firmware.
Jaxas said:
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
hey,
can you try this ...
https://forum.xda-developers.com/one-a9/general/htc-one-a9-android-7-nougat-t3546557
New info: Nougat is now available via OTA. Now we just need to... get back to full stock.
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
TWRP 3.0.3 beta is available for nougat
MGfusion said:
TWRP 3.0.3 beta is available for nougat
Click to expand...
Click to collapse
I saw, but I'm not sure what's going on in the thread right now. It seems it sometimes bootloops? I'm hesitant to upgrade until there's either an RUU for 2.whatever out or I'm sure TWRP is reliable. I'm resigning myself to living without Xposed, but I at least need root and Magisk.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
Whelp.
I'm upset, lol.
Time to re-reset my phone (finally got it set back up the way I wanted it yesterday on 6.0.1)
Oh well, thanks for the heads up!
I have the Sprint a9. I flashed the ruu and flashed TWRP 3.0.3-1 I believe, with no issues
Okay, so before I go re-wipe my phone and upgrade, I have a few quick questions...
1) Can this update be flashed with S-ON? (I'm assuming so, but always good to check) and
2) Can the Sprint A9 be rooted on Nougat yet?
Thanks!
I used TWRP 3.0.3.-4 and root with Magisk. Still miss Xposed, but the N features are pretty nice too. All seems to be working well.
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Jaxas said:
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
If you don't have an unmodified system image from before you mounted the system partition then yes, you do have to use an RUU, which will also give you stock recovery. No, you don't need to do anything with the bootloader.
Flash the RUU for the version you're on now, start up normally and take the OTA. No, I didn't have to do anything special besides making double checking /system is mounted read-only in TWRP. Personally I like using Magisk for root, etc, but I've heard SuperSU works fine. too. I'm S-on as well and it was all very easy.
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
samweli benjamin said:
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
Click to expand...
Click to collapse
What is your CID, MID and version-main? Is your bootloader locked or unlocked? S-ON or S-OFF?
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
samweli benjamin said:
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
Click to expand...
Click to collapse
What ruu version were you trying to flash and what was the error?
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
samweli benjamin said:
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
Click to expand...
Click to collapse
You can't flash a nougat ruu (2.xx.xxx.x) on a phone running the marshmallow firmware (1.xx.xxx.x). You need to manually update your firmware to 2.xx.651.x before being able to flash the 2.18.651.2 RUU. This is because the new signature key implemented in all 2.xx.xxx.x ruu, explained here at faq #4
Or you can flash the older 1.60.651.4 ruu and after, update your phone using OTA updates. Probably the easiest way for you :good:
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.60.651.4.exe
This seems to be of great help to me, but am afraid i can't install the OTA in my device, b'se I received it and i did downloaded it but when i click to install it finish unzipping file and then fail and the phone boots in TWRP recovery so i thought i can update it by running a RUU side load
Still says 2017-08-01 security patch, but now with Blueborne and Krack patched as well.
https://www.verizonwireless.com/support/galaxy-s5-update/
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar .md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot.tar.md5.zip
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
stormified said:
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
Click to expand...
Click to collapse
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Dudash said:
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Hi, I am running the Resurrection Remix Final N ROM on my g900v and I have this bootloader (g900vvrs2dqb2). I looked it up and saw that it was from February 2017.
I would like to update my modem and boot so I am ready for Oreo but I'm not sure best way to go about it,(Odin)?
I know this information is available on XDA and probably in this forum, but I am paranoid because I had a hell of a time unlocking the bootloader because I was fallowing old directions.
I would be very grateful to anyone willing to point me towards simple, but accurate directions.
Thanks in advance, and apologize for my ignorance!
Sent from my kltevzw using XDA Labs
Awesome! Thanks very much. I'm gonna give this a shot like the previous install/upgrade some time Friday afternoon PDT.
Jeebus I need sleep....
Can I flash this over LOS in TWRP to return to stock or do I have to use Odin?
Once flashed will the bootloader remain unlocked to allow me to reinstall LOS?
I got a new screen installed and it appears there may be an issue with how the digitizer interfaces with the software/kernal and going back to stock should update the software to allow the screen to function normally then allowing me to reflash LOS.
Hey Everyone,
Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days. The time has come to finally update my phone because some of the apps won't work anymore. I'm not into ROMs and stuff, I just want the latest firmware without all the bloatware. I had originally gone the TowelRoot method because people were having such a hard time with battery life (me included) with Lollipop. I was fortunate enough to get TowelRoot before updating to the newer version of Lollipop and went back to KitKat and I've been there ever since.
I'm currently on G900VVZW1ANCG (Kitkat 4.4.2) with root access and superuser. I have a CID 15 emmc which is a good thing from all the research I've been doing on XDA.
That's where I get stuck and confused with the newer stuff that's going on. Do I even need to unlock the bootloader?
In the end, I don't mind wiping the entire phone, I just want to get to the latest Marshmallow (which this thread seems to have) without all the bloatware or the ability to delete all the bloatware.
nickbike1 said:
Hey Everyone, Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days...
Click to expand...
Click to collapse
Welcome back!
You had asked some questions that is actually 2 separate ones upon themselves and I'll, hopefully, try to answer them...
Question 1: Should you unlock the bootloader?
Answer 1: The only need for anyone to require this is if they want to perform something outside the scope of just Rooting a device.
What I mean is... for example, if an individual would like to install a Custom Recovery and/or Firmware then you will need to unlock the bootloader.
Question 2: You would, ultimately, like to just debloat the Firmware?
Answer 2: Debloating Stock Firmware only requires root and not an unlocked bootloader.
The proper rooting of a device just means that you will be able to modify areas of the root directory that's restricted for devices without root and Debloating falls into this category.
Just an FYI regarding the following 2:
1) The 2 differences between the CID11 & CID15...
GS5 with CID11 = Toshiba EMMC
GS5 with CID15 = Samsung EMMC
2) There are a handful of Custom Firmwares that are based upon the stock Firmware that is already Debloated. Some of them only requires a Rooted device and Some requires an unlocked bootloader and recommends a Custom Recovery like TWRP.
This is just a brief summary to help you further but, I would recommend that you take note of/highlight the following 2threads that would be a bit more helpful depending on what your looking to do.
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=3561529
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Full System Backup method needed!
BigBird9906 said:
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Click to expand...
Click to collapse
1) -Yes, I just tried it, and it works perfectly! The only correction - you have to unzip
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip file and flash md5 file with Odin (Odin won't work with that zip file).
2) -I have exactly the same question to fellow members - what is the current most simple and reliable method of full system backup (like ghost image for PC)? I want to try Lineage, but I already spent many hours on system customization (applications, app settings, accounts with login names/passwords, etc.). I really need some fast method to revert phone back to QL1 with all my current setup. I will flash again System and TWRP from Odin, and Magisk from TWRP. How can I then restore my full setup with one click? I used to use 'Titanium Backup' in the past, but that is not an option anymore. It freezes every time when I try to restore 'All apps with system data'
Thank you for reading that and for any possible advices.
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Nerva said:
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Click to expand...
Click to collapse
If your looking for the Baseband Modem Firmware, the following link has them all for the G900V and won't affect what you have (i use them on my Unlocked G900V to update the Modem Baseband Firmware and I've got TWRP and LineageOS).
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks. Are the baseband modem firmware also included in the QL1 "Developer Bootloader Friendly/No Aboot No-Wipe Firmware"? I've been told I should upgrade both my modem and bootloader, but I don't want to re-lock my unlocked bootloader.
WTF?? I was running TWRP 3.2.1.0 and crDroid 7.1.2, and I used Odin to flash the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" and checked the BL and CP options, which I thought should update just the bootloader and modem, and now it boots up with the Samsung logo and then the Verizon logo, and then just sits there. I tried to go to recovery so I could restore a backup, but it looks like the stock recovery. What did I do wrong and how do I fix it??
Since crDroid 7.1.2 is older than the bootloader, I'm wondering if that's the issue. I do have crDroid 8.1 on the microSD card. I also have TWRP 3.2.1.0 on the microSD card. So I'm wondering if I can use the stock recovery to flash TWRP. I haven't played around with custom ROM's in four years, but prior to that I did it all the time, so apparently I now remember just enough to be dangerous...
@Nerva, I apologize for the delay but, I'm curious to know where, why and what gave you the impression that you were/was required, on your your working device, to update your devices bootloader???
I'm just perplexed about this...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I went back and tried to find where I read it, and at the very least it was in this post:
godofsalt said:
Yep all true. .... But....
Once he sends you the info (model numbers and such) might want to also double check that he is on the latest firmware, for his devise. Important!
All reads good. If it's rather, "New" then, I would keep it as well.
Click to expand...
Click to collapse
I think I saw it someplace else as well, but I haven't stumbled across it -- I was posting a lot of questions in a lot of threads as well as PMing people.
Nerva said:
I went back and tried to find where I read it, and at the very least it was in this...
Click to expand...
Click to collapse
Your situation prompted me to confirm what I knew and others that you can see on the recent posts on the following thread...
https://forum.xda-developers.com/showthread.php?t=2259645
... I just wanted to state that if your devices bootloader was already unlocked and the device wasn't bricked (or similar) then you should not need to update the bootloader or it'll lock it up again and, potentially, can even cause FRP issues as well. Luckily your FRP didn't trip and the device was able to be unlocked again.
I have the same device that was unlocked a long time ago and never ever needed its bootloader updated.
Your question regarding the Baseband Modem Updates...
Those are the Modem files extracted from the stock Firmware and only updates the devices Modem. That controls the WiFi, Carrier Data, etc...
This is similar to updating the Drivers for something specific on a PC (like the PC LAN, WiFi, Video Card, etc... ).
When you had flashed what you did on your device, you basically flashed an optimized version of the Stock Firmware. This is why you saw the Samsung Boot Screen.
I hope that I had explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?
It looks like this website will generate a cf-auto-root package for QL1:
https://desktop.firmware.mobi/device:840/firmware:14884
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Nerva said:
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?...
Click to expand...
Click to collapse
I'm not stating that Bootloaders doesn't get updated upon themselves but, they specifically seldom require it.
One way to look at it is that the function of the bootloader is allot like the BIOS of a PC. They both handle the boot process and seldomly require to be updated specifically.
When a new Stock Firmware version is released, the bootloader is only updated accordingly to reflect the updates of the firmware. This reflection is to protect the device from being updated to an incompatible firmware version.
In short, when the bootloader is unlocked, the bootloader still protects the device from an incompatible firmware from being installed but, it being unlocked just bypasses the "Samsung Stock firmware only" restriction.
TWRP is just the conduit between the Firmware and the bootloader that just handles the communication between the bootloader and the Firmware.
.
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Click to expand...
Click to collapse
If you flash the firmware, your just going to relock your bootloader and be back to stock.
To get the QL1, just flash the Baseband Modem Update from the following link and you'll be good to go and you'll see this in your device info.
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Have I clarified this okay?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Id like to downgrade my S7 from nougat to marshmallow. My current lowest factory reset option is nougat on bootloader version 3. Id like to downgrade to a downloaded stock firmware that uses version 1 of the bootloader.
my device is currently rooted and carrier unlocked
ive made a full backup of the nougat system, before ive done anything to it other than the rooting.
ive been reading around that some people were able to bypass the downgrade bootloader lock error in odin by first going into their desired downgraded firmware tar files and deleting any file that ends in .bin , and then successfully been able to flash the older firmware. what I want to know is if i decide to try this, and it still doesnt work in odin, or something still doesnt work properly - am i still able to fully restore from that backup ive just made? has anyone done this without issues? i hate the look and feel of nougat and oreo looks and feels the exact same...
i did make another thread about downgrading, but i didnt know nearly as much at the time. Been told downgrading is impossible and thats true, officially speaking. Id just like to know if anyone has been successful with this workaround.
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Beanvee7 said:
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Click to expand...
Click to collapse
model is sm-g930w8 but yes OEM unlocking is on, and so is usb debugging just to be on the safe side. It is running the very first version of nougat right now, 7.0. But the security patch is from feb 2018. Ive read that the bootloader itself is unlocked on this version of the phone though, its just that downgrade protection in the software that could get in the way, if what i read was correct? in the same place was where i read that deleting those bin files from the firmware i want to install would be a good workaround, it would make the bootloader not check it at all if i read it correctly.
i havent tried anything yet, ive been doing my research first to stay on the safe side. it might work without issues, but I want to be prepared for if issues do arise, what the correct next step should be to keep the device itself not bricked
Yea not 100% sure for the G930W8, it's the same SoC as the G930F but the firmware restrictions could be different since it's the Canada specific version
so, i decided to brave it and try it, since to read around you find alot of conflicting information... i was suspecting that odin would fail shortly after starting at sboot.bin if it was the bootloader thats the issue. but it didnt. it failed the very next step after that at param.bin.
anyone happen to know what param.bin means?
What files are you trying to flash? I have had the same problem, even though the bootloader is unlocked the device has efuses that prevent downgrade to older binary. I was using U2 binary and only managed to downgrade to nougat u2 binary version. Even when I skipped bootloader files, marshmallow would still give an error that system.img is version 0 where as device is v1
I bought a used S10e. It is Android 9, and OTA not find newer FW. Can i change the SW without risk?
Have you a noob tutorial, how can i do it?
Which ROM is suggested? Which have minimal bugs, and great battery time? I prefer the non-root original FW.
Android 9
G970FXXU3ASH3
Build: G970FXXU3ASH6
SAOMC_SM-G970F_OXM_XEH_PP_0014
Knox 3.3
Odin can upgrade, and downgrade FirmWare, when OEM unlocking is Enabled, in developers settings.
Downgrade too? I have andoid 11 and i wanna back to 10. There will be no problem with bootloader? (sometimes new android get new bootlader and then u cant back to old android - heard something like that)
edit:
I will answer myself: yes, U can downgrade without any issue
wmiki75 said:
Odin can upgrade, and downgrade FirmWare, when OEM unlocking is Enabled, in developers settings.
Click to expand...
Click to collapse
Does anybody know a legit source for Odin? The links provided are down :-(