Related
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.
mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota
Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk
Are you rooted? If so just get the ota from google and flash it with flashfire
jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.
I just flashed it this morning and had no problems.
I flashed a couple of hours ago official OTA package via ADB. No problems till now.
I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes
jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.
ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.
ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.
Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
Worst things that could happen are: OTA fails to install or you have to reinstall Magisk through fastbooting/T
WRP, so just try it.
I just flash full factory image and flash TWRP, Flash Kernel, and Magisk again, instead of waiting for OTA to be available through the phone.
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
To be safe i would use the flash-all for December update. It will take to back to stock kernel and remove magisk. Then take the January ota. I think that is a sure way and doesn't take to many step.
Better to do flash all bat of January Factory Image, and reflashing magisk after that,
You can edit the flashing script, removing -w to prevent it wiping your data
I've tried it twice to no avail. I was able to go back to magisk and reinstall. I haven't lost anything. Ymmv...
I have a Google edition Pixel XL on Vzw's network. I have only had it for a few weeks. I am currently running android 8.1.0, unlocked bootloader, with root and Majisk 16.0. Just a short while ago, I received a notification that there is an update available- specifically a Security update available and the update size is 68.2 MB. This leads up to my question.
Do I need to do anything special prior to installing this "security update"? Do I install this update? I am coming from a Samsung Galaxy Note 3 so I am certainly not up on the does/don'ts of this bootloader unlocked, with root and Majisk 16.0.
Thanks so much in advance.
statustray said:
I have a Google edition Pixel XL on Vzw's network. I have only had it for a few weeks. I am currently running android 8.1.0, unlocked bootloader, with root and Majisk 16.0. Just a short while ago, I received a notification that there is an update available- specifically a Security update available and the update size is 68.2 MB. This leads up to my question.
Do I need to do anything special prior to installing this "security update"? Do I install this update? I am coming from a Samsung Galaxy Note 3 so I am certainly not up on the does/don'ts of this bootloader unlocked, with root and Majisk 16.0.
Thanks so much in advance.
Click to expand...
Click to collapse
You cannot have any root or magisk or xposed installed to apply the update. Your bootloader can be unlocked though. To unroot to update just flash the boot.img. also can't have twrp installed
statustray said:
I have a Google edition Pixel XL on Vzw's network. I have only had it for a few weeks. I am currently running android 8.1.0, unlocked bootloader, with root and Majisk 16.0. Just a short while ago, I received a notification that there is an update available- specifically a Security update available and the update size is 68.2 MB. This leads up to my question.
Do I need to do anything special prior to installing this "security update"? Do I install this update? I am coming from a Samsung Galaxy Note 3 so I am certainly not up on the does/don'ts of this bootloader unlocked, with root and Majisk 16.0.
Thanks so much in advance.
Click to expand...
Click to collapse
I followed Tenn3r's guide. You don't have to do anything special you just have to flash magisk again.
https://forum.xda-developers.com/showpost.php?p=75480639&postcount=3
there is also this guide # 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
these worked fine for me. The only thing is I had to put my factory image files in the platforrm-tools folder.
George_Bushels said:
I followed Tenn3r's guide. You don't have to do anything special you just have to flash magisk again.
https://forum.xda-developers.com/showpost.php?p=75480639&postcount=3
there is also this guide # 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
these worked fine for me. The only thing is I had to put my factory image files in the platforrm-tools folder.
Click to expand...
Click to collapse
Do I need to uninstall majisk and twrp first when using the factory image files?
No. I don't even have to uninstall Xposed. You'll have to flash twrp and magisk again tho.
George_Bushels said:
No. I don't even have to uninstall Xposed. You'll have to flash twrp and magisk again tho.
Click to expand...
Click to collapse
Thanks a bunch, I appreciate the info
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
w_tapper said:
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
Click to expand...
Click to collapse
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Lughnasadh said:
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
Click to expand...
Click to collapse
w_tapper said:
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Click to expand...
Click to collapse
If that is how you updated, then correct. Each time you update via OTA it updates to the opposite slot you are on. Since you updated twice like this, both slots should have A13 on them and you should be fine.