Hi Everyone,
I have a Google Edition Pixel XL with unlocked bootloader, TWRP installed, as well as Magisk 16.0 installed. I would like to know the steps in layman's terms for what is needed to install OTA and keeping data? Then what are the next steps if any to do about keeping the bootloader unlocked, and being able to use TWRP, as well as Magisk to have root?
I have not attempted to updated OTA since I have unlocked the bootloader. I just do not want to lose anything.
Apologies for a newbie question and forgive me for asking for a little handholding
statustray said:
Hi Everyone,
I have a Google Edition Pixel XL with unlocked bootloader, TWRP installed, as well as Magisk 16.0 installed. I would like to know the steps in layman's terms for what is needed to install OTA and keeping data? Then what are the next steps if any to do about keeping the bootloader unlocked, and being able to use TWRP, as well as Magisk to have root?
I have not attempted to updated OTA since I have unlocked the bootloader. I just do not want to lose anything.
Apologies for a newbie question and forgive me for asking for a little handholding
Click to expand...
Click to collapse
a. Flash factory image instead of OTA, go to this thread:
[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch and do #4 Keep Data
b. To Root/Reroot after flashing factory image do # 7
c. "keeping the bootloader unlocked": Don't lock it.
Homeboy76 said:
a. Flash factory image instead of OTA, go to this thread:
[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch and do #4 Keep Data
b. To Root/Reroot after flashing factory image do # 7
c. "keeping the bootloader unlocked": Don't lock it.
Click to expand...
Click to collapse
Good Morning Homeboy76,
Thanks so much for the information and links! It is much appreciated Have you installed June 2018's patch?
Homeboy76 said:
a. Flash factory image instead of OTA, go to this thread:
[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch and do #4 Keep Data
b. To Root/Reroot after flashing factory image do # 7
c. "keeping the bootloader unlocked": Don't lock it.
Click to expand...
Click to collapse
My concern is an unlocked bootloader is an attack vector right? Why can't I relock with TWRP/Magisk? My thought is crossing a border tbh. I'm not doing anything, but don't want my device rootkit-ed if they decide they need to investigate it for whatever reason.
statustray said:
Good Morning Homeboy76,
Thanks so much for the information and links! It is much appreciated Have you installed June 2018's patch?
Click to expand...
Click to collapse
The June 2018 patch is included in the June 2018 factory image.
---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------
bobbob1016 said:
My concern is an unlocked bootloader is an attack vector right? Why can't I relock with TWRP/Magisk? My thought is crossing a border tbh. I'm not doing anything, but don't want my device rootkit-ed if they decide they need to investigate it for whatever reason.
Click to expand...
Click to collapse
Why can't I relock with TWRP/Magisk? If you lock the bootloader without returning the phone to stock you'll brick your phone
bobbob1016 said:
My concern is an unlocked bootloader is an attack vector right? Why can't I relock with TWRP/Magisk?
Click to expand...
Click to collapse
You did say you wanted to keep your data, didn't you?
Oh, and the whole being unable to boot thing, since you won't be stock.
Sent from my Pixel XL using Tapatalk
pkelly517 said:
You did say you wanted to keep your data, didn't you?
Oh, and the whole being unable to boot thing, since you won't be stock.
Click to expand...
Click to collapse
No I didn't really. And no one is clarifying WHY it won't boot... My best guess from what I read is signing? And I'd further guess that said signing must be done by Google not TWRP? Any way TWRP can protect against 3rd party mods by someone with my device to read my data/install stuff?
Related
ok, this is driving me crazy. had every nexus except the 6, got the 5x. unlocked bootloader, ok. flash twrp. cool. install root files, great. set up android pay, denied due to unlocked boot loader. went to lock boot loader... wants to do a factory reset.... ok..... now it just boot loops in twrp formats cache, and phone gives errors about corrupt system, different system, blah blah. so right now im bootloader unlocked, rooted with twrp. how is everyone relocking the boot loader?
You have to be on stock recovery to relock the bootloader. You can hardbrick this phone trying to lock it with TWRP installed. Consider yourself lucky?
Android pay is not working because of root, not the unlocked bootloader. Start reading about systemless root
berndblb said:
You have to be on stock recovery to relock the bootloader. You can hardbrick this phone trying to lock it with TWRP installed. Consider yourself lucky?
Android pay is not working because of root, not the unlocked bootloader. Start reading about systemless root
Click to expand...
Click to collapse
yes, i flashed the systemless root on my n5x ( i have a regular nexus 5, twrp, bootloader locked, and android pay works with systemless root) so i do now about this recent development. can it be flashed in stock recovery? i just feel like im missing something?
From the [GUIDE] Unlock/Root/Flash for Nexus 5X that you should have read before farting around with the phone:
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 11 of this guide for full instructions on how to return to stock.
Click to expand...
Click to collapse
Use the guide I linked to to flash the stock images. Then use the guide again to root the phone with systemless root.
PiousInquisitor said:
From the [GUIDE] Unlock/Root/Flash for Nexus 5X that you should have read before farting around with the phone:
Use the guide I linked to to flash the stock images. Then use the guide again to root the phone with systemless root.
Click to expand...
Click to collapse
thanks for the link, thats one of the first things i read when i started looking but it doesnt really talk about relocking the bootloader unless going stock. im just trying to keep my systemless root and have locked bootloader. sounds like i should try reflashing stock recov after rooting and then try to relock bootloader?
dwreck420 said:
thanks for the link, thats one of the first things i read when i started looking but it doesnt really talk about relocking the bootloader unless going stock. im just trying to keep my systemless root and have locked bootloader. sounds like i should try reflashing stock recov after rooting and then try to relock bootloader?
Click to expand...
Click to collapse
It plainly says:
mportant: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 11 of this guide for full instructions on how to return to stock.
Click to expand...
Click to collapse
If you have rooted your phone, you are not fully stock. Therefor do not relock the bootloader.
dwreck420 said:
yes, i flashed the systemless root on my n5x ( i have a regular nexus 5, twrp, bootloader locked, and android pay works with systemless root) so i do now about this recent development. can it be flashed in stock recovery? i just feel like im missing something?
Click to expand...
Click to collapse
The 5X is my first Nexus so bare with me. Why would you have TWRP installed with a locked bootloader on the OG Nexus 5? What is the benefit of that?
SlimSnoopOS said:
The 5X is my first Nexus so bare with me. Why would you have TWRP installed with a locked bootloader on the OG Nexus 5? What is the benefit of that?
Click to expand...
Click to collapse
well there was an app "bootunlocker" which let you unlock it on the fly. also android pay requires a locked bootloader.
so i have locked bootloader, systemless root, and twrp on my OG nexus 5.
just cant seen to relock bootloader and somehow reroot again since NOW nexus 5x required device be WIPED when relocked
PiousInquisitor said:
It plainly says:
If you have rooted your phone, you are not fully stock. Therefor do not relock the bootloader.
Click to expand...
Click to collapse
does android pay work for you with unlocked bootloaders and systemless root?
dwreck420 said:
well there was an app "bootunlocker" which let you unlock it on the fly. also android pay requires a locked bootloader.
so i have locked bootloader, systemless root, and twrp on my OG nexus 5.
just cant seen to relock bootloader and somehow reroot again since NOW nexus 5x required device be WIPED when relocked
Click to expand...
Click to collapse
Oh, that sounds pretty cool actually.
I don't use Android Pay but I know you do not need a locked bootloader to get it working. Which version of SuperSU did you install? Cuz every time I see a 5X user with working Android Pay, they have systemless root and even a custom rom. I am pretty certain that I read that you just need to delete /SU/xbin_bind to get Android Pay working with systemless root.
Edit: I've seen it mentioned in the SuperSU thread I think, but it is explicitly mentioned in this Nexus 6P Android Pay thread
dwreck420 said:
does android pay work for you with unlocked bootloaders and systemless root?
Click to expand...
Click to collapse
Yes. This is common knowledge.
Android Pay looks for changes to the system partition only. It doesn't give a rats ass if the kernel, recovery, or boot image are modified, nor does it give a flying **** if the bootloader is unlocked.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Yes. This is common knowledge.
Android Pay looks for changes to the system partition only. It doesn't give a rats ass if the kernel, recovery, or boot image are modified, nor does it give a flying **** if the bootloader is unlocked.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thanks for the clarification.
dwreck420 said:
thanks for the clarification.
Click to expand...
Click to collapse
No problem. Sorry if I came across a bit hostile. I may have been up too late last night.
Android Pay is also working on some ROMs. Cataclysm for one. PureNexus will be comparable next update too.
Sent from my Nexus 5X using Tapatalk
Never mind
Sent from my Nexus 5X using Tapatalk
So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.
Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.
TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks
Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.
TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now
[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.
The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot
Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk
awesome , thanks again everyone for your time and the help, very much greatly appreciated.
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
So i have the Sprint variant and TWRP / rooted so i could SIM unlock the phone. Now I did a Flashall.bat with stock Sprint 8.0.0 image and then did an OTA update to latest build. So I am assuming I am stock with Sprint factory image and factory recovery but my bootloader is still unlocked and I am NOT rooted (SuperSU / Magisk or otherwise). I am not passing SafetyNet check and thus cannot DL Netflix, use Google Pay, banking app complaining. I have a few questions:
Whats the least painful or suggested route to this? I'm assuming SafetyNet fail is due to unlocked bootloader
If I relock the bootloader will this erase data similar to unlocking does?
I read that flashing a custom kernel will fix this by not tripping a Safetynet Flag but what other effects does this do? Will it break OTA?
I do not want to root because I would like to continue receiving OTA updates.
Thanks in advance!
If you relock bootloader safetynet will pass and OTA will work
Marcowe said:
If you relock bootloader safetynet will pass and OTA will work
Click to expand...
Click to collapse
Yeah but does relocking the bootloader on our phones wipe data (factory reset)?
I ask because I heard it does on some Android phones.
Thanks for the reply!
jeffritz1 said:
Yeah but does relocking the bootloader on our phones wipe data (factory reset)?
I ask because I heard it does on some Android phones.
Thanks for the reply!
Click to expand...
Click to collapse
Relocking the bootloader will erase everything, that is the same for all phones with unlockable bootloaders. Magisk hides your unlocked bootloader and helps you pass safety-net while rooted with magisk.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
Relocking the bootloader will erase everything, that is the same for all phones with unlockable bootloaders. Magisk hides your unlocked bootloader and helps you pass safety-net while rooted with magisk.
Click to expand...
Click to collapse
Got it. But Magisk means goodbye OTA's correct?
jeffritz1 said:
Got it. But Magisk means goodbye OTA's correct?
Click to expand...
Click to collapse
Correct
Anyway to not wipe data, still accept OTA's, and pass SafetyNet?
jeffritz1 said:
Anyway to not wipe data, still accept OTA's, and pass SafetyNet?
Click to expand...
Click to collapse
You could boot twrp and flash pantheon. When you want to ota, just flash stock boot img and you can get ota again. Pantheon hides the flags in cmdline that make you fail safetynet. (In your case, the bootloader lock status flag). You could do the same with magisk though as well, you would just have to do a no wipe flash all when you want an ota. (Edit the .bat to not wipe user data)
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?