Develop Bugs

1/16/17 update N920AUCS4CPL1 - - looks like another security update

I just got another monthly update for my AT&T Note 5 labeled N920AUCS4CPL1 with the December 1, 2016 security patch included. I can't find anything else on this update but again, it looks like another security update - - NOT Android 7.0+

@mattern1974, did you take a screenshot or something? What does the about device screen say?

itskapil said:
@mattern1974, did you take a screenshot or something? What does the about device screen say?
Click to expand...
Click to collapse
Here you go!

Second screen shot

mattern1974 said:
Second screen shot
Click to expand...
Click to collapse
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
Thanks man!

mattern1974 said:
Here you go!
Click to expand...
Click to collapse
How did you change your background

MusicHelps said:
How did you change your background
Click to expand...
Click to collapse
Themes in the settings.
Edit: I also use Nova Launcher since I like the speed and customization over the stock Touchjizz.

Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.

Wow---this update is KILLING my battery. Google play services is running in the background like crazy. I've lost 10% in 2 HRS with little use where as before the update I would have lost 10% by 2 PM---UGH! Anyone else having this problem?

I updated to PK1 the day I got my phone (last week Monday).
The battery life for me has been superb (since I flashed through ODIN and started setting it up from scratch).
I want to get PL1 (for peace of mind), but I don't have an AT&T SIM card, so I'm waiting for a complete file that I can flash through ODIN.

I don't want anymore updates because I'm almost out of equipment contract now and I want to hack my Note 5. I wasn't aggressive about this until recently but somehow I had auto update on. So my phone started the download but I rebooted it and stuck it in the microwave.. (panic style) Then I tried to downgrade to 5.11 using the PH4 and the PH2 firmwares in succession but PH4 soft bricked me. Then I tried flashing N920AUCS4CPK1. and I got success. Wiped it all back to November 2016 security patch. (I dunno if this works after it installs, I have a sinking feeling it will not work.. There is no firmware available with Dec 2016 security patch that I'm aware so no way to recover if I'm correct in assuming the bootloader is blocking me from downgrades)
Edit: I want stress that fact that my phone never said Dec 2016 security patch, during all this it was still Nov 2016 patch

droidvoider said:
if I'm correct in assuming the bootloader is blocking me from downgrades)
Click to expand...
Click to collapse
With AT&T bootloaders, I thought that was always the case.
You WILL take the update when Nougat arrives. I'm eager to know when that will be. I have no intention of rooting my device to trip Knox.

batuhur said:
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Click to expand...
Click to collapse
Here S4CPK1 - to- S4CPL1 -

norbarb said:
Here S4CPK1 - to- S4CPL1 -
Click to expand...
Click to collapse
Thank you very much
Updating now

I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.

norbarb said:
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
Click to expand...
Click to collapse
Why don't you try it and let us know?

mattern1974 said:
Why don't you try it and let us know?
Click to expand...
Click to collapse
I don't have Note 5

It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.

Anonymously_Unknown said:
My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
With a locked bootloader, it will probably stay unrooted. I don't know of a root for it, would be nice if there was one. I think 5.01 bootlaoder got unlocked... But I keep looking...

Anonymously_Unknown said:
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
Check the file to norbarb post, and send to your phone via ADB, you can search in google how can you send ota by adb, its easy. Send OTA via adb donesnt affect knox, its install manually OTA.

Uograde to B185 caused android pay to stop working?

Hi, has anyone had any issue with b185 and android pay?
I get a message saying that I may need to unroot my device but it's not rooted

charmz2k2 said:
Hi, has anyone had any issue with b185 and android pay?
I get a message saying that I may need to unroot my device but it's not rooted
Click to expand...
Click to collapse
Did u get it by OTA or manuell update? If it's​ not signed by Huawei yet it can cause problems with Android Pay.
Sent from my LON-L29 using XDA Labs

I updated through funky Huawei.
Did the same for 180 and that worked fine...

charmz2k2 said:
Hi, has anyone had any issue with b185 and android pay?
I get a message saying that I may need to unroot my device but it's not rooted
Click to expand...
Click to collapse
I think updating through FH is making your Android pay not working.The update is not signed ,maybe!!

I received the B185 update yesterday, I notice 2 things: the option Aggregate data has disappeared from the settings menu, and smart unlock when connected to a bluetooth device doesn't seem to work anymore

Sorry for reviving this thread, but check if Play Store is certified. Go to Play Store, hamburger menu, Settings, scroll down to bottom. I have had uncertified before and SafetyNet still passed. That's until I installed C432B193 for my Mate 9. It was uncertified and CTS Profile wouldn't pass. So I guess they started checking that too now.

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.

[New Firmware] 47.2.A.4.45 [G8441] (8 January 2018)

[New Firmware] 47.2.A.4.45 [G8441] (8 January 2018)

change log? security patch and kernel version have not change

Nope, nothing change. Only one general bug even on locked bootloader, google pay stop working, ctsprofile - false
Fixed by Sony, now gpay work.

russel5 said:
Nope, nothing change. Only one general bug even on locked bootloader, google pay stop working, ctsprofile - false
Fixed by Sony, now gpay work.
Click to expand...
Click to collapse
Is there a new update to fix this? can you share the version number? I get random reboots on 47.2.A.45 UBL, magisk and cts profile false.

Seems like it's still on December patch. Customised MY variant
Sent from my G8441 using Tapatalk

