Database Develop

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

Kernel Patch for Android Pay (LineageOS)?

I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck

Please try this patch
https://review.lineageos.org/#/c/152083/

josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?

The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"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"
}
Sent from my MI 5 using Tapatalk

p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.

AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.

AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk

So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...

You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk

p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.

I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk

AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...

AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.

Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:

Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk

I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.

AT&T 4G/LTE not working after flashing stock boot.img

Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!

tiduscrying said:
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
Click to expand...
Click to collapse
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.

mrmazak said:
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
Click to expand...
Click to collapse
My phone came out of the box with version 6.1, so i was able to flash the modified stock update from here that updates the phone from 6.1 all the way to 7.4.2. I took the boot.img from the vanilla 6.1 prime update and flashed it, so that is probably what the issue is. I assume the next step would be to flash the boot.img from the 7.4.2 version, but I can't seem to find a normal version of the v.7.4.2 update that I can just take the boot.img from (unless I can take it from one of these flashable zips?). If it helps, here is a screenshot of my system info which has all the version numbers and whatnot.
{
"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"
}
EDIT: Okay, so I flashed the boot.img from a slightly modified zip of the 7.4.2 update (from here) and thankfully, everything is working fine now. 4G LTE is working swimmingly and I feel like a moron. Lesson learned. Kids, make your backups!

Well, now here is another weird issue. The 4G LTE data is working perfectly fine and speedy as ever, but MMS messages are not being received or sent for whatever reason now. I've already manually entered the correct APN settings and reset them as well to no avail. Any suggestions on this? I've also tried some other SMS apps (such as Pulse) and cleared Messenger's cache and data settings, but that all seems like it did nothing.
Edit: Well, I just flashed the modified 7.4.2 rom that's from the Rom's section of the Blu R1 HD board and MMS is working again. Looks like something other than the boot.img was messed up or something. I did a dirty flash so luckily my roms are in tact.
Edit 2: Sigh, I have no idea what's happening. MMS keeps getting screwey whenever I even start playing around with Xposed (more specifically, Gravity Box). I have no idea why this is happening now all of the sudden. A few days ago before I messed with Magisk, Gravity Box wasn't messing with my MMS messages (at least... I don't think it was...).

Question Fleeting chance to update to MIUI13 - what happened?

Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
Why you didn't search for this file:
miui_SWEETGlobal_V13.0.4.0.SKFMIXM_4e557a2f1f_12.0.zip
and clean flash it via orange fox?
Or search for the same fastboot file and flash it via miflash?

Laptapper said:
Why you didn't search for this file:
miui_SWEETGlobal_V13.0.4.0.SKFMIXM_4e557a2f1f_12.0.zip
and clean flash it via orange fox?
Or search for the same fastboot file and flash it via miflash?
Click to expand...
Click to collapse
That will be my next step - normally I would just flash a ROM of my choosing.
Mainly I didn't want to lose all my data and settings. For example, the scanning app I use for my Invisalign requires the dentist to generate a new registration code if I reinstall or get a new phone.

serapax said:
That will be my next step - normally I would just flash a ROM of my choosing.
Mainly I didn't want to lose all my data and settings. For example, the scanning app I use for my Invisalign requires the dentist to generate a new registration code if I reinstall or get a new phone.
Click to expand...
Click to collapse
Backup all customs APK with alpha backup pro and later restore them with all settings....

Laptapper said:
Backup all customs APK with alpha backup pro and later restore them with all settings....
Click to expand...
Click to collapse
Perfect - thanks!

I went back to Miui from Pixel Extended due to camera features. Today i got my update on Miui13...holy hell...
I havent seen a worse system in years. Laggy, slow..simply trash. Sorry to brag about this, but this is unnacceptable. and i look into some alternatives soon.(another rom).

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
Click to expand...
Click to collapse
serapax said:
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
The MIUI OTA update first downloads the update file to your phone. That file should still be on your phone somewhere. See if you can find it and note where it is. Then ...
​Launch ‘Settings’ app on your device, select ‘About phone’, click ‘System update’, then press ‘three dots’ icon at the top-right corner, and select ‘choose update package’ to enter. Choose the ROM file you’ve put in ‘downloaded_rom’ in Step 2.
Fold Image
{
"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"
}

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
something like that happened to me sometime back with MIUI 12. came back the update prompt few days later.

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.