Database Develop

HTC One - Couldn't Install on USB Storage or SD Card

Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.

Make a nandroid and flash another rom to see if that fixes it.

You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse

Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:

You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.

BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?

Yes. You can put TWRP back on after the OTA is on.

BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.

roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?

DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

Rog Phone 2 unable to update.

Hello, and thank you for this community.
I have a Rog Phone 2, tencent version with Rom and Fingerprint WW.
I am just asking what I should do to Fota update or manual update my phone. I downloaded tons of versions and I am receiving only Failed to update error. I will post a screenshots with info.
Thank you in advance for help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ToCsiQuE said:
Hello, and thank you for this community.
I have a Rog Phone 2, tencent version with Rom and Fingerprint WW.
I am just asking what I should do to Fota update or manual update my phone. I downloaded tons of versions and I am receiving only Failed to update error. I will post a screenshots with info.
Thank you in advance for help.
Click to expand...
Click to collapse
What rom version are you on now?

reg66 said:
What rom version are you on now?
Click to expand...
Click to collapse
ROM WW_Phone-user 9 PKQ1.190414.001 16.0622.1907.33-0 release-keys
Fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1907.33-0:user/release-keys

ToCsiQuE said:
ROM WW_Phone-user 9 PKQ1.190414.001 16.0622.1907.33-0 release-keys
Fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1907.33-0:user/release-keys
Click to expand...
Click to collapse
OK. You're still on android 9. For some reason, some people have had success updating by skipping versions using the full zip firmware, whereas others have had to do each incremental update in order to get to the latest.
1st try downloading the full zip for the last A9 update 1910.64 and place it in root of internal storage. Reboot, when prompted click to update.
Are you rooted? If so and you want to keep root, don't click restart after update is complete. Instead, choose 'later' and go to magisk manager. Click to install magisk and select 'after ota', then reboot once finished. Ignore this though if you are not rooted.
From 1910.64, download the full zip of latest A10, which is currently 2007.27 (full zip of 2007.97 is not yet available). Repeat the process to install the zip as with .64
If this doesn't work, you'll need to update each small incremental update in order if release and keep going until you're up to date

Thank you for your fast answer. I will come back with the results.

reg66 said:
OK. You're still on android 9. For some reason, some people have had success updating by skipping versions using the full zip firmware, whereas others have had to do each incremental update in order to get to the latest.
1st try downloading the full zip for the last A9 update 1910.64 and place it in root of internal storage. Reboot, when prompted click to update.
Are you rooted? If so and you want to keep root, don't click restart after update is complete. Instead, choose 'later' and go to magisk manager. Click to install magisk and select 'after ota', then reboot once finished. Ignore this though if you are not rooted.
From 1910.64, download the full zip of latest A10, which is currently 2007.27 (full zip of 2007.97 is not yet available). Repeat the process to install the zip as with .64
If this doesn't work, you'll need to update each small incremental update in order if release and keep going until you're up to date
Click to expand...
Click to collapse
1910.64 started and updating. I will post news.
Thank you! You are awesome! :good::good:

ToCsiQuE said:
1910.64 started and updating. I will post news.
Thank you! You are awesome! :good::good:
Click to expand...
Click to collapse
Full update zip is now available for latest A10
https://androidfilehost.com/?fid=8889791610682948538
If you are a heavy gamer, I'm not sure about latest build but many users prefer last android 9 version (.64) for gaming. Up to you.
If you go for latest A10, just download from above link and repeat process

reg66 said:
OK. You're still on android 9. For some reason, some people have had success updating by skipping versions using the full zip firmware, whereas others have had to do each incremental update in order to get to the latest.
1st try downloading the full zip for the last A9 update 1910.64 and place it in root of internal storage. Reboot, when prompted click to update.
Are you rooted? If so and you want to keep root, don't click restart after update is complete. Instead, choose 'later' and go to magisk manager. Click to install magisk and select 'after ota', then reboot once finished. Ignore this though if you are not rooted.
From 1910.64, download the full zip of latest A10, which is currently 2007.27 (full zip of 2007.97 is not yet available). Repeat the process to install the zip as with .64
If this doesn't work, you'll need to update each small incremental update in order if release and keep going until you're up to date
Click to expand...
Click to collapse
you are absolutely right, it works very well.
You have to go through the latest version of android 9

