https://developers.google.com/android/images
picked it up via OTA. They seem to be doing a better job getting OTAs ready right away. $10 says the screen flash is still there.
It supposedly fixes sound in video recordings, so that will be interesting to see. I don't record much video, but when I do, I want it to sound decent.
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
PuffDaddy_d said:
I just wish they'd fix the Google Assistant to start responding to the Hey Google hotword again. It's super frustrating when a key feature doesn't work.
Click to expand...
Click to collapse
I use "Hey Google" almost daily. I haven't seen reports of the hot phrase not working. Do many people have this problem?
- Pixel 3XL
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
l2tp bug is also still present! wtf Google. fix this!
sliding_billy said:
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
What was your process?
acidspider said:
What was your process?
Click to expand...
Click to collapse
1. Magisk saved to the phone (Just to be sure, I would confirm you have the one that Topjohn posted with the same version very shortly after originally posting V18 originally since there was an issue installing kernels after his 1st V18. The one on the main Magisk thread is the right/current one)
2. flash-all (without -w)
3. Once system boots back up, shut down, boot back to fastboot with key combo (I do all of my boots to fastboot from full shutdown and with key combo not ADB) and fastboot boot the current (different versions for my two phones) TWRP .img
4. Install Magisk V18
5. Reboot system from TWRP
6. Verify root and SafetyNet
7. Install ElementalX from EX application
8. After kernel forces reboot, just normal maintenance stuff like definitions for AdAway, checking modules, reinstalling BusyBox, installing native tethering prop
mikeprius said:
It appears I am $10 rich. I screen flash still there.
No worries. Just wait till the February update boys.
Click to expand...
Click to collapse
It's probably at the bottom of Google's list of priorities. It is hard to replicate, occurs rarely, and doesn't affect performance in any way. I wouldn't hold my breath waiting for a fix any time soon.
Installed v18 on both a P3 and P3XL (from the TWRP .img). No problem with either.
Click to expand...
Click to collapse
Yea I just installed v17.3 and upgraded to v18 through manager. Weird, must've been a bad download.
JJT211 said:
Has anyone had any issues with Magisk on this January update? I just updated and tried installing Magisk v18 and started bootlooping. I may try v17.3. Ill report back
EDIT: v17.3 installed just fine
Click to expand...
Click to collapse
I'm on canary 18.1 and it installed just fine.
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
SmokinCharger said:
I have been using the flash-all ( without -w) each month since I got the phone. I just installed the Jan update. However, the "Security patch level: September 5, 2018" still shows. Are you guys getting this too?
Click to expand...
Click to collapse
It should say Jan 5. Something went wrong, redo it and make sure you redownload the Jan update. Feels like maybe you didn't clean up or grabbed the wrong image.
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
ShadowJP88 said:
Strangely, since January update,I try to modify my host file again but it stay there only for a few minutes and get erase back to the original... Anybody know why?
Click to expand...
Click to collapse
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Cares said:
Why does it matter if you reboot-bootloader or using the "key combo"? It shouldn't matter.
Click to expand...
Click to collapse
I don't know, but I know there was some wonky behavior in TWRP a couple of months ago that only showed if you used ADB reboot or TWRP reboot. My only guess is that something gets cleared from memory during a full power down and that it simply looks like the difference is in the electronic vs. key combo method when it is actually in the power down function.
I think you are right. I talked about this on another thread because I have placed a LatineIME folder in my system/app folder, changed permissions, rebooted and used AOSP keyboard fine with every other update until Jan. Now, I place the folder in my system/app, change permissions, reboot and it is gone. I have tested this on three different phones, og pixel, Pixel 3, and Moto G5 Plus running custom Pie rom with Jan update. All three have the same problem.
PuffDaddy_d said:
It seems like system write privileges aren't sticking with the January update. Check my magisk thread below for updates.
https://forum.xda-developers.com/pixel-3/how-to/magisk-pixel-3-t3853445
Click to expand...
Click to collapse
Related
[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.
Hi to all,
Android 10 Final is now available (for Pixel phones)
https://developers.google.com/android/images#blueline
JC
0.19 and 0.20... what's the difference ?
is there a difference between the two versions? I'm guessing verizon vs non-verizon like a lot of the other ones, but which is which?
Looks like there are 2 versions. For a new version is the side load OTA technique still how it is done ? This would be the first time I would be loading a new version on Android non OTA/locked bootloader.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Based on previous versions of android, the specific ones are typically the secondary versions and the standard unlock are the first copy. Edit: see below comments.
My Pixel 3 on Fi is updating now. I'll come back and edit this post to let you all know which sub-version gets installed.
Edit:
So Google P3 on Fi pulled the .019 version. Hope that helps.
mikeprius said:
Looks like there are 2 versions. For a new version is the side load OTA technique still how it is done ? This would be the first time I would be loading a new version on Android non OTA/locked bootloader.
---------- Post added at 11:24 AM ---------- Previous post was at 10:54 AM ----------
Based on previous versions of android, the specific ones are typically the secondary versions and the standard unlock are the first copy. So probably the .019 is the one for everyone and the 0.20 is the version for Verizon.
Click to expand...
Click to collapse
i've sideloaded the newest of the 2 versions to my non verizon phone and it worked fine- only "issue" - i can see the build number at to top bar when i pull it down. Thats strange
robjective said:
My Pixel 3 on Fi is updating now. I'll come back and edit this post to let you all know which sub-version gets installed.
Click to expand...
Click to collapse
I'm on the P3 with Verizon but Google device. Updating now as well 1337.4 Mb d/l.
just wanted to sideload the other version but its getting canceled imediatelly ....
OTA
Just finished installing the OTA update and for my factory unlocked (non Verizon) pixel 3 its .20
Installed 10 on my wife's P3 (my 3 XL is on Havoc OS, and I am not ready for a factory reset) using flash-all (without -w). Root went fine. Had to put AdAway into systemless, but otherwise no real issues yet. I did notice during the flash that it beings up a screen that looks like it is going to fail and force you into recovery (and ultimately a factory reset), but it just kept chugging along in command prompt and rebooted like that screen was meant to be. Only thing post install that is odd is that clearing recent apps (half flip up and swipe to the right and clear all) leaves a shell of the app that says it is not available if you click on it and goes away completely with a lock and unlock.
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Just Ota. Mine says 0.19
Bought from Google store unlocked
Force 2D GPU rendering
Force 2D GPU acceleration is gone from developer options. On .20 OTA. But there is now a game driver preferences menu.
...
Cris7ianO said:
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Click to expand...
Click to collapse
Sweet! Just to make it crystal clear, you say this procedure works (credits to xda member Phil_Chambers) : (with magisk canary for now, I guess)
1-Download the 9.0.0 (PQ1A.181205.006, Dec 2018) file from https://developers.google.com/android/images
2-Unzip the contents of the zip into your ADB/Fasboot folder (I just leave my ADB folder on the desktop, windows 7). This is assuming you downloaded ADB/Fastboot program for Windows.
3-Right click and open the flash-all.bat file with a free program called Notepad++ and remove the last part of the text that says "-w" and SAVE FILE.
4-Remove the Edge sense module from Magisk on your phone if installed.
5-Make sure the phone has USB debugging enabled and USB cable plugged in with FILE TRANSFER mode turned on.
6-Run command in ADB/Fastboot:
adb reboot bootloader
click on adb flash-all.bat [now that its modified with -w removed. If -w was not removed, the phone will be WIPED CLEAN!]
(phone will restart) Go back into ADB/Fasboot:
adb reboot bootloader
adb fastboot boot <insert_name_of_TWRP_image_here>.img
7-Once in TWRP, FLASH your TWRP.ZIP and restart into Recovery.
8-Flash Magisk, other stuff etc at this point.
There is no need to remove Magisk or Unzip the secondary file inside the OTA. I've done it without those steps and nothing was changed.
I did re-install the latest version of Edge sense in Magisk as he put out a new version that works with the latest DEC update.
Click to expand...
Click to collapse
gatharot said:
Sweet! Just to make it crystal clear, you say this procedure works (credits to xda member Phil_Chambers) : (with magisk canary for now, I guess)
Click to expand...
Click to collapse
Yes, can confirm. Worked for me. As I am not pleased with the performance I will do a clean one just to be sure.
Cris7ianO said:
Just updated to 10 with flash-all and without -w. Procedure worked fine. This is my first experience with 10. And honestly Google like wtf, these gestures are horrible, unbelievable. How is it possible Apple does this million times better. So back on the good old 3 button layout.
Another thing: 10 feels even more laggy on the P3 than Pie. Anybody else experiencing this? Maybe I should try a new clean install... I am a die-hard Android fan but the experience on the 3 besides taking pictures with the great camera has just been disappointing from day 1 until now. Problem is, I don't see an alternative that keeps this form factor... The 7 pro is just to big.
Click to expand...
Click to collapse
I did a clean install with the factory ota images on a brand new P3. Super smooth! Plus, there's an option in 10 to go back to two- or three-button navigation instead of gestures
Been using for 24 hrs. The gestures are a bit choppy. Also it will not work with 3rd party launchers for the time being which sucks. The gestures don't really feel that smooth. When I use the back gesture and side menu they can get mixed up at times.
Bingley said:
I did a clean install with the factory ota images on a brand new P3. Super smooth! Plus, there's an option in 10 to go back to two- or three-button navigation instead of gestures
Click to expand...
Click to collapse
The 3 button navigation under accessibility options removes the ability for screen rotation by button
I just tried using flash.bat from the factory image (after removing the "-w") and now my phone is stuck in a bootloop....what on earth. I updated to the newest version every single time using that method but now it's screwed up....
For reference, previously the only thing I did was root with Magisk using TEMPORARY TWRP with Adaway. Nothing else. I have no idea why it isn't working. May need to go back to the August update...
Now it's saying in fastboot mode "no valid slot to boot". In terms of SDK Platform Tools, I'm using the newest ones that were from July 2019 (got it straight from their site yesterday).
EDIT: Flashed the August update back on my phone. Gonna stick with that for now since it's working fine anyways. Not in a rush to update to Android 10 or in general anyways.
Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Update: oxygen 11 released for the UK / EU
Thanks
Thanks for the post, just updated this way.
For some reason there were no update available for mine I was stuck on 5.4 - > Now 5.6 via this updater.
kalinlondon said:
Thanks for the post, just updated this way.
For some reason there were no update available for mine I was stuck on 5.4 - > Now 5.6 via this updater.
Click to expand...
Click to collapse
Nice one. Good to know it's not just me
After getting tired of waiting for the OTA update to 10.5.11.IN11BA to arrive, I used the Oxygen Updater to do it myself.
However, after the update I noticed that in the System Update screen, the changelog that was previously available at the bottom (as a slide up) is now gone.
Is this behavior expected? Should I worry for something, e.g. not getting any future OTAs?
dladz said:
Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Click to expand...
Click to collapse
Been using this app since I got my OP8P a month ago ?
Hugo_Sanchez said:
Been using this app since I got my OP8P a month ago ?
Click to expand...
Click to collapse
You have to be sure your getting the proper update for your phone version ie, China,UK, India, global They each have different ones
str8str said:
You have to be sure your getting the proper update for your phone version ie, China,UK, India, global They each have different ones
Click to expand...
Click to collapse
Actually the app identifies your model and will only provide updates for that model..
I mean that's my experiences of it.
dladz said:
Actually the app identifies your model and will only provide updates for that model..
I mean that's my experiences of it.
Click to expand...
Click to collapse
Yes of course ?
dladz said:
Not my app but a find in the play store
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Just used it to update from 5.5 to 5.6.
I wasn't being offered it from system update so I thought I'd try it.
Worked first time.
Click to expand...
Click to collapse
Is root necessary for updating with this app ?
xs1cht said:
Is root necessary for updating with this app ?
Click to expand...
Click to collapse
No
New dev preview available for the EU version via the app.
Haven't taken the plunge as I need stability at the moment.
Anyone flashes it, please let me know how it goes
10.5.12 is now available for the EU version of the device..
Downloading now..
Edit:
Installed and working well.
Couldn't comment on battery yet but feature wise it's about the same.
Thanks for writing about the app here. I just installed 10.5.14 on my EU OP8 Pro and everything is working well. The "official" installer didn't show this Update.
Magisk and NoLimits are working well.
drevel123 said:
Thanks for writing about the app here. I just installed 10.5.14 on my EU OP8 Pro and everything is working well. The "official" installer didn't show this Update.
Magisk and NoLimits are working well.
Click to expand...
Click to collapse
Yep absolutely, this app has been a god send to many, works with root albeit with an added process, beyond that's it's a spot on app.
Long may it last.
The official oxygen 11 update has rolled out for the UK / EU
Information as per oxygen updater.
Let the good times begin.
New update has arrived for the EU 2023
Will be updating and seeing if root, centre clock, xXx are affected..
Apparently canvas is now integrated too.
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Pekeltje91 said:
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Click to expand...
Click to collapse
No TWRP for A11
Pekeltje91 said:
Does anyone have the OTA link for the new EU version?
Or the Stock boot.img ?
I downloaded it to my phone using the app, did a local update, before rebooting installed magisk beta to my inactive slot, and did a reboot.
Now its stuck while booting, and TWRP doesnt seem to boot either with fastboot boot twrp.img
Edit: Got it working again.
Does anyone have a working TWRP, the version i tried gave a Qualcomm Crashdump mode error. (Havent tried after it worked again).
Click to expand...
Click to collapse
Why did you install twrp on 11? Just install your patched magisk partition.
All you needed to do was take the update then without booting go to magisk and install after OTA
dladz said:
Why did you install twrp on 11? Just install your patched magisk partition.
All you needed to do was take the update then without booting go to magisk and install after OTA
Click to expand...
Click to collapse
I tried to boot it, but didnt work.
But that was after i did the OTA from this app, and Magisk to the inactive slot.
Then a reboot and it didnt work, did not boot for some reason (Stuck on the red dot, with 2 white dots moving).
So then i tried the TWRP boot (No flash).
Maybe it was because of some Magisk modules (But it was just Smali and Recording enabler for OOS)
But its working again
But no option to boot TWRP so far when Android 11 is installed?
Thought it was OS independent.
Edit: patched and stock boot.img from Android 11 update from today (OnePlus8ProOxygen_15.E.31_OTA_0310_all_2011010124_d85208) for the OnePlus 8 Pro EU model.
Stock boot.img: test.jordykroeze.com/oneplus/android11_v2/boot.img
Magisk patched boot.img: test.jordykroeze.com/oneplus/android11_v2/magisk_patched.img