Finally out for customized DE. Is it okey to install? They took their time but I'm still worried

Evzzza said:
Finally out for customized DE. Is it okey to install? They took their time but I'm still worried
Click to expand...
Click to collapse
Just have done in - Disabled PIN, installed Customized DE, enabled PIN - everything seems to be normal, except Oreo is really nice

So I'm still on a DE Oreo rom with unlocked bootloader and magisk, but got the Ota prompt today to x.45..... Can I let it download and install rather than using flashtool?? I've never had it offer an update the official way before heh also now that there's twrp for Pie, is getting magisk back hard after updating to Pie?

OTA won't work with unlocked bootloader. Rooting with magisk is just as easy as always, just use the latest TWRP for xz1c pie.
If you want to keep your data, delete userdata*.sin from the downloaded firmware (and probably should also delete all .ta and persist*.sin if you still have your drm etc. keys) and flash with newflasher (flashtool might also work, I don't know).
Not sure if it will work without a factory reset, probably will, but maybe back up first...

Are you guys also having a slow response from Screen auto brightness? mine gets very dimm and takes, 3,4 seconds to go to a acceptable brightness...
anyone?

rsk_kelkar said:
Is there a new update to fix this? can you share the version number? I get random reboots on 47.2.A.45 UBL, magisk and cts profile false.
Click to expand...
Click to collapse
Was due to a rogue magisk module. All ok now

profyler said:
Are you guys also having a slow response from Screen auto brightness? mine gets very dimm and takes, 3,4 seconds to go to a acceptable brightness...
anyone?
Click to expand...
Click to collapse
Built-in auto brightness has always been ****, I use lux auto brightness, setup your lux values and link manually what light level readings you want the display to be at. You can have that set to auto brightness but I'd suggest setting it to on display wake, no constant polling.

I did update via OTA and no problems so far, but i have one bug, when i want delete a app it's not possible to do it via settings and apps (when i push the button "deinstall" than just nothing happens), i have to use a third-part app.
The auto brightness is a bit stupid, but i read that it have to learn for a while and than it will work better. So i will wait a bit and see if it works better in some days.

This update, whatever it is, always fails to install.
Now here's the catch: When I uninstall Magisk, I no longer am being offered the update! Anyone knows WTF is going on with that? :-O

WalrusInAnus said:
This update, whatever it is, always fails to install.
Now here's the catch: When I uninstall Magisk, I no longer am being offered the update! Anyone knows WTF is going on with that? :-O
Click to expand...
Click to collapse
OTA update does not work with an unlocked bootloader. Flash manually.

vofferz said:
OTA update does not work with an unlocked bootloader. Flash manually.
Click to expand...
Click to collapse
That is not true. All the smaller updates before downloaded and installed without any problems.

WalrusInAnus said:
That is not true. All the smaller updates before downloaded and installed without any problems.
Click to expand...
Click to collapse
Well, that's news for me. Everyone else has stated that OTA update fails with unlocked bootloader.

vofferz said:
OTA won't work with unlocked bootloader. Rooting with magisk is just as easy as always, just use the latest TWRP for xz1c pie.
If you want to keep your data, delete userdata*.sin from the downloaded firmware (and probably should also delete all .ta and persist*.sin if you still have your drm etc. keys) and flash with newflasher (flashtool might also work, I don't know).
Not sure if it will work without a factory reset, probably will, but maybe back up first...
Click to expand...
Click to collapse
And for those of us who do not have DRM-keys, which of those should I keep in?

bofis said:
And for those of us who do not have DRM-keys, which of those should I keep in?
Click to expand...
Click to collapse
Just delete those mentioned files before flashing. You should be fine too.
If you flash the persist sin file, you'll lose android attest key, but I don't think you anyway gain anything by flashing it, so just delete. Probably same with the .ta files - no gain, maybe something to lose. If you flash userdata you lose all your settings (&apps?) - it's like a factory reset.
Some people recommend a reset after a big update, but if you don't want to lose settings and apps, you should at least try if everything works fine.

call recording apps under this firmware update
Dean F said:
[New Firmware] 47.2.A.4.45 [G8441] (8 January 2018)
Click to expand...
Click to collapse
Hi Guys
There were some posts that call recording would not work anymore with Android Pie. Can someone confirm this statement /issue with Android Pie and specifically for this firmware upgrade?

Opps28.65-37-7-4

Does anyone have the latest security pacth update from February 1 2019 to download moto g5s?

I've download and installed successfully but the security path is still on feb 2019

And that the bootloader is unlocked and I can not block again because it is not the latest rom

keerthi perumal said:
I've download and installed successfully but the security path is still on feb 2019
Click to expand...
Click to collapse
Yeah, it doesn't do anything except apply so-called "security enhancements" :laugh:

My phone's actually rooted with bootloader unlocked, but I still got the notification for the update. Will it work?

JarlPenguin said:
Yeah, it doesn't do anything except apply so-called "security enhancements" :laugh:
Click to expand...
Click to collapse
Can't understand Moto these days

deivarchangel said:
My phone's actually rooted with bootloader unlocked, but I still got the notification for the update. Will it work?
Click to expand...
Click to collapse
i did it, same thing, bootoader unlocked and normal OTA update, working fine so far

I've got this too and still february patch. Weird releasing an update with no security patch, especially the current one is quite dated.

I updated mine too and it's normal, but I wanted to take it with me and I wanted to block the bootloader, and it's only possible with the latest rom