Database Info

[Q] How do OTA updates affect root users?

Hello,
How does the upcoming OTA update (4.3) affect people with unlocked bootloaders and custom ROMs? I am new to this and this will be my first OTA update since rooting/unlocking.
Will I even get a notification requesting to update, or will it force me to update? And which should I choose? Will I have to re-root the phone after the update? Or can I even get the OTA update since it is rooted?
Sorry, I have a ton of questions, so if someone can just explain what is going to happen and what our choices are that would be great!
Thanks in advance!!!
-Joe

I'll try to answer a few
...
It seems like the ota is delayed but who knows..
If you want to stay unlocked and rooted don't take the ota until a respected developer says otherwise.
You may or may not get a notification depending on your ROM or other system tweaks. If you are rooted only, you provably will.
Sent from my SCH-I535 using XDA Premium 4 mobile app

joejaniczek said:
Hello,
How does the upcoming OTA update (4.3) affect people with unlocked bootloaders and custom ROMs? I am new to this and this will be my first OTA update since rooting/unlocking.
Will I even get a notification requesting to update, or will it force me to update? And which should I choose? Will I have to re-root the phone after the update? Or can I even get the OTA update since it is rooted?
Sorry, I have a ton of questions, so if someone can just explain what is going to happen and what our choices are that would be great!
Thanks in advance!!!
-Joe
Click to expand...
Click to collapse
The OTA will note affect you at all, you will not even be prompted for it due to running a custom ROM.
If your running a stock rom and have only rooted/unlocked, an OTA will break root and relock your bootloader.
If your running a stock rom/unlocked/and a custom recovery, you'll get prompted for the OTA, but it will not install, it will fail due to the custom recovery (twrp/cwm/etc).
You'll need to Odin to stock to receive an official OTA, but remember there is always a risk of an OTA breaking root permanently....
My advice is to stay custom, and flash a rooted custom stock rom that will surely be appearing here within a day or two of the OTA... But Verizon will probably not release 4.3 to us, and if they do it'll be at least 4 months...

Is Unlocking the Bootloader prevent automatic OTA updates?

Greetings,
Just bought a brand new (directly from Google) Nexus 5. It came with 4.4.3 and immediately notified about an "update available", in which it downloaded and installed 4.4.4.
I then went on and Unlocked my bootloader in preparation for a root (I did not root yet, full stock). But I am not getting any update for Lollipop, not even when I manually Check for Updates.
Are these OTA updates come/pushed randomly, or did the Unlocking of the bootloader prevented an automatic OTA update?
I am aware of the option to manually update, I am just curious if the Unlocking prevents updates. If so, if I re-lock the bootloader again will I then get the OTA update?
Thanks.

No, it doesn't change anything. OTA updates are staged so you just probably haven't had it yet...

Unlocking does not affect OTA. But keep in mind you'll likely have to re-root if you get auto updated.

Thank you both!
Am I correct to assume that Rooting also will not prevent OTA updates?

sbi1 said:
Thank you both!
Am I correct to assume that Rooting also will not prevent OTA updates?
Click to expand...
Click to collapse
It won't prevent getting the ota but it will prevent it from installing
Sent from my Nexus 9 using XDA Free mobile app

Gota. So either:
Stock+Root and no updates
Stock+No-Root
Or Root+Custom
?!

sbi1 said:
Gota. So either:
Stock+Root and no updates
Stock+No-Root
Or Root+Custom
?!
Click to expand...
Click to collapse
In order for the ota to install you have to be 100% stock system, kernel, recovery, and radio. If you've modified any of those you'll have to return them to stock before the ota will install. There are ways to do that but it depends on the specifics of any modifications you've done to the device. Frankly, it's easier to just flash the new factory image than it is to take the ota if you've modified your device.
Edit, to the best of my knowledge modifying your device, short of deleting our freezing some system files specifically related to receiving updates, will not prevent you from getting the ota, just installing it.
Sent from my Nexus 9 using XDA Free mobile app

OK, so just to make sure I understand: Is Unlocking the Bootloader making my system not 100% stock? Which means, even if the update downloads it will not install?
Also - again, if I understand correctly - based on what you say I can root, I will receive the update OTA but it won't install. Is this correct?

sbi1 said:
OK, so just to make sure I understand: Is Unlocking the Bootloader making my system not 100% stock? Which means, even if the update downloads it will not install?
Also - again, if I understand correctly - based on what you say I can root, I will receive the update OTA but it won't install. Is this correct?
Click to expand...
Click to collapse
If you just unlock the bootloader you should have no trouble installing the ota. You'll have to unroot to install the ota. You can use the full unroot option in supersu
Sent from my Nexus 9 using XDA Free mobile app

Moto G LTE XT1045 updated to Lollipop rolled back to Kitkat

Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7

electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
Hi.
In my xt1040, i can flash CM 12 lollipop or a stock rom based from kitkat 4.4.4 without problems (I have a updated bootloader), to get OTA updates again, its necessary flash the stock rom (KK or LP), without root, PURE stock (with all "bloatware").
Now im using a optimized rom from:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
No bugs, amazing battery life, and a pure stock, no "bloatware", great ram management.
Sorry for bad english.

electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
You'll have to wipe the system anyway, updating it will be a waste of time...

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.

Reasons to upgrade to 10.3.3? Rooted and on 9.0.9.

Hi, except for security patches, what would be the reasons to upgrade to 10.3.3 from 9.0.9?
Not experiencing any issues.
I'm not sure I want to go through the hassle of upgrading.
I'm rooted with unlocked bootloader, running magisk.
Thanks! / Jonis

JonisB said:
Hi, except for security patches, what would be the reasons to upgrade to 10.3.3 from 9.0.9?
Not experiencing any issues.
I'm not sure I want to go through the hassle of upgrading.
I'm rooted with unlocked bootloader, running magisk.
Thanks! / Jonis
Click to expand...
Click to collapse
Dark mode, better gesture navigation, randomized MAC, improved location permissions. There's not much hassle in upgrading, too. You can just download the zip, local upgrade, and it would install in the background. If you want root, you can just re-root after updating since your bootloader will stay unlocked. Besides, we would surely get Android 11 by next year, and I don't think you'd want to be left behind by 2 updates when that comes.

Thanks. ?