Related
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???
Same thing happened to me. Don't know why yet.
Same here. Where are you from?
Nvidia might have pulled it to fix something wait patiently it will come.
I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!
Exact same issue here.
If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.
Just wait a little. That's what NVIDIA calls "staggered rollout".
Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.
if you have "nougat launcher apk" just delete it.
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.
Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.
When I rooted on Pie, I just didn't bother with OTAs after that. Unless it's a new Android version or has new features, I don't care. Security patches are overhyped drivel. Never had an issue, never will.
When I updated to 10, I Googled like mad and followed some step by step instructions. Easy peasy. But I'd really like to just KNOW what to do and how to do it. So could someone knowledgeable on this walk me through the correct way to deal with OTAs when stock rooted with Magisk. The only root stuff I even really use is a few substratum themes here and there, which of course I know to disable/uninstall before an update.
Unless I'm mistaken (or just remembering it wrong), there's a nifty A/B method for doing OTAs and keeping Magisk/root.
Anyway, could someone just give me a play by play of what exactly I need to do and how to do it? I was hoping I could learn before the November update drops in (presumably) a few days or so. Help would be greatly appreciated.
it's pretty simple, restore images then perform OTA (don't restart) and install magisk to inactive slot.
for details check official Magisk Documentation (can't post link)
Long time rooter who has more or less given up in recent years.
Rooted:
HTC hero
HTC desire
Samsung Galaxy s1
Nexus 4
Nexus 5
Nexus 5x
Not rooted:
Pixel 2
Pixel 4xl
Just got a pixel 4 but would be tempted to root the pixel 2 while it's still got some life in it.
Got a few quick questions as to what has changed recently. Would be using magisk to achieve root after installing twrp. (Unless this is old hat and something else is the method of choice). Probably will have to unlock bootloader can't remember if I ever did it on the pixel 2
What's the procedure for monthly updates can they be done via ota or do I need to bring adb into it?
Best guides floating about at the moment? Any other pertinent advice? Muchthx
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
IMO the rooting party is pretty much over. I also returned to xda after many flashes years ago. For the Nexus, the great Beanstown dev provided monthly flashes for your custom recovery, but it looks so much more complicated today, to the point it's not worth the effort anymore. I'm sticking with stock till the '2 dies. The risk of unlocking the bootloader and getting root is simply not worth the headache as evident in the Q&A posts. So for now, for my much wanted rootness, I resort to debian linux on the desktop, a command line, and the luxury of typing sudo!!
sudoxd said:
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
Click to expand...
Click to collapse
Very impressive signature of the number of many devices you have. Maybe a new wall plaque perhaps?
I know I've had severe complications with updates on a rooted device in the past and I'm hoping to not brick my phone right now. It appears it's going to install when the device reboots whether I like it or not, and there's even a little thing that says reboot at 2:00am like it's going to do that on it's own if I don't manually do it.
open magisk and install magisk to inactive slot if loosing root is your problem.
Updates usually dont break your phone simply because your rooted.
Does the Magisk to inactive slot trick still work on the P7P?
finshan said:
I know I've had severe complications with updates on a rooted device in the past and I'm hoping to not brick my phone right now. It appears it's going to install when the device reboots whether I like it or not, and there's even a little thing that says reboot at 2:00am like it's going to do that on it's own if I don't manually do it.
Click to expand...
Click to collapse
The update will fail and won't be installed. What you need to do is:
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
It's also discussed here
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
finshan said:
I know I've had severe complications with updates on a rooted device in the past and I'm hoping to not brick my phone right now. It appears it's going to install when the device reboots whether I like it or not, and there's even a little thing that says reboot at 2:00am like it's going to do that on it's own if I don't manually do it.
Click to expand...
Click to collapse
Would suggest using Pixel Flasher to update. You can also keep root while updating using this tool.
Also, "Installing to Inactive Slot" via Magisk has been hit or miss. Has worked for some, not for others.
I don't think the OP is asking about how to update OTA nor how to keep root, I think OP is worried about the fact that, although rooted, the OTA has stated it has been downloaded and is going to be installed automatically at a specific time -- and how/if it has potential in resulting in a brick.
@finshan, it's been known to happen (on all versions of Pixels), and is NOT cause for concern. It may a be cause on other devices and/or at one point on smartphones or another, but is no longer the case -- at the very least from the Pixel 5 on, I can personally vouch. At best, it will error out because you are rooted and you might just have an annoying notification stating such. At worst, for whatever reason, some member's have woken up updated but without root/un-rooted. In the end, they just re-root and go about their day/night. I've never seen an instance of it being worse than that, but I imagine worst case scenario is a soft-brick bootloop, which can simply be fixed by re-flashing the factory firmware image...
In general the update process should fail due to the Magisk patched boot.img and the resulting invalid hash verification.
But the process could be stopped by
- deleting the data of the updater app
- rebooting into bootloader and use fastboot to switch the bootable slot to the non-updated one
Actually it's not required to interrupt the update. Just patch the new boot.img and everything is fine.
simplepinoi177 said:
I don't think the OP is asking about how to update OTA nor how to keep root, I think OP is worried about the fact that, although rooted, the OTA has stated it has been downloaded and is going to be installed automatically at a specific time -- and how/if it has potential in resulting in a brick.
Click to expand...
Click to collapse
OP also stated that they had "...severe complications with updates on a rooted device in the past...", so some of us were giving him options on how to update (while keeping root) without severe complications.
Lughnasadh said:
OP also stated that they had "...severe complications with updates on a rooted device in the past...", so some of us were giving him options on how to update (while keeping root) without severe complications.
Click to expand...
Click to collapse
True...I took his OP more on his concern on OTA updating on a rooted device and wanted to direct assurances to that; as, in his context, it was more a worry of that unintentionally having severe complications on a system processed OTA than "complications" when he attempted it himself...
that was just how I saw it...I'm sure all the information that you and all that have been given is helpful nonetheless...
Wow thank you all for the replies!
It didn't install at 2am, praise God.
@simplepinoi177 is correct that I was mainly interested in how to avoid the automatic reboot bricking my device. I disabled automatic reboots for updates in developer options and it hasn't rebooted. Then I rebooted on my own just to be sure it wouldn't try to sneak in the update—all clear. But now I get an obnoxious system notification from time to time (I can dismiss it) about how there's an update available.
So now onto actually dealing with the update.
Are you all suggesting that I don't have to disable magisk stuff? Just use some method to update and there will be zero complications? And afterwards, just patch the boot.img? I've rooted every pixel phone and I feel like when I did this one a few months ago it was more in depth...
Many ways to deal with this. Personally, I would download the factory image, extract the init_boot and root it. Then run flashall after removing the -w and flash patched init_boot I made. Might be more than most would do, but for me it is the most straight forward way to do it.
I mean... Pixel Flasher?
krakout said:
I mean... Pixel Flasher?
Click to expand...
Click to collapse
That works, too. I have no experience so I did not mention it. I did read the thread and it would do the job you want no problem.
finshan said:
Wow thank you all for the replies!
It didn't install at 2am, praise God.
@simplepinoi177 is correct that I was mainly interested in how to avoid the automatic reboot bricking my device. I disabled automatic reboots for updates in developer options and it hasn't rebooted. Then I rebooted on my own just to be sure it wouldn't try to sneak in the update—all clear. But now I get an obnoxious system notification from time to time (I can dismiss it) about how there's an update available.
So now onto actually dealing with the update.
Are you all suggesting that I don't have to disable magisk stuff? Just use some method to update and there will be zero complications? And afterwards, just patch the boot.img? I've rooted every pixel phone and I feel like when I did this one a few months ago it was more in depth...
Click to expand...
Click to collapse
Told you, you don't have much to be concerned about -- although I have seen some instances where, somehow, it actually did update (although rooted) and the member lost root; kinda crazy...
So you can update fairly easily, but no matter how you update, you will lose root -- but at least there will be zero complications in terms of bricking your device. It's as you say, you just have to patch the init_boot .img after. You had a couple of good suggested already in this thread (included in quotes below) in how to go about it. The most simplest straightforward way is badabing2003's PixelFlasher, but if you really want to understand the ins and outs, you should try going about it manually (as PixelFlasher does the same, just under a GUI with certain checks involved). But in using PixelFlasher, it's the easiest way to update *while keeping root (*it doesn't really retain root; more re-roots immediately after updating before loading the OS).
And if you do so wish, you can flash/install OTA's if you wish to update that way...
In all cases, it is safer to disable Magisk modules when updating, but not necessary in many/most cases, and even if it does result in bootloops, there are ways to correct it without being able to boot into the OS.
WoKoschekk said:
It's also discussed here
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Lughnasadh said:
Would suggest using Pixel Flasher to update. You can also keep root while updating using this tool.
Also, "Installing to Inactive Slot" via Magisk has been hit or miss. Has worked for some, not for others.
Click to expand...
Click to collapse
krakout said:
I mean... Pixel Flasher?
Click to expand...
Click to collapse
Happened to me as well. I was rooted and the OTA automatically downloaded. I pulled the trigger and installed. It went through with no issues but I obviously lost root lol