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
I am on 8.1 DP2 which is OPP6.171019.012, tried to install the official 8.1 OTA which is OPM1.171019.011 : obviously the latter is older that DP2, so now I am still on DP2.
Maybe I need to wait for the OTA for those that are on beta program?
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
skw5115 said:
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
Click to expand...
Click to collapse
I can confirm this, I have updated this way.
anyone has the OTA for those on DP2?
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Mikulec said:
I can confirm this, I have updated this way.
Click to expand...
Click to collapse
I'm assuming you already had an unlocked bootloader?
Mr Patchy Patch said:
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
Click to expand...
Click to collapse
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
oxman said:
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Click to expand...
Click to collapse
go to the website and unenroll.
imnuts said:
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Usually an OTA is made to go from one specific build to another. Which would make sense on why you can't do it that way. If you have the unlocked bootloader flashing the factory image for 8.1 can be done.
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
If you have an unlocked bootloader, you can update now with the factory image. Otherwise wait until the OTA rolls or for beta users.
Sent from my Pixel 2 XL using Tapatalk
I just got the small ota to bump me from DP2 to final. So it's in the wild now. You can probably force the update at this point.
Like he said, I just got the official OTA bump yesterday to final. If you can't force it, it should come soon regardless.. This shows the December 5th patch.
hrkahn said:
I'm assuming you already had an unlocked bootloader?
Click to expand...
Click to collapse
yes
I have same problem with Nexus 5X.
Adb sideload breaks at 47%.
Now i can only wait, because i have the no-rpmb-bug.
is there anyway to Sideload Android P Preview on a lock Verizon Pixel 2 Xl ? I can get it to work getting errors like E:footer is wrong e:error 21 E:signatire verification failed
Thanks
https://developer.android.com/preview/download.html
Go to your recovery and flash it through adb sideload
I tried to flash it the ADB Sideload update.zip and it get to 0% and fails
You may have to enroll in Beta first in order for P to work.
There is no Beta Yet For Android P
Badwished said:
There is no Beta Yet For Android P
Click to expand...
Click to collapse
After doing some research, you have to be bootloader unlocked to flash the Android P firmware.
This is a developer preview. Next version will be Beta and then there will be an ota method.
update your adb and fastboot.
and get the OTA from here: https://developer.android.com/preview/download-ota.html
Remember if you go P on Verizon you can't go back because of the locked bootloader.
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
bond32 said:
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
Click to expand...
Click to collapse
You can flash the factory images through adb to go back to 8.1. I was on P and went back
franchise said:
You can flash the factory images through adb to go back to 8.1. I was on P and went back
Click to expand...
Click to collapse
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Why did you go back to O?
bond32 said:
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Click to expand...
Click to collapse
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
franchise said:
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
Click to expand...
Click to collapse
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Sorry to hear that. I may try it tomorrow to see if it works for me.
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Yep, P is technically older than what you have so it won't OTA. A new P is due any day now.
//
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.
Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.
Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.
Thank you. I tried to find it on the github site and found nothing.
Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.
Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
nima0003 said:
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
Click to expand...
Click to collapse
Do you have update to 10.5.5.IN11AA ?
gaww said:
Do you have update to 10.5.5.IN11AA ?
Click to expand...
Click to collapse
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
spotmark said:
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
Click to expand...
Click to collapse
Just got the phone and it updated to .5, and late at night, .6 showed up. It installed without all the trouble with TMo 7.
It unrooted, and I used the .5 magisk patched.img above without any problems, but will use .6 when available.
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
dladz said:
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
Click to expand...
Click to collapse
Thanks. I didn't wipe and I don't use fingerprint.
gaww said:
Thanks. I didn't wipe and I don't use fingerprint.
Click to expand...
Click to collapse
Right ok, might want to check it if you ever do. Just in case
Will this work on the Verizon compatible phone?
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
If you're using an unlocked 8 Pro, sure. If you're using an 8, purchased directly from Verizon, no.
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
Check your pms if you want to tinker with the Verizon model with
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Ecna said:
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Click to expand...
Click to collapse
No - don't use old one. If you search, you should find 10.5.10 boot image.
Thanks, I couldn't find a new one so I downgraded to 5.9.
Ecna said:
Thanks, I couldn't find a new one so I downgraded to 5.9.
Click to expand...
Click to collapse
Now you can upgrade back to 5.10 and reinstall magisk before booting up the update. Works real easy.
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Deckardmac said:
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Click to expand...
Click to collapse
Don't make things complicated, update to 10.5.10, boot twrp, install magisk from the zip
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Deckardmac said:
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Click to expand...
Click to collapse
Use 20.4
^ Thanks guys. It worked flawlessly.
how to fix cts profile false on 10.5.10