I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk
Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?
Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs
sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.
QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.
Related
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.
jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.
Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...
madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.
dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.
So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?
OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.
Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.
FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
UrAverageNerd said:
If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Hi there. I ran into similar problems when I was a Root noobie (which I still am). Try the All In One Tool that can be found in this forum. That will help you flash TWRP. It got me there when I was struggling to Flash TWRP.
redpoint73 said:
Haven't seen guacomoleb (different code name to me implies a different device, but I'm not sure in this case). Just use the file from the dev's TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Unofficial version -75 is the current version. Use the version ( Q versus Pie) for your current Android/OOS version. Might be obvious, but some folks have asked about that.
Per the developer in his thread I linked above, for a stock device, if you flash TWRP, you should root (with Magisk) or the phone might not boot. Some folks have reported that they can flash TWRP and not Magisk and still boot. But there is not point in risking it, since your intent is to root anyway. Fastboot boot TWRP img, then flash TWRP installer zip, and just flash Magisk right away at the same time, then reboot. It's pretty easy.
Also note that installing TWRP is somewhat optional. You can just fastboot boot TWRP img, then flash Magisk to root. It is a matter of preference whether to have TWRP installed or not, and folks are pretty split on this. My opinion, TWRP installed (while not required) does give some potentially useful features if things ever go wrong. I personally don't see much advantage to not installing TWRP, but just my opinion.
Click to expand...
Click to collapse
Thanks for your help. Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching. I like using TWRP because it's convenient if I wan't to flash something else without a PC or Mac.:laugh:
UrAverageNerd said:
Apparently the Android Q unofficial build -75 doesn't have any mirrors. It's still searching.
Click to expand...
Click to collapse
Something wrong with the "main" download link (androidfilehost)?
UrAverageNerd said:
Greetings to anyone that may see this - I am new to the android root thingy, so I apologize in advance if I have a stupid question. I have only rooted an old tablet with Kingoroot which used SuperSU as the root manager. First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.) I tried the regular guacamole image, but the phone didn't seem to want to boot the image. I am going to try guacamoleb. If I flash TWRP, can I boot my device normally? Some sources say yes some no. Thanks for all your help in advance!
Click to expand...
Click to collapse
Use adb & fastboot via powershell
Get the adb files in a folder
Copy the twrp.img to the adb folder and on phone /storage/emulated/0/
Get a copy of the twrp installer on your phone anywhere works
Open adb folder
Hold shift and right click a empty space
Open powershell & type
Adb boot bootloader
Fastboot boot twrp.img (you can drag and drop the file into powershell if your lazy like me)
Flash the twrp installer on your phone
Done?
Reboot and go back into recovery to see if it works
Tip for updates:
After you get the update
Flash via twrp
Then flash twrp (so you don't need your computer)
Flash magisk if you want superuser
Reboot
Reboot recovery
Flash magisk again (seems it takes two flashes)
None of the tools work for my devices anymore just powershell
All in one doesn't read my fastboot
Cmd has a remote error after attempting to boot it.
UrAverageNerd said:
First off, I want to address TWRP. What is the difference between the OP7Pro "guacamole" and "guacamoleb" (the "b" is very important and intentional.)
Click to expand...
Click to collapse
Just noticed that the TWRP "guacomoleb" is the "unified" version that works with both the OnePlus 7 and the 7 Pro. Shouldn't make a difference whether you use the "unified" version or the 7 Pro specific TWRP.