I updated my rog phone2 to Android 10 from within the Asus site. After the update, it restarts many times. The phone is a tencent games version, and ww. The previous Android version was 9 (.19) which had no problems. Please help me.thank you

Mahdi shokati said:
I updated my rog phone2 to Android 10 from within the Asus site. After the update, it restarts many times. The phone is a tencent games version, and ww. The previous Android version was 9 (.19) which had no problems. Please help me.thank you
Click to expand...
Click to collapse
Are you saying the phone doesn't boot to android at all, just keeps re booting correct? You need to boot into fastboot mode (from power off state, hold vol up and power buttons together until you reach a menu) then you need to flash raw firmware, preferably for the current rom/firmware that you are on.

No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing
---------- Post added at 10:49 AM ---------- Previous post was at 10:41 AM ----------
No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing
---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------
No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing

Mahdi shokati said:
No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing
---------- Post added at 10:49 AM ---------- Previous post was at 10:41 AM ----------
No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing
---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------
No, the phone will boot, but while working, it suddenly freezes many times and restarts, especially when playing
Click to expand...
Click to collapse
If your bootloader is unlocked you could flash twrp /magisk and backup all apps + data etc. I use swift backup but you need to be rooted for app data, WiFi, etc etc.
But yeah, sounds like you might need to factory reset and start a fresh. If you wanted to downgrade to last A9 there's a downgrade zip on asus website but it will also wipe data

Did anyone else get an Android 12 update notification...on Android 12?

This popped up today and has me completely baffled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yeah i got the notification nearly the same time.
u already updated it?

Loisel said:
yeah i got the notification nearly the same time.
u already updated it?
Click to expand...
Click to collapse
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015

V0latyle said:
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015
Click to expand...
Click to collapse
I will update right now from android 11.

Loisel said:
I will update right now from android 11.
Click to expand...
Click to collapse
If you intend on rooting, I'd wait a second....

Yes I got it as well

Maybe they're rolling out an update for Pixel-only-features like they did with the Pixel 6 series.
Until now I didn't get it even with manual search.

Well...I did a clean factory install yesterday, and I don't see an update anymore. It's not posted on the Google firmware pages either, but then again, neither is the new Pixel 6 OTA.
Still see an update available for download but not sure I want to try it quite yet.

Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.

V0latyle said:
Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.
Click to expand...
Click to collapse
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.

ProjectAlly said:
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.
Click to expand...
Click to collapse
Same

So I just wiped, re flashed with the flash tool, patched my boot image and everything is running fine again.
I will advise though! For now do NOT update Magisk! Stick with v23000 for now!
The newest release will take some effort to figure out, as far as getting V4A running and other modules since the repo has been removed from the app now. Stay on the older version for now, it will save you a headache.
I updated Magisk and regret it now.

I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.

chrizzle30 said:
I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.
Click to expand...
Click to collapse
Same here .. went everything well for you after installing the update again?

ulxerker said:
Same here .. went everything well for you after installing the update again?
Click to expand...
Click to collapse
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Same here. Before, the build number was SP1A.211105.003 but that's how it's supposed to be according to other reports.

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Since I installed Android 12 the day of the Pixel 6 announcement, I will guess that I was on build number SP1A.210812.015, Oct 2021. This is very interesting because on the Android OTA site, the build that just installed says that this is the Verizon image. I am on Google Fi and I purchased my Pixel 5 from the Google Store.

Today I got an update of Google Play System Update (?) and after that, no more system update available on notification bar or system settings!

General June update finally :)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So? Did it finish? It's your Pixel "better" now?

I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.

gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher. Download the files here:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
And use PF...
Releases · badabing2005/PixelFlasher
Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.
github.com
No waiting for hours on the OTA, all work on PC, only dl time for the big files.

justDave said:
So? Did it finish? It's your Pixel "better" now?
Click to expand...
Click to collapse
Lol, I never see a difference

t-ryder said:
Forget about real OTA. Install full OTA files or factory images (if rooted or not) via Pixel Flasher.
Click to expand...
Click to collapse
Pixel Flasher only works with unlocked bootloaders though.

justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
You can sideload the Full OTA with a locked bootloader with Pixel Flasher.

justDave said:
Pixel Flasher only works with unlocked bootloaders though.
Click to expand...
Click to collapse
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...

ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
IDK, but last time I offered a handful of Pixel owners a workaround that needed root (or at least an unlocked bootloader), I got no takers.

ldeveraux said:
Why buy a Pixel if you're not going to unlock the bootloader? They practically beg you to do it...
Click to expand...
Click to collapse
Couldn't agree more. The ease of unlocking, flashing, rooting etc without warranty implications is my favorite Pixel feature.

gerhard_wa said:
I have never had a phone that takes this long to download, install and optimize a monthly update! This was a “feature” update, but the previous one also took around two hours. And this was over 500 mbps wifi.
Is this the price to pay for having done away with the cache partition and the download and patch is made directly to the working partition? Or did it take the same ridiculously long time with Pixel phones when a cache partition was in use?
As you probably can tell I am new to Pixels and in awe over the slowly moving scale. As I bought the P7 in the end of April I was certain the phone had crashed and frozen during update, but I forced myself to leave the phone alone and was really surprised when it at last was ready!
A real warning would not have been in the way instead of the lacklustre message that the update could take some time.
Click to expand...
Click to collapse
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher

simplepinoi177 said:
Stock System Update = 2 hours
Downloading OTA image file and manually flashing (PixelFlasher or sideload in Recovery Mode) = less than 20 minutes
Hell...with an unlocked bootloader, the non-OTA Full Factory image takes less than 20 minutes when manually flashing in CMD
Stock System Update < sideloading/PixelFlasher
Click to expand...
Click to collapse
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.

Does this update fix the AVRCP issues with this phone's bluetooth?

t-ryder said:
I updated the factory image for June on my Pixel 7 in 134 seconds using Pixel Flasher. Full device backup (apps/app data/data), using Pixel Flasher to update and re-root, flashing custom kernel in FKM... on my Ryzen 3900X machine with M.2 SSDs it's all together like 15 min. for me. Since having the Pixel 7 I tested real OTA like once, and it took hours. Bananas.
Click to expand...
Click to collapse
exactly...
honestly...most of that "under 20 minutes" stuff is downloading the 2.6GB image, extracting it, copying it over to the platform-tools folder....
and that's me doing everything manually; i've never used PixelFlasher, but I imagine badabing2003 streamlined it so the GUI/program just points to the image files than needing it to be in the same folder....
Before I convinced my wife to allow me to root her P7P, I did the real OTA once with it and it was nails on a chalkboard as I was manually flashing my rooted P7P -- again, not that one needs a rooted device to sideload an OTA; which is still considerably faster than using the stock System Update...

Still haven't received the OTA update.
Pixel 7, purchased from Google, on AT&T.

this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?

Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?

justDave said:
Did you install the latest OTA over GrapheneOS? Was that a GrapheneOS OTA or the Google OTA the rest of us are talking about?
Click to expand...
Click to collapse
It was GrapheneOS OTA of course =) , but update content is the same (QT3A)

Albirew said:
this latest OTA made my phone bootloop if i re-add magisk...
Is it just on GrapheneOS or flashing Magisk on latest stock makes bootloop too?
Click to expand...
Click to collapse
Magisk works fine on June stock update.

Lughnasadh said:
Magisk works fine on June stock update.
Click to expand...
Click to collapse
Thanks.
Since it's a GrapheneOS specific issue, I started my own thread.