Related
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
SoCmodder said:
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
Click to expand...
Click to collapse
tried to flash the modified but failed
jiggajaydroid said:
tried to flash the modified but failed
Click to expand...
Click to collapse
Are you on the stock rom? I'm not sure it will work if you're on the deodexed one.
tried flashing the modified one on a stock rooted rom. Firmware portion gave failure notice.. Seems like build.prop has new version but i'm still getting update nag
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
CNexus said:
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
Click to expand...
Click to collapse
Thank you, Sir!!
CNexus said:
I'll be posting a full OTA zip for rooted users that contains the full updated files in a bit (not just the patch.p files)
Click to expand...
Click to collapse
Thanks!
will this wipe the phone ? will i loose root ? i am s-on . can i flash over bone stock rom ?
thanks
andybones said:
Thank you, Sir!!
Click to expand...
Click to collapse
Are you planning on updating your bonestock rom with this OTA Andy, or is it not worth it since it's a relatively small one?
Sent from my HTC6500LVW using xda app-developers app
red rage said:
will this wipe the phone ? will i loose root ? i am s-on . can i flash over bone stock rom ?
thanks
Click to expand...
Click to collapse
Would like to know this too as i am bootloader unlocked with s-on and rooted. if this will patch my bootloader, what service do i freeze to avoid getting the nagging OTA notification?
Thanks
I am s-on, but unlocked and rooted. I'm still unlocked and I'm still rooted after applying this update. I wouldn't recommend doing it on another Rom though. It would probably fail.
Sent from my HTC6500LVW using Tapatalk 2
I am s-off with rumrunner can i just flash the modified OTA?
thewagdy said:
I am s-off with rumrunner can i just flash the modified OTA?
Click to expand...
Click to collapse
If you still have stock recovery yes. Then flash custom recovery and su. Choose the nonmodified one.
Sent from my Nexus 7 using Tapatalk 4
dottat said:
If you still have stock recovery yes. Then flash custom recovery and su. Choose the nonmodified one.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I already have custom recovery
thewagdy said:
I already have custom recovery
Click to expand...
Click to collapse
Check this then.. http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Nexus 7 using Tapatalk 4
SoCmodder said:
I got the OTA update notification today, but I couldn't install because of CWM.
I modified the zip to remove the recovery check, but it's the first one I've ever done, so I'm not sure if it will work. Either way, you'll probably have to reflash CWM if it does work.
As always, I'm not responsible for anything that goes wrong with your phone. Whether it blows up, catches fire, or just bricks....not my fault.
Anways, here are both the OG and the modified versions of the OTA update.
UPDATE: I just flashed the modified zip and it installed fine. Got rid of that annoying notification and I still kept root by choosing to fix root after flashing it.
Modified
Original
Click to expand...
Click to collapse
The original is unrooted and signed? I need to be able to flash it via stock recovery or in RUU. Need to get someone back to .10 for rumrunner.
BreakingVZW said:
The original is unrooted and signed? I need to be able to flash it via stock recovery or in RUU. Need to get someone back to .10 for rumrunner.
Click to expand...
Click to collapse
This is just the update files from .08 to .10. They aren't full roms. There is another thread with stock roms, but I'm not sure about stock recovery. You may have to pull it from the RUU.
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Do you have a link to their research or are their findings private?
Regards,
Mr_Bartek said:
Do you have a link to their research or are their findings private?
Regards,
Click to expand...
Click to collapse
saurik - his analysis of the "second master key vuln"
giantpune for his symlnink attack vuln in property space:
Code:
/system/bin/mv /data/property /data/backupprop
/system/bin/mkdir /data/property
/system/bin/ln -s /sys/kernel/uevent_helper /data/property/.temp
/system/bin/setprop persist.sys.fail /data/pwn.sh
jcase said:
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
coolrevi said:
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
Click to expand...
Click to collapse
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
jcase said:
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
Click to expand...
Click to collapse
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
ricky310711 said:
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
Click to expand...
Click to collapse
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
pulser_g2 said:
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
Click to expand...
Click to collapse
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
ricky310711 said:
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
Click to expand...
Click to collapse
It depends on if OEMs backported it, depends on which build OEMs used and depends on the bug. Four or five different zip parser bugs with similar results. This one I used was patched in 4.3, but other exist.
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
trickraca said:
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
Click to expand...
Click to collapse
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
jcase said:
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
Click to expand...
Click to collapse
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
It should not come rooted, if it comes rooted then no way did it pass CTS. I'm guessing unlocking the bootloader and flashing a recovery? I don't know, I dont have one
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
noobish doubts..
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Please i ne ed a walthrough..
1) download twrp
2) put it in root of the telephone robot
3) flash it in recovery?
4) reboot recovery wipe cache and dalvik flash omnirom..
Please correct me..
Thank you
giuliano rigon said:
1) download twrp Yes
2) put it in root of the telephone Yes
Make sure to copy Omnirom to your phone at some point
3) flash it in recovery? No - Flash TWRP in Fastboot if you haven't flashed the recovery already. Use the official Teamwin site for guidance
4) reboot recovery wipe cache and dalvik flash omnirom.. Wipe Cache, Dalvik, System, and Data
Click to expand...
Click to collapse
Updates in Red
This is off-topic for this thread though. Questions/Info for flashing Omnirom should be addressed in the Omnirom thread.
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
not rooted.. confirm i can flash
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
I nave tried my damnedest to root .. Fastboot flashing supersu flashing from recovery Direct install from google play complete unroots and reflash letting recovery do it .. No way..
So now i need a last confirmation.. Can i flash omnirom after wipes even if i am unrooted.. And has anyone rooted omnirom or does it come unrooted.. Thanks for the info .. Another idea.. Flashing color OS footing and then flashing omni.. Or is this a late night bad Dream..
---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------
Harfainx said:
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
Click to expand...
Click to collapse
Sorry now i got it.. It was in the forums.. Just unchecking the respect cyanogen settings in the super su menu got me roooted and happy.. Sorry for your time.. I flashed super su zip from recovery rebooted and unchecked .. Now i am set..
I were rooted myN1 in yesterday, its really good . thankss
Sent from my N1 using XDA Premium 4 mobile app
Does OTA updating work while bootloader is unlocked? Or does it not work only when rooted/custom recovery?
coyotefiveoh said:
Does OTA updating work while bootloader is unlocked? Or does it not work only when rooted/custom recovery?
Click to expand...
Click to collapse
Having an unlocked bootloader does not interfere with accepting an ota, root, exposed , TWRP recovery and any other alteration will cause the ota to fail.
Sent from my XT1635-02 using XDA-Developers Legacy app
Thank you sir
flashallthetime said:
Having an unlocked bootloader does not interfere with accepting an ota, root, exposed , TWRP recovery and any other alteration will cause the ota to fail.
I have a rooted device with f2f patch, twrp and supersu, can I still install the OTA?, or I have to restore to stock?
EDIT: the OTA i am receiving is nougat 7.0 (yeah, till today I am receving nougat...)
Click to expand...
Click to collapse
tronoslycer said:
I have a rooted device with f2f patch, twrp and supersu, can I still install the OTA?, or I have to restore to stock?
EDIT: the OTA i am receiving is nougat 7.0 (yeah, till today I am receving nougat...)
Click to expand...
Click to collapse
You have to reflash stock. Root and TWRP will cause OTA updates to fail.
tronoslycer said:
flashallthetime said:
Having an unlocked bootloader does not interfere with accepting an ota, root, exposed , TWRP recovery and any other alteration will cause the ota to fail.
I have a rooted device with f2f patch, twrp and supersu, can I still install the OTA?, or I have to restore to stock?
EDIT: the OTA i am receiving is nougat 7.0 (yeah, till today I am receving nougat...)
Click to expand...
Click to collapse
Why would you take a chance and end up hard bricked? I gotta bang my head against the wall as you already have TWRP installed and you can flash my nougat stock 7.1.1 rom which has the July 1st security update.
Really folks you really like to play Russian roulette with your phone
Click to expand...
Click to collapse
flashallthetime said:
tronoslycer said:
Why would you take a chance and end up hard bricked? I gotta bang my head against the wall as you already have TWRP installed and you can flash my nougat stock 7.1.1 rom which has the July 1st security update.
Really folks you really like to play Russian roulette with your phone
Click to expand...
Click to collapse
really??, can you give me the link to download that flasheable ROM?, its pre-rooted?, I need root to modify build.prop, I need Miracast, thanks
Click to expand...
Click to collapse
flashallthetime said:
tronoslycer said:
Why would you take a chance and end up hard bricked? I gotta bang my head against the wall as you already have TWRP installed and you can flash my nougat stock 7.1.1 rom which has the July 1st security update.
Really folks you really like to play Russian roulette with your phone
Click to expand...
Click to collapse
ok, now I want to update to the december patch but one of the requirement is to have a nougat bootloader, but whan installed TWRP i had marshmallow. that means I have a MM bootloader because I never updated to nougat by OTA. I have an MM NANDROID I made with TWRP, how I can update my bootloader?
thanks in advance
Click to expand...
Click to collapse
tronoslycer said:
flashallthetime said:
ok, now I want to update to the december patch but one of the requirement is to have a nougat bootloader, but whan installed TWRP i had marshmallow. that means I have a MM bootloader because I never updated to nougat by OTA. I have an MM NANDROID I made with TWRP, how I can update my bootloader?
thanks in advance
Click to expand...
Click to collapse
This purports to do it though I haven't tried it myself.
https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
Click to expand...
Click to collapse
KrisM22 said:
tronoslycer said:
This purports to do it though I haven't tried it myself.
https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
Click to expand...
Click to collapse
thanks
Click to expand...
Click to collapse
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, sounds doable
ABotelho23 said:
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
Click to expand...
Click to collapse
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
XDRdaniel said:
Yes, sounds doable
Click to expand...
Click to collapse
Yeah. Well.. I'm gonna try this out myself. Thanks! :highfive:
GTRanushka said:
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
Click to expand...
Click to collapse
Plan to keep a copy of OB18 around? If so, then yea absolutely it should work. Root will either modify your system or your kernel depending on the method, which both get overwritten if you flash stock.
Issue you'll probably end up having in the future though is that if you always use OB18, when it comes time to install OB20, you'll be downgrading without a wipe, which I don't think is a great idea.
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Simone98RC said:
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Click to expand...
Click to collapse
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
XDRdaniel said:
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
Click to expand...
Click to collapse
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
This would be weird because I always had to flash magisk after a ota update..
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
ajnexus5 said:
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
Click to expand...
Click to collapse
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
Why i try to unroot and do OTAs is the much less download size compared to FOTAs.
Renosh said:
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Click to expand...
Click to collapse
I tried it with the bootloader open and I did not think that something is not right that it has to download complete the rom.:
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