Database Info

Is it Safe to Take 4.4.3 OTA Update on Stock?

Hi, i'm kinda new to Rooting HTC Devices, but not to rooting android devices in general. I was wondering if it was safe to take the OTA Update to get the Latest Firmware / Radios Etc, and then Install Viper One 2.5.0. I haven't touched the Firmware at all and i heard from Team Venom that you had to update your firmware and so far i haven't found any RUU's that work properly and whenever i try to flash Viper One 2.4.0, i get VERY long boot screens and sometimes it hangs on the HTC Logo, like the post suggested. Is there any way of safely doing this to a Verizon Phone without loosing S-OFF, Root or an Unlocked Bootloader? Considering they said:
Notice: at the time of writing, both T-Mobile US and Verizon’s 4.4.3 Updates were not available yet, but announced.
Click to expand...
Click to collapse
which i think its not true since people are already running 4.4.3 and Viper One Running on the latest Firmware, and they also said
While the Verizon and T-Mobile US guys need to wait (with “method #1″), the TmoUS folks could head over to my thread (linked above) and set their phones to S-OFF and flash an international firmware as a shortcut (it should be ok, not sure on the impact, maybe losing some WiFi calling functionality which can be restored by flashing TmoUS Firmware once it becomes available), going by “method #2″. However, Verizon: do NOT flash an international GSM firmware! You would regret it badly! Same goes for Sprint by the way. No INT firmware for you ever!
Click to expand...
Click to collapse
Yet on the Verizon Post on Xda, they point you directly to it like i'm supposed to do that, and when i try "Method 2" which is also on their Website's Post that Links you to their Special Firmware Thread here , They Say:
I will cover GSM PHONES ONLY - no cdma / sprint firmware except when i wish to do otherwise.
Click to expand...
Click to collapse
which makes no sense considering they basically told me to go there from linking me in their Verizon Thread. I mean i'm totally confused how your supposed to flash the newest Firmware and it doesn't help that NO ONE has a tutorial online for this. I'm sorry if i'm coming off as a noob, but Normally Verizon OTA Updates have a tendency to Break Root and Lock the Bootloader and i don't know if this is any different.
My Device:
Verizon HTC One M8 (M8_WLV)
4.4.2, 1.55.605.2 Stock Sense
Rooted, S-OFF, Bootloader Unlocked

It's really easy to apply the radio and firmware. Just follow the instructions here
http://forum.xda-developers.com/showthread.php?t=2824882
Also you are correct that taking the ota directly will cause you to lose root. Once you have applied the firmware you should be good with the ROM

[Q] Accidentally took OTA update and SVTP tether doesnt work

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

S3 LTE issues (bootloader unlocked) Need new radio?

I have a Verizon Galaxy S3 that I've had for a couple years that I bootloader unlocked first thing when I first purchased it. The baseband says "NE1"
I am running a later release of Cyanogenmod 11 (official) with TWRP recovery and I may be having LTE issues; unsure if it is because of the area I am living or if it is my phone itself but I do run into a handful of LTE issues.
I figure my best solution is to install the latest radio that is compatible with my open bootloader firmware. I would love to stick with my open bootloader instead of flashing the latest firmwares and risk locking the bootloader.
I need to know where and which latest bootloader I should flash and which method to flash with. Someone that can point me in the right direction is greatly appreciated.
Thanks for reading.
EDIT: Could I also be running an old phone FIRMWARE? As far as I am aware, the only thing that I can update being that I am unlocked bootloader is my baseband/radio- is there anything else that I should check to update to flash via odin?

stevey500 said:
I have a Verizon Galaxy S3 that I've had for a couple years that I bootloader unlocked first thing when I first purchased it. The baseband says "NE1"
I am running a later release of Cyanogenmod 11 (official) with TWRP recovery and I may be having LTE issues; unsure if it is because of the area I am living or if it is my phone itself but I do run into a handful of LTE issues.
I figure my best solution is to install the latest radio that is compatible with my open bootloader firmware. I would love to stick with my open bootloader instead of flashing the latest firmwares and risk locking the bootloader.
I need to know where and which latest bootloader I should flash and which method to flash with. Someone that can point me in the right direction is greatly appreciated.
Thanks for reading.
EDIT: Could I also be running an old phone FIRMWARE? As far as I am aware, the only thing that I can update being that I am unlocked bootloader is my baseband/radio- is there anything else that I should check to update to flash via odin?
Click to expand...
Click to collapse
Post a screen shot of your about phone screen if you can
Edit: you can update to the newest modem, that should (don't quote me) fix your issue
Sent from my Nexus 5

Going to sell my S3 on swappa, but first, some questions.

Hey guys. It's been a while since I've poked around the S3 sub-forum. A year or so ago I picked up a pair of 2013 Moto X's for my wife and I to make my life a little easier. I had a note 2, she had the s3. Playing admin for two devices, and keeping up with their individual quirks was proving to take up too much of my time, so, we decided to stream line. I wouldn't say the Motos are better by any standard, but, making the switch has made my life easier.
Recently, we've decided to move. We started going through our drawers cleaning things out and found these devices and thought we should sell them. They're both bootloader unlocked, so, they can run the latest and greatest CM builds. The thing is though, I've pretty much forgot what I'm doing with them.
I don't want to odin the s3 back to stock. We got this device when it launched and as such the device has never gotten a official update and I prefer to keep it that way. I want to install a fresh, recent build of something and clean out any of our information that may be on the device before we sell it. Can anyone offer any advice on how to wipe on the s3 in this way? Any changes that I should be made aware of that's happened with the device in the last year or so? I was gonna flash the official CM12 build with gapps but if there's any other recommendations I'd love to hear them.
Thanks in advance.

If you obtained the SGS3 at launch and it has had no updates that would put you on the the 4.0.4 bootloader and modem. Checking the CM 12.1 thread for the i535 indicates you need the MF1 bootloader and the NE1 baseband (modem). MF1 was the second of two 4.3 bootloader released. The NE1 modem is from the 4.4.2 release.
Above all do not upgrade the bootloader past where you need it, the NE1 bootloader is locked very tight. IIRC the NC1, second 4.3 release, bootloader is not locked, but you can not downgrade bootloaders once it is installed. I don't recall the status of the first 4.3 bootloader, ML1. There is a link to the MF1 bootloader / NE1baseband combo flie in the OP of the CM 12.1 thread.
I haven't checked for the i535, I received mine used after it was on the NE1 bootloader, but for other US/Canadian SGS3 variants there is a viable free sim unlock for devices that are not beyond the 4.1.1 modem.

dawgdoc said:
If you obtained the SGS3 at launch and it has had no updates that would put you on the the 4.0.4 bootloader and modem. Checking the CM 12.1 thread for the i535 indicates you need the MF1 bootloader and the NE1 baseband (modem). MF1 was the second of two 4.3 bootloader released. The NE1 modem is from the 4.4.2 release.
Above all do not upgrade the bootloader past where you need it, the NE1 bootloader is locked very tight. IIRC the NC1, second 4.3 release, bootloader is not locked, but you can not downgrade bootloaders once it is installed. I don't recall the status of the first 4.3 bootloader, ML1. There is a link to the MF1 bootloader / NE1baseband combo flie in the OP of the CM 12.1 thread.
I haven't checked for the i535, I received mine used after it was on the NE1 bootloader, but for other US/Canadian SGS3 variants there is a viable free sim unlock for devices that are not beyond the 4.1.1 modem.
Click to expand...
Click to collapse
so 4.3 NC1 is unlockable?
Sent from my SCH-I535 using Tapatalk

nikkifm said:
so 4.3 NC1 is unlockable?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
No. Only root able
Nexus 6 via Pure Nexus

New Update - QH2

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.