MMB29Q factory image is available on Google developers site (FWIW).
https://developers.google.com/android/nexus/images
So does the Q mean it's actually an older build than S what we currently have?
zip please
StykerB said:
So does the Q mean it's actually an older build than S what we currently have?
Click to expand...
Click to collapse
No. MMB29Q was just posted by Google this afternoon. It is the latest, February security update.
StykerB said:
So does the Q mean it's actually an older build than S what we currently have?
Click to expand...
Click to collapse
MMB29Q has a build date of Fri Dec 11 00:43:54 UTC 2015
MMB29S has a build date of Tue Dec 15 22:16:10 UTC 2015
Bit odd that it has an older build date and build number. Once AOSP has been updated with these new builds, it'll make more sense.
I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
And just for the fun...
The zip components are dated 5th January, and the images are dated 1st January 2009.
I'm not touching this with a bargepole until someone explains this to me in one-syllable words...
dahawthorne said:
I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
Click to expand...
Click to collapse
Not sure about that. FWIW, in "about the phone" it says: "Android security patch level: February 1, 2016".
and one more thing, T was the latest, and im on it. but its not there anymore. now S is before Q
Was there a modem update with Q.....or T?
Edit: I believe latest was 32R for reference.
Edit 2: Just extracted the archive and the Modem is the same as last release. Bootloader size and name are also exactly the same so I don't think there was a new bootloader or modem. (In version Q)
I just extracted and only system.img looks different to me, although both the bootloader and radio images have January 5, 2016 build dates compared to January 1, 2009 dates for S. I think I'll just fastboot all of them to be safe.
Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.
AlkaliV2 said:
Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.
Click to expand...
Click to collapse
HI I got the same message, so i did this:
1. Clean Flash again.
2. Boot the phone for first time, but in the part that ask for a pin or Pattern i didn't.
3. Flash supersu systemless.
4. Boot the phone and set a pattern and enjoy.
Hope this can be helpful for you.
dahawthorne said:
I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
And just for the fun...
The zip components are dated 5th January, and the images are dated 1st January 2009.
I'm not touching this with a bargepole until someone explains this to me in one-syllable words...
Click to expand...
Click to collapse
I got the Q update today via normal OTA and I was on January's S update. So I'd say that the Q update is legit.
I'm running on 32R with no issues so I'm gonna keep it that way.
Took the q update, no probs don't understand why s is older then q. But stable and no issues at all
Sent from my Nexus 6 using Tapatalk
log1321 said:
HI I got the same message, so i did this:
1. Clean Flash again.
2. Boot the phone for first time, but in the part that ask for a pin or Pattern i didn't.
3. Flash supersu systemless.
4. Boot the phone and set a pattern and enjoy.
Hope this can be helpful for you.
Click to expand...
Click to collapse
AlkaliV2 said:
Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.
Click to expand...
Click to collapse
Marshmallow kernel images (boot.img) check for system partition integrity and therefore regular injection of su binary inevitably causes the corruption message to appear. So when you flash these updates either you should manually patch the kernel or use systemless root which includes that patch.
Use SuperSU 2.66 which automatically determines which method should be used to install SuperSU.
---------- Post added at 03:51 AM ---------- Previous post was at 03:48 AM ----------
simms22 said:
and one more thing, T was the latest, and im on it. but its not there anymore. now S is before Q
Click to expand...
Click to collapse
If you still have the T update do u think you can post it online somewhere? Thanks.
MMB29T was announced on 4th January, so MMB29Q is the latest, since it has a security revision date of 1st February.
Google are making a right dog's breakfast of these update sequence letters...
And why use SuperSU 2.66 when there's already a stable 2.67?
I wanted to find out if anyone else has had any problems since this update. I'm having odd freezes that last 30 seconds to a minute. Also my Mailwise app is shutting itself down every minute or so. TouchPal keyboard doesn't respond after it pops up occasionally. Security updates have never caused me a problem before. I'm on Marshmallow 6.0.1, with an unlocked bootloader(if that matters), using Nova Launcher.
Sorry if I put this in the wrong forum, but none of these problems existed before the update. Thanks guys!
@ahpukuh,
I've not had any of the problems that you mention, or any problems at all. FWIW, I'm running the stock launcher and keyboard.
najoor said:
Marshmallow kernel images (boot.img) check for system partition integrity and therefore regular injection of su binary inevitably causes the corruption message to appear. So when you flash these updates either you should manually patch the kernel or use systemless root which includes that patch.
Use SuperSU 2.66 which automatically determines which method should be used to install SuperSU.
---------- Post added at 03:51 AM ---------- Previous post was at 03:48 AM ----------
If you still have the T update do u think you can post it online somewhere? Thanks.
Click to expand...
Click to collapse
Then why don't I get the corruption message when am rooting with NRT, which I thought used the older "system" root.?
Related
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
You can't flash an OTA with TWRP, and you can't take an OTA if you have root/modifications. If you've never rooted or modified in any way you should be able to just flash the stock recovery back and then initiate the OTA process. If you do have root you need to flash the factory images to update. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sr Vincenzo said:
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
Click to expand...
Click to collapse
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Heisenberg said:
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Click to expand...
Click to collapse
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Sr Vincenzo said:
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Click to expand...
Click to collapse
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Heisenberg said:
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Click to expand...
Click to collapse
Alright man...
Some people should never unlock their bootloader or root their phone.
UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I used Heisenberg's method yesterday and it worked well. If you copy the commands into notepad, edit them so the file paths and build numbers are correct you can just copy/paste into the command prompt. All settings will be saved with the exception of a couple of widgets I had to redo.
I will say with the latest update the device seems faster so I feel like it is worth it.
I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
anirbannath said:
I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
Click to expand...
Click to collapse
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
myksh said:
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
Click to expand...
Click to collapse
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
anirbannath said:
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
Click to expand...
Click to collapse
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
myksh said:
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
Click to expand...
Click to collapse
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
anirbannath said:
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
Click to expand...
Click to collapse
Umm, yes. I meant I got stuck and flashfire showed the same error you faced, find it attached below.
Also, yes that's what I meant by security patch but if you get into the other partition, which still will be on the August patch, you'll have to download the September patch(1+gb) and then the October one(118mb). If it doesn't work, you'll have to download the rom file from miui.com flash it and then update to October patch.
This A/B partitioning is nowhere near a feature but looks more like an extended road and a U turn to get back to the same place. Only the ones who wont root their phones will be happy.
Facing the same issue as you guys. I can live without the October patch for a while. What do you guys think? Will flashgire be updated to accommodate these updates in the future or will TWRP be the way to go?
when i try to update via settings it says installation error. looks like i will have to be on september patch for now. any other way to update?
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Minimum effort to reflash firmware to September, download October and reroot october: 45 mins
Not sure how you were able to do it that fast but I'll stay on September until something easier comes around
me also waiting solution for this problem
tonycapuozzo said:
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Click to expand...
Click to collapse
How did You unrooted ?By super su or something else?
rkview37 said:
How did You unrooted ?By super su or something else?
Click to expand...
Click to collapse
Flash the stock boot.img
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
robgee789 said:
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Just flashing boot image via flashfire, and wifi doesnt work anymore. Trying to flash with MiFlash and the last rom , getting an error.
How to return to stock rom?
Any help please...!!
ok now.A mistake in process...!!! :fingers-crossed:
There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.
its actually october patches. l14 in the US got this update before the l04.
TomTheGeek3 said:
its actually october patches. l14 in the US got this update before the l04.
Click to expand...
Click to collapse
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs
ayush rao said:
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread
TomTheGeek3 said:
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread
Click to expand...
Click to collapse
Awesome thanks!
Sent from my FRD-L04 using Tapatalk
Saw this update message and got excited thinking we were getting Android Oreo... security updates are such a tease!
I'm glad to see the October security release updated so quickly for the Honor 8. To bad the KRACK vulnerability wasn't fixed until the Nov release. Hopefully it is patched quickly too given how serious it is.
How do you spoused to download if you got twrp threw updater or what?
ayush rao said:
There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.
Click to expand...
Click to collapse
i m downloading it right now on L04, Karachi - Pakistan
SSyar said:
i m downloading it right now on L04, Karachi - Pakistan
Click to expand...
Click to collapse
It is October Security Patch
Mikeyy233 said:
How do you spoused to download if you got twrp threw updater or what?
Click to expand...
Click to collapse
EDIT - this post made me go ahead and create a new Guide thread. Please check it out if you are wondering how to take an upgrade if you have unlocked and rooted your phone.
Here is the original post I made....
I just researched this myself and this is what I did....
1) Make a backup using TWRP (if the new update locks the phone, you will need this backup to restore data after unlocking it)
2) The update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you are like me, you don't have a copy of the stock recovery image on hand (if you do have a copy, then skip to step 3). Therefore we need to extract it from the stock ROM image. Download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
download the Hauwei Update Extractor software and install it on a computer. Here is a Youtube video showing how to use it. You only need to extract the "Recovery.img" file for our use (the video extracts several additional files that we don't need). Move the stock recovery image to your ADB folder so you can flash it in step 3.
3) Use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of TWRP.
4) Reboot into system
5) Go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 3gb, so make sure you are ready to handle that size transfer. For me, the phone automatically did the update after downloading the package. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong. It worked fine the second attempt.
6) The phone will reboot and you should check the status to make sure you are on the latest version.
7) I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update. I was simple able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, the read the note at the bottom of this post.
8) Reboot into system
9) Reboot into recovery and flash Magik zip to get SuperSU.
10) Reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
11) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NAIDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.
SSyar said:
It is October Security Patch
Click to expand...
Click to collapse
Did u notice anything else or is it just the security patch?
Sent from my FRD-L04 using Tapatalk
ayush rao said:
Did u notice anything else or is it just the security patch?
Click to expand...
Click to collapse
It's just a security patch.
#Boring
PuffDaddy_d said:
It's just a security patch.
#Boring
Click to expand...
Click to collapse
That is so disappointing but atleast they bothered updating the phone. Its a good sign that Oreo still might come.......
Sent from my FRD-L04 using Tapatalk
Delete....
Does anyone know when KRACK will be patched? I think Google included it in the November security updates. This may mean I'll come in December?
How it's battery life on these update ... b388 kills my battery like crazy ???
luisaet82 said:
How it's battery life on these update ... b388 kills my battery like crazy [emoji23][emoji23][emoji23]
Click to expand...
Click to collapse
Really? I get great battery life on B388. Actually I hadn't formatted my phone in over 8 months and when I did it I started getting really good battery life. You could maybe try that too?
Sent from my FRD-L04 using Tapatalk
I'm gonna give a try today
Oh boy it's looking great so far
FYI
Factory images:
https://developers.google.com/android/images
OTA:
https://developers.google.com/android/ota
Just finished installing a Pixel and a PIxel XL with no issues. Used flash-all (deleted the -w), fastboot boot TWRP (decrypt worked) but not permanent install, Magisk 16.0 rooted. All pretty seamless this month. No change to platform-tools since December.
sliding_billy said:
Just finished installing a Pixel and a PIxel XL with no issues. Used flash-all (deleted the -w), fastboot boot TWRP (decrypt worked) but not permanent install, Magisk 16.0 rooted. All pretty seamless this month. No change to platform-tools since December.
Click to expand...
Click to collapse
I just completed the same process and can confirm all is well. Will report back on if I notice any improvements/differences.
Anyone having problems with their microphone after updating to the June Patch? Mine no longer works.
UPDATE: Turns out it was an issue with my custom kernel. A fix was already pushed down by the dev.
Alcolawl said:
Anyone having problems with their microphone after updating to the June Patch? Mine no longer works.
Click to expand...
Click to collapse
Phone calls have been fine for me.
sliding_billy said:
Phone calls have been fine for me.
Click to expand...
Click to collapse
No issues. I've made and received several calls since I updated yesterday evening. No one reported any issues hearing me. I also just tested via Sound Recorder app and audio was recorded and played back without issue.
sliding_billy said:
Phone calls have been fine for me.
Click to expand...
Click to collapse
sb1893 said:
No issues. I've made and received several calls since I updated yesterday evening. No one reported any issues hearing me. I also just tested via Sound Recorder app and audio was recorded and played back without issue.
Click to expand...
Click to collapse
Appreciate the swift feedback, fellas. Turns out it was the custom kernel I had flashed after the update. The dev pushed out a fix minutes after I posted here lol. Thanks!
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Carrzy said:
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Click to expand...
Click to collapse
Not seeing any difference or delay at all on the OG Pixel XL...still as speedy as ever....
Anyone else notice the difference in the June images ?
EDIT : NEVERMIND . I downloaded the wrong images apparently ............. Lol .
Sent from my Pixel XL using Tapatalk
This can't be normal right? Trying to flash the factory image from scratch...
EDIT: Fixed by updating my ADB and Fastboot to the latest google provides.
Carrzy said:
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Click to expand...
Click to collapse
I read those too. Weird. No difference in speed here. Still nearly instant.
I just got my pixel xl , and for the may update i did a adb sideload fastboot twrp rooted, . Is flash- all with -w deleted the same as a ota or well i need to well i need to set up the phone all over again. Just wondering ,
brightjh01 said:
I just got my pixel xl , and for the may update i did a adb sideload fastboot twrp rooted, . Is flash- all with -w deleted the same as a ota or well i need to well i need to set up the phone all over again. Just wondering ,
Click to expand...
Click to collapse
flash-all with -w deleted will save your data. You will not have to set up your phone 'all over again'
I know I can dl this and do it manually, and I shall do (I have done for several years now), but how the f is my non-google essential ph1 receiving the update notification for June OTA before my PXL?!? This has been constant since I got the ph1in April.
It seems the whole "quickest" update pull for ElGoog devices no longer has any real point.
Any noticeable improvement with this update?
Homeboy76 said:
flash-all with -w deleted will save your data. You will not have to set up your phone 'all over again'
Click to expand...
Click to collapse
Hi. I'm running stock rom, rooted with magisk, TWRP permanently installed. I used to flash repackaged OTAs using TWRP on my Nexus 6. Is that no longer a 'thing' for the Pixel phones?
Assuming that there are no TWRP flashable OTA updates, then what I'm hoping for is a set of detailed (idiot-proof) instructions for updating to the June OTA ... ideally with an explanation about what I will have to re-do after installing the update (will I have to reinstall TWRP, Magisk?).
Thanks to anyone who can point me in the right direction. :good:
demlv said:
Hi. I'm running stock rom, rooted with magisk, TWRP permanently installed. I used to flash repackaged OTAs using TWRP on my Nexus 6. Is that no longer a 'thing' for the Pixel phones?
Assuming that there are no TWRP flashable OTA updates, then what I'm hoping for is a set of detailed (idiot-proof) instructions for updating to the June OTA ... ideally with an explanation about what I will have to re-do after installing the update (will I have to reinstall TWRP, Magisk?).
Thanks to anyone who can point me in the right direction. :good:
Click to expand...
Click to collapse
Step-by-step instructions for the Pixel/Pixel XL are on this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Read them: #4 and #7 for answer(s) to your question(s)
Do them: Do #4 Keep Data (4.1.) to update firmware, then do # 7 to root/reroot.
Homeboy76 said:
Step-by-step instructions for the Pixel/Pixel XL are on this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Read them: #4 and #7 for answer(s) to your question(s)
Do them: Do #4 Keep Data (4.1.) to update firmware, then do # 7 to root/reroot.
Click to expand...
Click to collapse
Noob here. I had been using Nexus 5x and I just receive the Pixel XL recently. I have followed the guide post above. Just wanna make sure something:
1. If I wanna update and keep data, why not adb sideload OTA instead of fastboot factory image?
2. If I unlock bootloader with stock recovery and root with Magisk, can I still get OTA update?
3. Do I need to reroot every time after update?
thanks
digimon04 said:
Noob here. I had been using Nexus 5x and I just receive the Pixel XL recently. I have followed the guide post above. Just wanna make sure something:
1. If I wanna update and keep data, why not adb sideload OTA instead of fastboot factory image?
2. If I unlock bootloader with stock recovery and root with Magisk, can I still get OTA update?
3. Do I need to reroot every time after update?
thanks
Click to expand...
Click to collapse
1. You could side load the OTA then Fastboot twrp.img, flash twrp.zip, and flash Magisk.
2. I don't think so. Note: Once you unlock the boot loader DO NOT lock it until you have completed #3 B.
3. Yes
The reason I suggest Do #4 Keep Data to install factory image (I think it is simpler), then Do #7 to Root
Can someone please paste a link to the 11.0.4.4 global installation file. My Oneplus8 pro is rooted and as such I cannot download it from system updates. I tried to fastboot an unpatched boot but I couldn't get WiFi to turn on. Accordingly, I'd like an alternate download option for 11.0.4.4 global.
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Have not seen the full 11.0.4.4 global zip anywhere yet....
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
Tried that. No joy.
State.of.mind said:
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Click to expand...
Click to collapse
I tried that, but when I did I couldn't get wifi enabled. I tried to download on cellular but it repeatedly failed. I rarely use cellular and I only have 2gb/mo. (If it were stable I'd be fine.)
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
Oxy updated still has 2 2 not 4.4
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
No joy.
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
almahix said:
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
following.
devsk said:
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
Click to expand...
Click to collapse
Yes Magisk works on 4.4. There's a 4.4 Boot image thread in the Guides. You should be able to find it
almahix said:
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
dladz said:
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
Click to expand...
Click to collapse
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
almahix said:
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
Click to expand...
Click to collapse
I have the BA model. So I can't help you there mate.
There were people flashing BA according to people in my thread, perhaps contact them via PM and see what they say.
Wasn't a big deal by all accounts.
11.0.4.4 available now via OnePlus site.
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
almahix said:
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
Click to expand...
Click to collapse
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
bouchigo said:
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
Click to expand...
Click to collapse
Great idea! I never thought of patching the stock boot.img on another device. It worked and now I'm finally rooted. Thank you for sharing your idea! BTW my former phone was a Pixel2XL. Was that the best phone ever? Still is but I sold it when I bought my 8pro. Big mistake!