Develop Bugs

OTA Update Today for AT&T Note 2

Check for OTA Update in your settings.

Is it Lollipop?

I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.

Update the Software for the Samsung Galaxy Note II (i317)
Update summary
AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.
Software Update Includes
Android OS Enhancements
User-Initiated Software Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
Tap Software update.
Tap Check for updates, and then follow the subsequent prompts.
Verifying the Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
The following information displays:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Kernel version: 3.0.31-1728680 [email protected] #1 Wed Oct 1 22:38:36 KST 2014
Build number: KOT49H.I317UCUCNJ1
File size: 93.2MB

I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?

keplenk said:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
Click to expand...
Click to collapse
I wouldn't. I just posted this in the other thread about the OTA:
a042349 said:
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
Click to expand...
Click to collapse

same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?

kabinoff said:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
Click to expand...
Click to collapse
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

melvinaury said:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
actually flashed CF with Odin and it worked.

kabinoff said:
actually flashed CF with Odin and it worked.
Click to expand...
Click to collapse
Did it really work?

I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...

toshik1 said:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
Click to expand...
Click to collapse
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.

Zen Arcade said:
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Click to expand...
Click to collapse
Yes the SIM card has normal active service on it.

Other reasons OTA won't work:
1 - Location (if you are not in an area where OTA updates are provided, then...
)
2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)
3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)
As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.

DroidTuner said:
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Click to expand...
Click to collapse
Which process did you freeze?

I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5

toshik1 said:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
Click to expand...
Click to collapse
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). Approx. 93MB security and minor enhancement update.

Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.
I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.
It's now I317UCUCNJ1

[2016-10-07] New official Samsung 5.0 ROM N900TUVSFPH3 available on sammobile

N900TUVSFPH3 is now available on sammobile.
Model SM-N900T
Model name GALAXY Note3
Country USA (T-Mobile)
Version Android 5.0
Changelist 6005498
Build date Fri, 26 Aug 2016 12:38:40 +0000
Security Patch Level 2016-09-01
Product code TMB
PDA N900TUVSFPH3
CSC N900TTMBFPH3
Click to expand...
Click to collapse
Here's the changelog from t-mobile:
August/September Security Updates
Click to expand...
Click to collapse

At least they are providing security updates.
Sent from my SM-P600 using Tapatalk

Can you please share the baseband and modem?

The question is, will we be able to revert back to FOL1 after this update is flashed?

megaforcer said:
The question is, will we be able to revert back to FOL1 after this update is flashed?
Click to expand...
Click to collapse
I believe so.

I was pleasantly surprised yesterday when I saw the update notification. Nice to still see love for our Note 3.

I wanted to flash this using FlashFire and retain Root from FOL1. I made an attempt leaving the defaults checked (Boot, Recovery, System, Cache).
It completed successfully however, it caused my phone to no longer recognize the sim card. I simply re-flashed FOL1 with FlashFire and it was fixed.
I assume I need to maybe also check the protected partitions (Modem Firmware, Firmware, TrustZone, DBI/SDI). At least the Modem Firmware anyways....
Does anyone know if this (checking all, or one of the protected paritions) will trip Knox, or maybe require me to lose data? I have no reason to trip knox, so I'd like to avoid it if possible.
Thanks
--------
Edit: Went ahead and tried all the protected partitions. Checked every available flash option, besides the obvious disabled bootloader ones. Clicked "Yes" when it asked to do the protected partitions seperate, then proceeded to leave the rest stuff default. Flash was successful, root kept, knox 0x0.
Little note for people who may up doing this... I disabled xposed modules and uninstalled it before flashing the updated firmware.

billowusu47 said:
Can you please share the baseband and modem?
Click to expand...
Click to collapse
everything says FPH3 after flashing, weather or not there are any differences beyond the build number is above my capability of descernemnt
NSA updates?

Sideloading OTA vs flashing full factory image

I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?

There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.

Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.

savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...

5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?

sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...

sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...

5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.

savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...

5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.

sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...

sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/

alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...

alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.

Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/

savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...

PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.

shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.

PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.

OTA Updates???

I know when flashing, firmware updates can be 1Gb - 2Gb file sizes. When you take that same update OTA, do they send down the entire firmware file, or just the sections that need updating? This 910V is the first phone I have never rooted, and have never taken an OTA update. When I bought it, it was on 5.0. I downloaded the CQC1 firmware and installed it updating it to 6.0, via Odin. It tried to update itself immediately after I rebooted. I disabled the updater until I did some homework, as the thing was relentless about updating and driving me crazy. I see now there is CQD1, CQE1, and CQF2 available. My problem is, I have a crap internet connection (1.5Mb) and am wondering if it has to download that huge file anyway OTA, if I wouldnt be better downloading it myself and installing it via Odin.... rather than an OTA update that gives me no info on progress etc....?
So:
1) OTA or download and install it/them myself
2) If installing myself, Where is the best place to download the huge file, without having to sign up or be throttled?
3) Is there anything in these newer updates that warrant updating, or any problems that arise from them? Or is it wise to just stay on CQC1 which is working without a hitch?
Thanks for any help.

