I've had my pixel 2 xl for a few weeks now. I unlocked bootloader, flashed TWRP, rooted with magisk 16.4 and I am on flash kernal with stock ROM. I am getting a prompt for a Google security update. I shouldn't update with this right? Would I lose root or maybe it wouldn't work? Why am I getting the prompt since I'm rooted? Thanks.
Sent from my Pixel 2 XL using Tapatalk
getsideways said:
I've had my pixel 2 xl for a few weeks now. I unlocked bootloader, flashed TWRP, rooted with magisk 16.4 and I am on flash kernal with stock ROM. I am getting a prompt for a Google security update. I shouldn't update with this right? Would I lose root or maybe it wouldn't work? Why am I getting the prompt since I'm rooted? Thanks.
Click to expand...
Click to collapse
It wouldn't update anyway since your rooted with custom recovery. You can long press the notification to shut it off, and in developer options, disable automatic updates :good:
Related
I've seen the guides for rooting the Developer Previews--but has any of that changed?
I'm on Marshmallow, decrypted using Xceed and TWRP.
I want to flash the Factory images and then root afterwards. Best advice?
wait until the kernels are done and/or supersu has been updated to reflect new build
I had the update notice when I got home Monday. It downloaded the update, and then I used FlashFire to apply the OTA since I had twrp installed. FF updated the tablet and then re-rooted it. Still have twrp and root.
Sent from my Nexus 5X using Tapatalk
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
n1ck0 said:
Hi,
Do you mean that with flashfire you can root your pixel c and get Ota update without loosing data or root???
Thanks for your help
Click to expand...
Click to collapse
I used FlashFire to install the OTA and kept data and root.
The title says it all. I'm running a Google version of Pixel XL unlocked, rooted with TWRP installed. How can I update to 7.1.1 while using a Mac?
john7760 said:
The title says it all. I'm running a Google version of Pixel XL unlocked, rooted with TWRP installed. How can I update to 7.1.1 while using a Mac?
Click to expand...
Click to collapse
On a Mac is is easy as pie. It is like a Linux system as the pixel will be recognized. Just download the standalone adb and fastboot installer. I don't remember the thread but do a search
Good luck. My Mac won't work with my phone's anymore. I year or so ago I lost the ability to do anything with adb and fastboot.
Sent from my Pixel XL using XDA-Developers mobile app
john7760 said:
The title says it all. I'm running a Google version of Pixel XL unlocked, rooted with TWRP installed. How can I update to 7.1.1 while using a Mac?
Click to expand...
Click to collapse
Us this http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187. You just need to put "./" in front of all fastboot commands. This will keep data but flash new system. Once you are back to stock just reflash twrp and reroot. Just did this yesterday and it worked perfectly. Just make sure you are on slot a not slot b when you flash everything.
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 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
Dear XDA members,
picking up my Pixel 3 XL I decided to get again in touch with all the custom rom's, kernals, rooting and all this.
I have been there but never really touched it since my Galaxy Nexus and did not much with my Nexus 5 completely disbanding the topic since my Nexus 6P.
I just have some question were I could not find an definite answer for myself or found different missleading ones so I bet some of you definetly will know them. Also my memory since the Galaxy Nexus Era dramatically diminished so basically learning everything new with Magisk, the A/B partition thing etc.
So help is appreciated.
Should you enable or disable the Adaptive Battery if you have a custom kernal?
What happens with Googles Adaptive Battery Feature if you are rooted and even have a custom kernal? Is it straight up not "working", do you have to "learn" it again does it resets everytime?
At which step normal OTA Google Updates will fail to install?
unlocked bootloader
unlocked bootloader + rooted via patched boot.img from magisk manager
unlocked bootloader + rooted via flash Magisk via temporary booted TWRP
Can you be more "lazy" to keep your phone up to day and still be unlocked/rooted.
Currently my phone is unlocked but completely setup with apps, personal data.
1.) boot twrp
2.) flash magisk via twrp [optional flash twrp itself => If you just plan to get rooted there is no need to install twrp it self right?]
If there is a new factory image Update
3.) boot twrp and flash magisk uninstaller via twrp then boot into bootloader and
5.) flash the factory image WITHOUT -w
6.) repeat 1.) 2.)
Or is it better with the patched boot.img?
Thanks in advance please don't blame me for this for sure stupid questions.
Miniqpa said:
Dear XDA members,
picking up my Pixel 3 XL I decided to get again in touch with all the custom rom's, kernals, rooting and all this.
I have been there but never really touched it since my Galaxy Nexus and did not much with my Nexus 5 completely disbanding the topic since my Nexus 6P.
I just have some question were I could not find an definite answer for myself or found different missleading ones so I bet some of you definetly will know them. Also my memory since the Galaxy Nexus Era dramatically diminished so basically learning everything new with Magisk, the A/B partition thing etc.
So help is appreciated.
Should you enable or disable the Adaptive Battery if you have a custom kernal?
What happens with Googles Adaptive Battery Feature if you are rooted and even have a custom kernal? Is it straight up not "working", do you have to "learn" it again does it resets everytime?
At which step normal OTA Google Updates will fail to install?unlocked bootloader
unlocked bootloader + rooted via patched boot.img from magisk manager
unlocked bootloader + rooted via flash Magisk via temporary booted TWRP
Can you be more "lazy" to keep your phone up to day and still be unlocked/rooted.
Currently my phone is unlocked but completely setup with apps, personal data.
1.) boot twrp
2.) flash magisk via twrp [optional flash twrp itself => If you just plan to get rooted there is no need to install twrp it self right?] Your choice to inatall or not install twrp. Some say install it, others prefer to just boot it.
If there is a new factory image Update
3.) boot twrp and flash magisk uninstaller via twrp then boot into bootloader and
5.) flash the factory image WITHOUT -w
6.) repeat 1.) 2.)
Or is it better with the patched boot.img?
Thanks in advance please don't blame me for this for sure stupid questions.
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Do #4 'keep data', then do #8 to root
I think flashing the factory image is better.
Homeboy76 said:
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Do #4 'keep data', then do #8 to root
I think flashing the factory image is better.
Click to expand...
Click to collapse
I read this post you linked before opening mine but still had this questions.
Why do I have to flash the factory image if I am already on stock? Or do you mean in case if there is an actual ugrade?
Thanks for your answer.
Miniqpa said:
I read this post you linked before opening mine but still had this questions.
Why do I have to flash the factory image if I am already on stock? Or do you mean in case if there is an actual ugrade?
Thanks for your answer.
Click to expand...
Click to collapse
You don't, just do #8 to root: #4 is for monthly upgrdes.
My last Google device was a Nexus 4, since then I've always had a Samsung S-series smartphone, so I've never touched root again. With Pixel 3 I run the risk of losing some function when doing root?
Enviado de meu SM-G950F usando o Tapatalk
Guto ViP said:
My last Google device was a Nexus 4, since then I've always had a Samsung S-series smartphone, so I've never touched root again. With Pixel 3 I run the risk of losing some function when doing root?
Enviado de meu SM-G950F usando o Tapatalk
Click to expand...
Click to collapse
I don't think you'll lose any functions, you can gain the use of functions by rooting.
Guto ViP said:
My last Google device was a Nexus 4, since then I've always had a Samsung S-series smartphone, so I've never touched root again. With Pixel 3 I run the risk of losing some function when doing root?
Enviado de meu SM-G950F usando o Tapatalk
Click to expand...
Click to collapse
You'll just have to use Magisk Hide on a few things (like Google Play Store to keep the unverified notice away or Google Pay which is checked by default) where you need Safetynet from being tripped. Other than that, run stock and rooted and it is all good that you gain.
Should you enable or disable the Adaptive Battery if you have a custom kernal?
What happens with Googles Adaptive Battery Feature if you are rooted and even have a custom kernal? Is it straight up not "working", do you have to "learn" it again does it resets everytime?
At which step normal OTA Google Updates will fail to install?unlocked bootloader
unlocked bootloader + rooted via patched boot.img from magisk manager
unlocked bootloader + rooted via flash Magisk via temporary booted TWRP
Click to expand...
Click to collapse
/push
ok i have booted into temp twrp just fine installed twrp just fine but any time i install magisk i just boot to the G and the loading bar under it then it reboots into twrp i have even tried installing custom kernel what am i doing wrong?
DrUnkeN_TiGeR said:
ok i have booted into temp twrp just fine installed twrp just fine but any time i install magisk i just boot to the G and the loading bar under it then it reboots into twrp i have even tried installing custom kernel what am i doing wrong?
Click to expand...
Click to collapse
After you install twrp and your kernel, let the OS boot up, then go back to twrp and flash magisk again and see if that works.
Do I have to flash a custom kernel?
Badger50 said:
After you install twrp and your kernel, let the OS boot up, then go back to twrp and flash magisk again and see if that works.
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
DrUnkeN_TiGeR said:
Do I have to flash a custom kernel?
Click to expand...
Click to collapse
If you want to keep touch response working in twrp, yes. At least until twrp gets fixed.
Badger50 said:
If you want to keep touch response working in twrp, yes. At least until twrp gets fixed.
Click to expand...
Click to collapse
What did twrp-3.2.3-2 fix?