what's up, oneplus peeps?
it used to be so easy to root a oneplus device.
but now, there are so many versions of the stock rom. and no one bootimage to rule them all. no stock firmware and modem to define the device to be recognized by a customized rom.
so it becomes so scary to go down the rabit hole now.
should i take the blue pill or the red pill?
but i should take the red pill. otherwise life will be so boring just like an iPhone 12.
finally, what made a oneplus device attractive, such as my beloved Oneplus 3t, was that it was definitely a flagship killer at that time. and it was so easy to root. and this was also what made Oneplus so attractive especially to those who just wanted a rooted phone and be able to play with different ups that required a rooted device.
jmadiaga said:
what's up, oneplus peeps?
it used to be so easy to root a oneplus device.
but now, there are so many versions of the stock rom. and no one bootimage to rule them all. no stock firmware and modem to define the device to be recognized by a customized rom.
so it becomes so scary to go down the rabit hole now.
should i take the blue pill or the red pill?
but i should take the red pill. otherwise life will be so boring just like an iPhone 12.
finally, what made a oneplus device attractive, such as my beloved Oneplus 3t, was that it was definitely a flagship killer at that time. and it was so easy to root. and this was also what made Oneplus so attractive especially to those who just wanted a rooted phone and be able to play with different ups that required a rooted device.
Click to expand...
Click to collapse
and now it is aalaready March, and yet there is still no OTA update even just toupdate the security patch which is still Nov.2021.
so disappointing.
jmadiaga said:
and now it is aalaready March, and yet there is still no OTA update even just toupdate the security patch which is still Nov.2021.
so disappointing.
Click to expand...
Click to collapse
OxygenOS 12 Skin: OnePlus Confirms the device list for Android 12
OnePlus already released Beta program of Android 13 for OnePlus 10 Pro users. But stil some OnePlus user waiting for Android 12 based OxygenOS 12 update. Last year, OnePlus launched Android 12-based OxygenOS 12 skin in the global market. If you own a OnePlus smartphone, you probably bought it...
www.rmupdate.com
Seems like some of it is from Android and Qualcomm. Just look at the file size , froyo was around 100mb roughly now it's 1gb or more.
OnePlus is lazy to keep their phones up-to-date, but that another story. If you like to keep patched monthly, goes to Samsung flagships.
Ranting about root hard eh? Root is still easy, only few extra steps are needed now. You're just being lazy to follow instruction. Android becomes more, and more secure OS, you can't compare old op3t released with A6 with latest phone released with A11/A12, there's many changes since A6 was released.
op9 is A/B device, unlock bootloader, boot twrp image (NOT flash), flash twrp from inside twrp, then root with Magisk. If you change kernel, you need to flash magisk again. That's it, it's still simple.
x3r0.13urn said:
OnePlus is lazy to keep their phones up-to-date, but that another story. If you like to keep patched monthly, goes to Samsung flagships.
Ranting about root hard eh? Root is still easy, only few extra steps are needed now. You're just being lazy to follow instruction. Android becomes more, and more secure OS, you can't compare old op3t released with A6 with latest phone released with A11/A12, there's many changes since A6 was released.
op9 is A/B device, unlock bootloader, boot twrp image (NOT flash), flash twrp from inside twrp, then root with Magisk. If you change kernel, you need to flash magisk again. That's it, it's still simple.
Click to expand...
Click to collapse
Hi! it was a rant, indeed. and how to do "boot twrp image (NOT flash). and i really can't find any OP9 bootloader.img file and also the firmware for the OP9 (IND).
the stock OS is just so bloated for me.
TIA
This is the easiest phone to root in the world man.
Related
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?
After riding the HTC and Samsung wagons for quite a while, I have purchased the Oneplus
I have been browsing around the other threads for the 7 and 8 models and it looks like OnePlus typically releases the firmware and/or recoveries right away when a new model is launched. Does anyone know if this will be the case for the 8t?
I want to get root out of the way before setting up the new device when it arrives, so I was hoping a dev already has the boot img uploaded somewhere or it was coming soon.
Does anyone care to elaborate on what expectations should be for this type of stuff?
Thanks in advance!
MNoisy said:
After riding the HTC and Samsung wagons for quite a while, I have purchased the Oneplus
I have been browsing around the other threads for the 7 and 8 models and it looks like OnePlus typically releases the firmware and/or recoveries right away when a new model is launched. Does anyone know if this will be the case for the 8t?
I want to get root out of the way before setting up the new device when it arrives, so I was hoping a dev already has the boot img uploaded somewhere or it was coming soon.
Does anyone care to elaborate on what expectations should be for this type of stuff?
Thanks in advance!
Click to expand...
Click to collapse
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Superguy said:
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Click to expand...
Click to collapse
There is no need to add the useless commentary. I appreciate your reply but I wasn't asking for timelines from a dev or some modification to be done. I wanted to gauge the typical expectations of people have who are current OnePlus users for things like firmware, updates, etc.
For example, HTC is terrible at getting out new updates and has not provided timelines or expectations for firmware updates in like the last year + for their last two flagship models. Samsung is very consistent with software releases and public schedule announcements. These are important to a lot of users and it was tough to determine this when reading the other forums for other OnePlus devices.
Past availability is frankly the only way to estimate when things like this might be available to us. Most companies don't change the way they do everything just because there is a new product being released. If you want to help with that information instead of being negative, I welcome your assistance!
There is typically a monthly update in firmware, with possibly more frequent ones in the beginning if there are issues.
I wouldn't necessarily expect root for at least a week or 2 on any new phone, especially with a new OS.
Superguy said:
There is typically a monthly update in firmware, with possibly more frequent ones in the beginning if there are issues.
I wouldn't necessarily expect root for at least a week or 2 on any new phone, especially with a new OS.
Click to expand...
Click to collapse
Thank you! Good info!
OnePlus phones can be rooted as soon as you have the bootloader unlocked, and you have either TWRP booting (data decryption does not need to work), or stock recovery patched to accept ADB commands.
Once you can pull the stock kernel, you can patch it with Magisk, boot off it in fastboot, then direct install through Magisk inside the OS.
NotATreoFan said:
OnePlus phones can be rooted as soon as you have the bootloader unlocked, and you have either TWRP booting (data decryption does not need to work), or stock recovery patched to accept ADB commands.
Once you can pull the stock kernel, you can patch it with Magisk, boot off it in fastboot, then direct install through Magisk inside the OS.
Click to expand...
Click to collapse
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for Oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick? It has been a while since I had to root and I honestly forget if it is the root or unlocking the bootloader which wipes the device, but I at least hoped to get that done before setting up the device.
MNoisy said:
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick?
Click to expand...
Click to collapse
I don't know what version is out there right now. My OP8T doesn't come until tomorrow, and I will be at least 40 days out from rooting since T-Mobile won't SIM unlock (generally) until that time, and you need to be SIM unlocked in order to unlock the bootloader.
Superguy said:
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Click to expand...
Click to collapse
What is wrong with you? Why are you being so toxic to someone asking a simple question?
Thanat0s24 said:
What is wrong with you? Why are you being so toxic to someone asking a simple question?
Click to expand...
Click to collapse
Actually, he's not toxic. He's just said the truth.
No sign of stock firmware zips yet, but I'd expect the MSM unbrick tools to be readily available this week.
MNoisy said:
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for Oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick? It has been a while since I had to root and I honestly forget if it is the root or unlocking the bootloader which wipes the device, but I at least hoped to get that done before setting up the device.
Click to expand...
Click to collapse
Just to follow up on this so others can avoid it, flashing TWRP does not work. Neither the TWRP vanilla edition nor the isntantnoodle edition worked and went straight to Qualcomm Crashdump mode in both.
I guess it is now a wait for the OTA to download
Hello everyone! I just bought an Amazon renewed Op 9, and I wanted to ask How to install Evolution X or Lineage OS, since maybe the instructions are different from the global Version and T Mobile version Add more step to installation or simply can not be achieved
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!
posar said:
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!
Click to expand...
Click to collapse
Its neccesary the root for the steps?
Yasser.d said:
Its neccesary the root for the steps?
Click to expand...
Click to collapse
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.
posar said:
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.
Click to expand...
Click to collapse
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc
Yasser.d said:
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc
Click to expand...
Click to collapse
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).
posar said:
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).
Click to expand...
Click to collapse
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms
Yasser.d said:
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms
Click to expand...
Click to collapse
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.
posar said:
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.
Click to expand...
Click to collapse
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass
after that fix dual sim is working?
Yasser.d said:
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass
Click to expand...
Click to collapse
I haven't heard this, but I haven't really been keeping track. I guess I'll find out.
gioodo said:
after that fix dual sim is working?
Click to expand...
Click to collapse
To my knowledge dual sim can't work on the T-Mobile OnePlus 9. It doesn't even have a dual sim tray.
Hello, newbie here. I bought a google pixel 6a earlier today for experimenting with custom roms. After unboxing it found that it shipped with android 13. I saw the anti rollback warning here and i wonder what i should do.
Shoudl i try and return it or can i save it in a way? I havent connected it to the internet at all or anything like that. It's almost exactly as it was shipped. Any advice? Thanks.
Edit:
Okay i am totally new to this and maybe the warning doesn't mean what i think it does. Does it just mean that theres an increased risk of bricking a device or that after android 13 custom Roms wont work?
I forget the exact technical details, but it only means that you can't go back to Android 12 (because hackers rollback to A12 to exploit a vulnerability/bug that they fixed in A13). That being said, Google did release a way to rollback though I don't know much about it (never tried it).
I don't think you need to return the phone. I've never had to rollback to A12. It's already been like 8 months that A13 was released. I'm happy with A13 and the 6a.
Just enjoy your device, mate.
There's an increased risk for bricking your device if you're new to this and don't double check everything you do. Be sure to ask (always Google first tho, haha) if you're not certain about something you're about to do.
Sending your device back and buying a new one is not really a solution imo, likely all devices are going to come with A13 out of the box. FWIW, I was already on A13 when I was able to unlock my bootloader and switch to custom ROMs.
if he wants to root his device he can't enjoy it. because there is no root for 13 yet and you can't roll back to 12 because of a "efuse" that blows when 13 is installed.
Lada333 said:
Just enjoy your device, mate.
There's an increased risk for bricking your device if you're new to this and don't double check everything you do. Be sure to ask (always Google first tho, haha) if you're not certain about something you're about to do.
Sending your device back and buying a new one is not really a solution imo, likely all devices are going to come with A13 out of the box. FWIW, I was already on A13 when I was able to unlock my bootloader and switch to custom ROMs.
Click to expand...
Click to collapse
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.
Alldayismokebomb said:
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.
Click to expand...
Click to collapse
Not sure what you mean by "no root for Android 13"... Yes you can get get root access on Android 13 using Magisk, and yes it has been available since the launch of Android 13.
Alldayismokebomb said:
there is no root for 13 or I would have upgraded. I take that back there is but all the roms have stuff that does not work on them . like revanced or other things.
Click to expand...
Click to collapse
Rooting A13 has been available without any issues for many many months now.
What do you mean by things not working on all A13 ROMs? What things? ReVanced works flawlessly for me, running crDroid A13.
Alldayismokebomb said:
if he wants to root his device he can't enjoy it. because there is no root for 13 yet and you can't roll back to 12 because of a "efuse" that blows when 13 is installed.
Click to expand...
Click to collapse
I rooted my Pixel 6a with A13 a month ago using guide from here. Also tried GrapheneOS for a bit. Had zero issues.
The guide for LineageOS tells you to upgrade to Android 13 before installing it anyway.
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