widowmaker17 said:
I know when flashing, firmware updates can be 1Gb - 2Gb file sizes. When you take that same update OTA, do they send down the entire firmware file, or just the sections that need updating? This 910V is the first phone I have never rooted, and have never taken an OTA update. When I bought it, it was on 5.0. I downloaded the CQC1 firmware and installed it updating it to 6.0, via Odin. It tried to update itself immediately after I rebooted. I disabled the updater until I did some homework, as the thing was relentless about updating and driving me crazy. I see now there is CQD1, CQE1, and CQF2 available. My problem is, I have a crap internet connection (1.5Mb) and am wondering if it has to download that huge file anyway OTA, if I wouldnt be better downloading it myself and installing it via Odin.... rather than an OTA update that gives me no info on progress etc....?
So:
1) OTA or download and install it/them myself
2) If installing myself, Where is the best place to download the huge file, without having to sign up or be throttled?
3) Is there anything in these newer updates that warrant updating, or any problems that arise from them? Or is it wise to just stay on CQC1 which is working without a hitch?
Thanks for any help.
Click to expand...
Click to collapse
Yeah the ota update is a smaller file. If you want, I just downloaded the CQI2 firmware and can upload it to AFH. I just did the 6 hr download and could save you some time.
The new update patches the bluborne vulnerability and from camparing the framework between this version and the last, there are a bunch of changes but Ive only had it installed for half a day so Im not real sure how much better or worse it is.

Thanks for the offer, much appreciated! But I went ahead and allowed the PTA update. I thought it would download the latest update and be done. Nope, it downloaded them 1 at a time in order. First CQD1, then CQE1, then CQF2, then CQI2. It took about an hour each total, but at least its updated

kevintm78 said:
Yeah the ota update is a smaller file. If you want, I just downloaded the CQI2 firmware and can upload it to AFH. I just did the 6 hr download and could save you some time.
The new update patches the bluborne vulnerability and from camparing the framework between this version and the last, there are a bunch of changes but Ive only had it installed for half a day so Im not real sure how much better or worse it is.
Click to expand...
Click to collapse
If you still have the file could you post it please.

macgyver40 said:
If you still have the file could you post it please.
Click to expand...
Click to collapse
Sure! Here you go. It's a completely unaltered firmware of CQI2. If your bootloader is unlocked, flashing this file will lock it back up and you'll be 100% stock.

B367 Update available for US variant (BLN-L24)

The security patch is updated to Jan. 1, 2018. "Integrates Google security patches for improved system security"

I still do not get it

jamesxantt said:
I still do not get it
Click to expand...
Click to collapse
Try the system update from the HiSuite. I didn't get it from the phone system update but the update became available in the HiSuite software (PC).

galapagos said:
Try the system update from the HiSuite. I didn't get it from the phone system update but the update became available in the HiSuite software (PC).
Click to expand...
Click to collapse
Thanks ?

I'm gonna take a big guess and say I'll lose root if I do this.
Edit: Can't update. Have TWRP. Don't have stock boot file for my US Honor 6X. No available links in the sticky forum either.

AidenSurvival said:
I'm gonna take a big guess and say I'll lose root if I do this.
Edit: Can't update. Have TWRP. Don't have stock boot file for my US Honor 6X. No available links in the sticky forum either.
Click to expand...
Click to collapse
These are the files needed for the update (B366 version):
https://mega.nz/#F!7clljDYQ!DjUTltO2GOHfBlHDndmCvQ
After the update, just flash TWRP and root again. None of your settings or apps/data will be affected (unless you've something that changes system files such as xposed framework - this can be resolved by reinstalling exposed zip)

galapagos said:
These are the files needed for the update (B366 version):
https://mega.nz/#F!7clljDYQ!DjUTltO2GOHfBlHDndmCvQ
After the update, just flash TWRP and root again. None of your settings or apps/data will be affected (unless you've something that changes system files such as xposed framework - this can be resolved by reinstalling exposed zip)
Click to expand...
Click to collapse
the update don't lock the bootloader?

Alex19Gam said:
the update don't lock the bootloader?
Click to expand...
Click to collapse
Nope, I never had to. If the update re-locks the bootloader, your data partition will be wiped. As said above, the update does not affect your data (as also noted by Huawei's update info which says "This update will not erase your personal data, but we recommend that you back up any important data before updating.").

Got it! But I saw B368 on Firmware Finder.
Sent from my HUAWEI BLN-L24 using XDA Labs

I got B367 on Saturday via notification. I'm the only one of three in the family thus far to get it, so it's definitely a slow roll out. I was super excited when I realized it also magically fixed my lagging camera-startup issue. :good:
That is, until today, when I realized I still had a massively lagging camera. Sigh...
Please tell me we'll soon get Oreo AND a camera fix.