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.

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.

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.

Android 9 Pie update

Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?

Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.

Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)

EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045

prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level

prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?

Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.

Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way

prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?

Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool

Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?

Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.

Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/

I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.

Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?

neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.

Question ANDROID 13 IS HERE! WW-33.0610.2810.72

Just checked Asus website of Rog6 support. I'll be downloading it but before I have to back up my data, in case anything goes wrong. Anyone already on 13?

fux1976 said:
Just checked Asus website of Rog6 support. I'll be downloading it but before I have to back up my data, in case anything goes wrong. Anyone already on 13?
Click to expand...
Click to collapse
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13

mind if you share how you downgraded your phone to .197?
Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse

I also updated to Android 13 Version: 33.0610.2810.72.

Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse
To be honest with Rog2 was much easier. I can't figure out what's the problem with Android Auto (crashes) but voice typing started working magically on its own. Never had problems with hardware luckily.
Today I'll upgrade and let you know the result. Fingers crossed!

amit.akm said:
I also updated to Android 13 Version: 33.0610.2810.72.
Click to expand...
Click to collapse
Is everything working fine? Did you update on top or factory reset?

Redlith said:
mind if you share how you downgraded your phone to .197?
Click to expand...
Click to collapse
You need to flash raw firmware via fastboot

Thanos88 said:
You need to flash raw firmware
Click to expand...
Click to collapse
did the bootloader unlocked and be able to receive firmware update?

Redlith said:
did the bootloader unlocked and be able to receive firmware update?
Click to expand...
Click to collapse
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flash

Thanos88 said:
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flle
Click to expand...
Click to collapse
any new features you've noticed?
i mean, does flashing raw file unlocked the bootloader?

Redlith said:
any new features you've noticed?
i mean, does flashing raw file unlocked the bootloader?
Click to expand...
Click to collapse
Just some UI changes, nothing visually changed but phone feels more snappy & Overall much better. All the bugs I had on .197 have been fixed. It's a excellent update.
No it doesn't unlock bootloader

Thanos88 said:
Just some UI changes, nothing visually changed but phone feels more snappy & Overall much better. All the bugs I had on .197 have been fixed. It's a excellent update.
No it doesn't unlock bootloader
Click to expand...
Click to collapse
Just updated: wow! It seems like a new phone! Snappier, visual and settings improvement. Updated on top, no factory reset. For one time it went flawlessly. I applied Magisk before rebooting ("after OTA"). Perfect!

Thanos88 said:
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flash
Click to expand...
Click to collapse
Thanks for providing your feedback, I'll update in a bit...

Pete450 said:
Thanks for providing your feedback, I'll update tonight.
Click to expand...
Click to collapse
Sorry for double-posting, but just following up - I updated from WW-32.2810.2210.220 (skipping WW-32.2810.2212.241) to WW-33.0610.2810.72, and can confirm it to be working without data wipe.
Also, it resolved the sound issue, where after placing/receiving a call, the bottom speaker would be much louder than the top speaker during any media audio.

Hello
I have a rog 6d ultimate i just download Android 13 update from asus
UL-ASUS_AI2203-ASUS-33.0404.1203.63-1.1.1-2301-user.zip
I put it on root restart my phone ,update showed up but fail to update.what should i do ?!
My phon not rooted but bootloader is unlocked is that matter ?!
My phone is ww

havard20009 said:
Hello
I have a rog 6d ultimate i just download Android 13 update from asus
UL-ASUS_AI2203-ASUS-33.0404.1203.63-1.1.1-2301-user.zip
I put it on root restart my phone ,update showed up but fail to update.what should i do ?!
My phon not rooted but bootloader is unlocked is that matter ?!
My phone is ww
Click to expand...
Click to collapse
Possibly bootlader, not sure. My bootloader has always been locked

Thanos88 said:
Possibly bootlader, not sure. My bootloader has always been locked
Click to expand...
Click to collapse
What should i do ?!
Can i lock it again?!
After update can i unlock it again ?!
How about update raw file ?!

havard20009 said:
What should i do ?!
Can i lock it again?!
After update can i unlock it again ?!
How about update raw file ?!
Click to expand...
Click to collapse
You should lock it and try the update again. I don't know if you can unlock it after updating, haven't tried myself

hi every one i need help about update to a13 wthout ota and how to creat backup
and how to check if bootloader are locked or no

Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse
Hey bro, I just bought a ROG 6, I'm gonna manually update the phone, my cuestion is, wich firmware version is the best? (Already on 134) I don´t mind if isn't the lastest version, I just want to know wich is the most stable/recommendable version, you said the 197 is a stable one, I think the 241 should work great because is the last android 12 update, can you confirm? Do you recomend the lastest android 13 version? (WW-33.0610.2810.81) Or, in your experience wich is the most recommendable one?
Sorry for so many cuestions
Thanks