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] [NMF26U] [Jan 4] Stock Kernel + SafetyNet Patch

Stock Pixel/PixelXL Kernel + SafetyNet Patch
Current version: android-msm-marlin-3.18-nougat-mr1
Suitable for build: NMF26U
Security patch level: January 5, 2017
I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.
Installation:
- Download attached .zip and unzip into a folder
- Reboot device into bootloader (power down device, then Power + Volume down)
- Connect device to computer
- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)
- Enter command: fastboot flash kernel <kernel_image>
- Once flashing is complete, enter command: fastboot reboot
- Disconnect device and wait for reboot sequence to complete.
- You now have a stock Pixel with an unlocked bootloader that can use Android Pay
**WARNING**
If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest
Downloads:
NMF26U
All versions

If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk

joetheshmo said:
If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yep, let's us unlock the bootloader in case we need it in the future, without committing to any mods or losing Android Pay just yet.

Stock + Safetynet patch.... Finally.
Thank you

Thanks for sharing your work, OP.
Sent from my Pixel using Tapatalk

Any chance of you turning this into a flashable TWRP zip? Then I could run ElementalX and root when I want to, and flash back to stock if I want to, all from my phone, in a single reboot.

Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks

@Sakete, I appreciate your attitude.... You need something, you just make it.

jay661972 said:
Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks
Click to expand...
Click to collapse
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Sent from my Pixel using Tapatalk

Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?

Sakete said:
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Click to expand...
Click to collapse
You are right there should have no issues at all since the change was the safetynet patch.
Thanks for this..

quangtran1 said:
Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?
Click to expand...
Click to collapse
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.

Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
{
"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"
}

quangtran1 said:
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add A Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
Click to expand...
Click to collapse
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!

Sakete said:
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!
Click to expand...
Click to collapse
No, thank YOU for the kernel.
One item I must mention. That is, AP will break if you disable login security, or even just changing from PIN to password, or anything that would normally require a reactivation of your Android Pay credit cards. Then you just need to reflash the kernel, which in essence kills root. Add back AP, then reroot.
... Of course, Google can always implement another layer to circumvent this workaround in the future. But that's what makes Android fun.

thank you for this kind sir.
*next on my list is a deodexed stock 7.1 so i can start themeing this device...
time to bring BuuF back

Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...

pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.

pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Sakete said:
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.
Click to expand...
Click to collapse
almost sounds like the active slot got swapped from A to B or B to A. When that happens the previous update boots instead of the current build.
the active slot can be changed in bootloader w/fastboot.
I believe the command for that is:
1. fastboot set_active _a
or
2. fastboot set_active _b
depending on which slot you want active.

I assume that we can flash this over a custom kernel no problem in order to go back to stock?

Rear Low Light Lens - Good, OEM App - Not So Much

Most cameras have settings for 'shutter' or 'aperture' etc priority. They also have 'full auto' or 'full manual'. Our OEM app is limited to much fewer options, as many phone cam apps are.
To take advantage of the 20mp low light rear lens, you have to (of course) use the manual setting to select that lens, AND select the other (available) settings manually. The reason is that the OEM app AUTO is horrible in this area.
I used the AUTO (iso and shutter) for this pic initially. the result was really bad. The iso was auto set to 6400. It was a terrible low light result, very grainy.
Then I set them manually to iso 200 and shutter at 1/2 sec. You need a steady hand or rest the phone on something, and use the timer, it seems to help. Much much better result. I'd say more than acceptable, quite good.
So this isn't an ideal situation. It's time consuming to determine best settings manually, and some good shots don't wait around for you. But it's worth knowing it can be done.
edit; forgot to mention; I have cam2api, no matter though, it seems the Oem app is not using EIS in this situation anyway, the slightest movement meant significantly out of focus. Another negative for the oem app.
{
"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"
}

I do not think that EIS can be applied while you shoot pictures, it only applies when you record videos (in case of using our camera), nice pic though, very realistic.

Yep. EIS only stabilizes video from frame to frame so it's not applicable for still pics

I can't say that the stock camera app is that bad. In fact, compared to other solutions, it proved to be the less noisy option (after camera 2api, OpenCamera becomes terrible to me. GCAM shows too much dots and other apps, like Lightroom takes very noisy pictures too with A2).
When taking daylight or nightly long exposure, the stock camera app shines brighter to me.

Stock cam app makes too much blurry photos for me, like 5 out of 10 will be blurry or without good details, and it is easier for me to partially or completely remove noise from pictures with some external software then to add details.

kadu20es said:
I can't say that the stock camera app is that bad. In fact, compared to other solutions, it proved to be the less noisy option (after camera 2api, OpenCamera becomes terrible to me. GCAM shows too much dots and other apps, like Lightroom takes very noisy pictures too with A2).
When taking daylight or nightly long exposure, the stock camera app shines brighter to me.
Click to expand...
Click to collapse
Oh I agree, the oem app does a very good job in daylight, or manually adjusted exposure time low light.
But the 'auto' settings for low to medium lighting could be better. The Gcam port I have consistently uses a lower iso and longer exposure, using 'auto', then does the oem app under the same conditions.
Part of my reason for the post though is that the rear 20mp lens is much maligned. I think most of that reason is the oem app though, and it's faulty exposure values especially show up with the low light lens, although it's advertised for that scenario. But it turns out to do worse!
It's not the lens though, it's the app.

