Related
Changelog for the NI2 update being pushed today:
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy-s5-091614.pdf
Looks like we're getting ready for Advanced Calling 1.0 i.e. voice over LTE
jeff_roey said:
Changelog for the NI2 update being pushed today:
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy-s5-091614.pdf
Looks like we're getting ready for Advanced Calling 1.0 i.e. voice over LTE
Click to expand...
Click to collapse
My VOLTE is working fine on NHA. I noticed the support in the phone when this update was released a couple weeks ago. You need to log into your verizon account and activate the VOLTE feature. It will be working almost immediately after that. I tried a few video calls between my S5 and my wife's and they seem to work OK on my weak LTE signal at my house. You need to turn off wifi before it works too.
I plan to do a manual upgrade to NI2 today. (flash backwards and OTA to NI2 then re-root)
skiddingus said:
My VOLTE is working fine on NHA. I noticed the support in the phone when this update was released a couple weeks ago. You need to log into your verizon account and activate the VOLTE feature. It will be working almost immediately after that. I tried a few video calls between my S5 and my wife's and they seem to work OK on my weak LTE signal at my house. You need to turn off wifi before it works too.
I plan to do a manual upgrade to NI2 today. (flash backwards and OTA to NI2 then re-root)
Click to expand...
Click to collapse
Please let me know if you are able to successfully reroot after taking N12 upgrade
seanatsb said:
Please let me know if you are able to successfully reroot after taking N12 upgrade
Click to expand...
Click to collapse
Everything worked great. I'm rooted on NI2 with Xposed and Wanam. After updating OTA to NI2, just flash the original NCG kernel, root, then reflash the NI2 kernel.
Worked Great for me too. Confirmed rooted on NI2
Is it currently OTA only? What about those of us that aren't using Verizon, probably have to wait for a full flash?
I have the Verizon Developer Edition of this phone with it being rooted and having TWRP custom recovery. I tried a 4.4.4 (NI2) ROM on it, and my phone got stuck on the first screen during boot. I was able to restore from a backup through TWRP recovery to get back up and running, again. Hopefully, a working version of NI2 for the Developer Edition comes out soon because I want to enable VoLTE for my phone..
Hey guys, any idea where to get the NI2 kernel? Sorry I wasn't able to find it via a search.
http://forum.xda-developers.com/showthread.php?p=55495211
Seriously, It was in the next thread.
Thank you!
tap'n on my S5
Rooted G900v on NE9 OTA to N12?
Hey everyone,
Im new to rooting, so my fault for the dumb questions. Im. Currently on NE9, rooted with towelroot, Still on stock Android 4.4.2. Do I take the OTA to N12? Will it mess up my phone?, Ill just root it after I update, So Im not worried about losing Root.
Any advice would be much appreciated, Thanx!
Hey everyone,
Im new to rooting, so my fault for the dumb questions. Im. Currently on NE9, rooted with towelroot, Still on stock Android 4.4.2. Do I take the OTA to N12? Will it mess up my phone?, Ill just root it after I update, So Im not worried about losing Root.
Any advice would be much appreciated, Thanx!
Click to expand...
Click to collapse
Follow these install instructions in the OP. Youll be fine.
http://forum.xda-developers.com/showthread.php?p=55495211
I have a Verizon Samsung SM-G900V which I did run Towelroot on to root on the original.
Verizon pushed out the NE9 OTA which I accepted and it broke root. I haven't yet gotten around to following the directions to take it back to root.
My problem is they are trying to push out the NI2 update over the last few weeks to me and every time I try to apply it the phone errors out when trying to apply it. Of course no additional information as to why.
I haven't seen too many people having this particular issue so figured I would ask to see if I should go through and root again then apply the NI2 to the system through a different method than OTA, or if there is a particular file I should check to see what the reason it is failing might be.
Thanks for any advice.
Alex
When you were rooted before, did you freeze or uninstall any applications?
warpedmind0u812 said:
When you were rooted before, did you freeze or uninstall any applications?
Click to expand...
Click to collapse
No. I didn't that I remember specifically, but it is possible that I did freeze something and just don't remember.
When I start the phone it boots up then presents me with an error saying "Unfortunately, VZWAVSService has stopped." Otherwise everything seems to be fine.
I didn't have any problems applying the OTA for NE9 so found it odd that this one wouldn't push out correctly.
Alex
absamide said:
No. I didn't that I remember specifically, but it is possible that I did freeze something and just don't remember.
When I start the phone it boots up then presents me with an error saying "Unfortunately, VZWAVSService has stopped." Otherwise everything seems to be fine.
I didn't have any problems applying the OTA for NE9 so found it odd that this one wouldn't push out correctly.
Alex
Click to expand...
Click to collapse
Follow these install instructions in the OP. Youll be fine.
http://forum.xda-developers.com/showthread.php?p=55495211
warpedmind0u812 said:
Follow these install instructions in the OP. Youll be fine.
http://forum.xda-developers.com/showthread.php?p=55495211
Click to expand...
Click to collapse
Hmm. Ok, thanks. I don't do Windows, but I think Heimdal will do what I need as well. I will try that out.
Alex.
absamide said:
Hmm. Ok, thanks. I don't do Windows, but I think Heimdal will do what I need as well. I will try that out.
Alex.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55569056
absamide said:
Hmm. Ok, thanks. I don't do Windows, but I think Heimdal will do what I need as well. I will try that out.
Alex.
Click to expand...
Click to collapse
Heimdall might work with the smaller kernel files but honestly I haven't tried it yet. Give Jodin a try, you can run it from the website or off your computer. Jodin uses heimdall so it won't work with large tar files but should be ok with the smaller ones. Here is the NCG PIT file you will need also. Don't worry it is the same pit for all the versions so far.
Echo_Platoon said:
I have the Verizon Developer Edition of this phone with it being rooted and having TWRP custom recovery. I tried a 4.4.4 (NI2) ROM on it, and my phone got stuck on the first screen during boot. I was able to restore from a backup through TWRP recovery to get back up and running, again. Hopefully, a working version of NI2 for the Developer Edition comes out soon because I want to enable VoLTE for my phone..
Click to expand...
Click to collapse
You're extremely lucky you did not lock your bootloader. I understand a rooted phone with a custom recovery will normally prevent an OTA update from successfully installing. But, to be on the safe side, I would NEVER allow an OTA update to be installed on my Developer Edition phone. Just a suggestion...if you have a Developer Edition S5 do not take an OTA or ODIN/Flash a retail firmware. If you do, your bootloader will get locked and you'll be left with a very expensive retail version of the S5.
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?
Hi! I'm new here... Hope I'm in the right place, but I've been having problems with my GS5. I rooted it using towelroot about 3 months ago which was successful, then a Verizon system software update was pushed and installed to my phone, and that somehow installed fine, but now root checker says my phone isn't rooted and towelroot says my phone isn't supported... For months now my phone has been trying to install the 4.4.4 update with no luck, when it reboots and is in the middle of installing with the little android dude with his chest open, it says 'error'. Has there been a fix or way around this? Any way I can completely factory wipe everything?
rswans said:
Hi! I'm new here... Hope I'm in the right place, but I've been having problems with my GS5. I rooted it using towelroot about 3 months ago which was successful, then a Verizon system software update was pushed and installed to my phone, and that somehow installed fine, but now root checker says my phone isn't rooted and towelroot says my phone isn't supported... For months now my phone has been trying to install the 4.4.4 update with no luck, when it reboots and is in the middle of installing with the little android dude with his chest open, it says 'error'. Has there been a fix or way around this? Any way I can completely factory wipe everything?
Click to expand...
Click to collapse
Verizon may of patched the towelroot exploit with the new update. Have you tried posting this in the VZW S5 forums?
From my CM11 S3
Towel root is dead for firmwares newer than June 2014. You can try chainfire for root. If t he 4.4.4 firmware isn't updating, try flashing with Odin.
chaostic_2k1 said:
Towel root is dead for firmwares newer than June 2014. You can try chainfire for root. If t he 4.4.4 firmware isn't updating, try flashing with Odin.
Click to expand...
Click to collapse
Thanks for chiming in but I basically said that already. There's no need to duplicate it. You won't be able to run supersu for root as you can't flash any zip files on a locked bootloader
From my CM11 S3
Thanks for replying but I basically gave OP actual useful answers to his direct question.
chaostic_2k1 said:
Thanks for replying but I basically gave OP actual useful answers to his direct question.
Click to expand...
Click to collapse
As did I
From my CM11 S3
ShapesBlue said:
As did I
From my CM11 S3
Click to expand...
Click to collapse
Sure you did
chaostic_2k1 said:
Sure you did
Click to expand...
Click to collapse
I explained a different perspective and I didn't question what you said. Let's just leave it at that
From my CM11 S3
rswans said:
Hi! I'm new here... Hope I'm in the right place, but I've been having problems with my GS5. I rooted it using towelroot about 3 months ago which was successful, then a Verizon system software update was pushed and installed to my phone, and that somehow installed fine, but now root checker says my phone isn't rooted and towelroot says my phone isn't supported... For months now my phone has been trying to install the 4.4.4 update with no luck, when it reboots and is in the middle of installing with the little android dude with his chest open, it says 'error'. Has there been a fix or way around this? Any way I can completely factory wipe everything?
Click to expand...
Click to collapse
Its too bad there is not a way to block any updates.. These companies want to control all we see and do on our devices. I have made the decision to dump my smart phone.I am going to get a flip phone and only use for phone calls.
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
cell2011 said:
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
Click to expand...
Click to collapse
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Pretoriano80 said:
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Click to expand...
Click to collapse
Great ty what if phone was rooted would that stop OTA`s? Just curious im not rooted. Is the OTA suppose to be released with Gapps included do you know? There are an awful lot of people not being able to recieve gapps the right way. I hear location doesnt work and some other stuff but maybe thats a handful of people
I don't think the root prevent a device receiving the OTA,but it might cause the OTA installation to fail,so it's always best to disable root before updating.
I didn't used the OTA to update my device,so I can't say if there's any issue with it,but I know people that updated via OTA and it was all fine.
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
The Joke(r) said:
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
Click to expand...
Click to collapse
That seems to be a major bug there are so many talking about location not working or its in another place in settings. Not sure where cause i dont have my phone right now. Im sure there will be a workaround soon
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
You won't be able to update while rooted. Actually updating with a factory image is probably safer than taking an ota update. Personally, I think the update is worth it.
Sent from my SM-T530NU using XDA-Developers mobile app
hexr96 said:
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
Click to expand...
Click to collapse
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
acejavelin said:
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
Click to expand...
Click to collapse
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Tel864 said:
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps stability is not the real argument here... both are stable, as are most production ROMs, I have been using Marshmallow since early December and never had any real problems. But there are pros and cons to both and depending on your situation one may be better than the other, but I guess that wasn't really the point of this thread so I will say I half agree with your statement.
I would also have to relock the bootloader, correct?
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
No
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
Nope, in fact, you can't relock the bootloader even if you want to. The bootloader lock state is not relevant to taking an OTA.
Thank you everyone