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
Related
https://developers.google.com/android/nexus/images?hl=en
I haven't even gotten MDB08L via OTA yet. Has anyone else gotten either of the two?
I'm still on MDB08I too. Went through the "about phone" to check for an update and it says there isn't one. Don't really want to flash this seeing as i'm not rooted or unlocked.
Very strange that they'd release two images simultaneously. Can't recall seeing something like this before.
I think MDB08x is just carrier specific I I got notified for mdb08i when I first booted the phone up with no sim. After I put my verizon sim in, it said I was up to date. But when I put a tmobile sim in and right away prompted me to update.
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.
sgravel said:
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.
Click to expand...
Click to collapse
I see the same thing, but I reflashed the "systemless" rooted boot image and it booted up just fine. Differences are minimal, I guess?
I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!
jm.kloz said:
I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!
Click to expand...
Click to collapse
https://groups.google.com/forum/#!msg/android-security-updates/n1aw2MGce4E/jhpVEWDUCAAJ
k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
delete
To restate, I'm running the MDB08M build. And I'm rooted.
I used the systemless bullhead boot.img from http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
I did however use the factory image script to wipe the phone clean when I flashed it. That was the only vaguely strange thing I did.
Not noticed any strange behaviour, but this phone isn't my daily driver yet.
Added some screengrabs
Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk
adrialk said:
Is the update file available anywhere so you can update without a data wipe?
Click to expand...
Click to collapse
I haven't found an OTA zip link yet, but I'm sure they'll come. What I don't get it why Google doesn't post the OTA links themselves.
adrialk said:
Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
If your bootloader is already unlocked, yes by flashing the factory image's system.img manually. If not unlocking the bootloader would trigger a wipe.
You'll be able to adb sideload once someone captures an OTA for it, but in theory the OTA should start rolling out to everyone gradually.
If my bootloader is unlocked is it impossible to accept an ota update? The only other nexus I messed with is my mom's N7 2013 and it's a royal pain to install updates on it. Have to manually do everything to save the data.
Unlocked bootloader has no effect on ota update.
Sent from my Nexus 5X using Tapatalk
Looks like the change logs have been posted
MDB08L is the Security Update and MDB08M is the WLAN patch below.
https://android.googlesource.com/platform/hardware/broadcom/wlan/+/25e0325
Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.
antiseen said:
Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.
Click to expand...
Click to collapse
Im on Verizon and still on MDA89E. Im still completely stock. Im reading up on bootloader unlock, recovery and root so I dont EFF anything up
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.?
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
USFguy said:
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
Click to expand...
Click to collapse
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks, I haven't used adb since 2014 with my HTC One X so I'm a little hesitant but seems easy enough.
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
no, everything will just fine..
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
Nope, it has no effect on future OTA's.
Heisenberg said:
Nope, it has no effect on future OTA's.
Click to expand...
Click to collapse
Just unlock bootloader and flash?
USFguy said:
Just unlock bootloader and flash?
Click to expand...
Click to collapse
Yeah that's it, unlock your bootloader and flash the factory images for MHC19I and you'll be up to date.
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
samomamo said:
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
Click to expand...
Click to collapse
Did you read the other posts in this thread?
Heisenberg said:
Did you read the other posts in this thread?
Click to expand...
Click to collapse
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
samomamo said:
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
Click to expand...
Click to collapse
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Heisenberg said:
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Click to expand...
Click to collapse
Thanks alot bro, im just lazy to set everything up again.
samomamo said:
Thanks alot bro, im just lazy to set everything up again.
Click to expand...
Click to collapse
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Heisenberg said:
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
Click to expand...
Click to collapse
Thanks a lot u convinced me. I unlocked and for the hell of it flashed the Android N. Man is so fast , its like running 60fps, I thought its just gonna be little ui changes, but i was wrong. Its like lightning fast. Thanks
Ok it didnt last long. Back to M latest. The N was fast, but toooo many glitches.
Heisenberg said:
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Click to expand...
Click to collapse
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
USFguy said:
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
Click to expand...
Click to collapse
You should have no issues flashing the images without wiping userdata.
Heisenberg said:
You should have no issues flashing the images without wiping userdata.
Click to expand...
Click to collapse
Ah, but I think I answered my own question, won't unlocking the bootloader wipe all data anyway?
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:
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