I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.

ki69 said:
I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.
Click to expand...
Click to collapse
Hey pal, I'm the noobest of the noobs from here, and still, I followed the tutorial and BAM! Got camera2API working.
I tried many times the Majisk with no success. Everytime I rebooted the device the module was gone and I had to patch and do everything again (and even got bootloop when tried to remove majisk), so I gave a chance to TWRP and it worked like a charm.
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.

kadu20es said:
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
If you did not mess with any system files, and enabled camera2 over adb shell, you will have working OTA. :good:

kadu20es said:
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
minnuss said:
If you did not mess with any system files, and enabled camera2 over adb shell, you will have working OTA. :good:
Click to expand...
Click to collapse
I can report, Oct update applied, no issues. Cam2api still enabled

AsItLies said:
I can report, Oct update applied, no issues. Cam2api still enabled
Click to expand...
Click to collapse
Unfortunately didn't work for me.
Maybe I need to flash stock image and try again.
Or wait for Pie.

kadu20es said:
Hey pal, I'm the noobest of the noobs from here, and still, I followed the tutorial and BAM! Got camera2API working.
I tried many times the Majisk with no success. Everytime I rebooted the device the module was gone and I had to patch and do everything again (and even got bootloop when tried to remove majisk), so I gave a chance to TWRP and it worked like a charm.
Now I just don't know about updates, if they will work or not, so, if works, I'll come back here and tell you.
Click to expand...
Click to collapse
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
For now i will not install the october update and wait to see if is released a new TWRP. I really want to enable camera2api. ( man installing Remix Firmwares in My xperia M dual was so more easy than just unlock bootloder and enable camera2api in this Xiaomi...)

ki69 said:
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
For now i will not install the october update and wait to see if is released a new TWRP. I really want to enable camera2api. ( man installing Remix Firmwares in My xperia M dual was so more easy than just unlock bootloder and enable camera2api in this Xiaomi...)
Click to expand...
Click to collapse
No no, I followed this one:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
For now, I think I'll wait for Pie. Maybe there's not thaaaat difference of x.x.6.13.

kadu20es said:
No no, I followed this one:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
For now, I think I'll wait for Pie. Maybe there's not thaaaat difference of x.x.6.13.
Click to expand...
Click to collapse
you put the same guide that i mention.

ki69 said:
you put the same guide that i mention.
Click to expand...
Click to collapse
Ops! Sorry

ki69 said:
You fallow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058 ???
For me that has the best guide, only missing the files need for bee noob proof.
There are many users that have
August
September 1s update
September 2nd Update
And now October
So there are 4 Boot images to search, or extract from Full Formware update, and if some one make a mistake, the things could be messy. Plus there are patch boot images of the firmwares also.
The other problem is that TWRP only works with august patch and no news for a new version ( https://forum.xda-developers.com/mi...nofficial-twrp-recovery-mi-a2-t3825146/page12)
Edit: The other options is to downgrade to August Firmware, but for that need other guide so don´t mess up because i read that the A/B partitions changed from August to September updates.
...
Click to expand...
Click to collapse
Worked, I finally installed the update, however, in order to work, I had to flash boot.img and system.img.
The camera2api is still working after flashing and after update.:good:

kadu20es said:
Worked, I finally installed the update, however, in order to work, I had to flash boot.img and system.img.
The camera2api is still working after flashing and after update.:good:
Click to expand...
Click to collapse
That only means that they enable it by default in October update, I will confirm this today, because my brother has the same stock LOCKED Mi A2
EDIT: Nope, they did not enabled Camera2 by default !!! Just checked and confirmed.

How can u set iso 6400. The maximum limit is 3200 ??

ki69 said:
I´m still waiting for a simple, clean tutorial for enable camera2api only with bootloader unlock and without root so i can still get OTA, with aout messing with A/B partitions and get a briked Phone.
For what i read there are only 2 ways to get camera2api enable:
1- with root , with magisk modules.
2- Without root with TWRP, but depending on the version of the Update , it change A/B partion and we can get the phone briked.
I´, waiting for a noobs guide for that, but the ones that i already read, some of he users that falow the guides get a Bricked Phone, so i will wait for a Noobs Proof Guide for some one that have the second Update for september.
I really want to try the Gcam Mods. Because the reason i bought this phone has the camera features. I regreat i did´t wait a little long and get the POco that have inferior cameras, but have camera2api enable by default.
Click to expand...
Click to collapse
+1

schubeir said:
+1
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
After my post i use this guide and i´ve got Camera2api and all the OTa updates without root, only with bootloader unlocked.

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!

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.