Post OTA Update Root Recovery - Google Pixel 2 XL Guides, News, & Discussion

Hey everyone. I have a 2XL that was rooted with version 10. I accidentally DL'd the latest ota and recently had to reboot so it updated and took root away. How do I get root back without losing data? Thanks in advance.

So, I tried running steps from the standard root process and nothing worked. Still no root.
Im trying to use the Magisk/TWRP method. I installed the factory image (not OTA) and that went fine. Booted up perfect and no loss of data. When I tried to install twrp and magisk, I got errors. Is there a different process for android 11? Thanks.

carbon coupe said:
So, I tried running steps from the standard root process and nothing worked. Still no root.
Im trying to use the Magisk/TWRP method. I installed the factory image (not OTA) and that went fine. Booted up perfect and no loss of data. When I tried to install twrp and magisk, I got errors. Is there a different process for android 11? Thanks.
Click to expand...
Click to collapse
There is a conflict when you "install" TWRP and Magisk together. Instead of installing TWRP you should boot it up via fastboot which will temporarily allow you to flash Magisk (fastboot boot<twrpxxx.img name> ).
You can also just patch the boot image with Magisk and forego TWRP altogether.

Ok, so should I reflash the factory image first or just fastboot twrp and install Magisk?

carbon coupe said:
Ok, so should I reflash the factory image first or just fastboot twrp and install Magisk?
Click to expand...
Click to collapse
If neither TWRP or Magisk is currently installed, then just fastboot TWRP and install Magisk.

Related

TWRP bootloop after flashing TWRP Solved

Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.

No OS installed. TWRP cannot flash new custom ROM

Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.
Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works
First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.
Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!
Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!
no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*

How can I remove Magisk?

I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update

Re-Rooting 1+5 after OS 5.1.1 Update

So I tried updating to Oxygen is 5.0 ran into an install issue, stuck in boot loop. Lucky I had done a Nandroid back up and restore everything. The other night I decided to update to 5.1.1 thinking why not get Android 8.1.0 on my AWESOME phone. Downloaded update, placed in internal storage, booted into TWRP to do a Nandroid back up (due to issues with past update). Back up failed needed to clean drive. So I decided, phone works in Android 7.1.1, why can't what's not broken. Rebooted phone and somehow the update activated. I freaked since last time it failed and not stuck in a loop. This time update was successful but still got stuck in a boot loop. I plugged my phone to my computer and noticed all my files were gone on their install storage, no files / foldersI recognized (e.g. DCIM, DATA, DOWNLOAD, etc). Emailed One Plus and chatted with them. TWRP was gone and was back on stock recovery. Since all was lost I was asked to "Erase All". I did, rebooted and I'm now on 8.1.1 but all my stuff was lost. So I've done since searching and found FlashFire do to a Nandroid backup but need root. So my question is...
Can I re-root my phone without using TWRP but stock recovery and use FlashFire for my back ups? I am not going to flash custom ROM but if I need to flash something, wouldn't stock ROM flash anything on my phone (Magisk)?
If so, can anyone provide me with assistance on re-rooting my phone without TWRP.
Thank you
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Hi
To root your OnePlus 5, you must to follow carefuly the steps below and take your time.
1 - Make a full backup of your data
2 - Unlock the bootloader (Note that'll erase your phone)
3 - Install another recovery : TWRP. This one : https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download
4 - Flash the full rom Oxygen OS 5.1.1 : http://otafsg.h2os.com/patch/amazon...23_OTA_034_all_1804201219_3824995916a49ee.zip
5 - Install magisk : https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
6 - Clear cache / Dalvik
7 - You're all done, reboot the phone
8 - Once your phone has booted up, install magisk manager : https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Check this tread, that'll help you as well : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
vanzant83 said:
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Click to expand...
Click to collapse
Hello, thanks for the info and yes, I did try flashing Magisk with stock recovery, while waiting for a reply and can confirm installation failed. So if I reflash TWRP, flashing Magisk using TWRP will work. Therefore, do you have instructions (step-by-step) on how to install TWRP. I have downloaded the latest TWRP image from their website (twrp-3.1.1-1 cheeseburger) onto my desktop. Bootloader is already unlocked as I was previously rooted under Android 7.1.
Thank you.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
vanzant83 said:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
Click to expand...
Click to collapse
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
jmoricone said:
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
Click to expand...
Click to collapse
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Try this link, get the ZIP file from the version you want: https://github.com/topjohnwu/Magisk/releases/
In case you need, this the official section: https://forum.xda-developers.com/apps/magisk
vanzant83 said:
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Click to expand...
Click to collapse
Hey there, sorry for the late response..but thank you for the assist..phone is rerooted..all is good..thanks again

Android 10 and root?

I'm on Android 10. I unlocked the bootloader.. easy.. I downloaded the corresponding file for my device, software channel, version. Ran the boot img through magisk manager. So I have the patched boot img. Before I go further with trying to flash it through fastboot, I was wondering would this successfully root my device? I'm hesitant because I haven't came across anyone discussing there success in doing this with Android 10. I really don't want to proceed until I know I'm ok to go ahead. Thoughts?
Install Twrp, flash Magisk latest zip through twrp, done
HueyT said:
Install Twrp, flash Magisk latest zip through twrp, done
Click to expand...
Click to collapse
Sorry to butt in but that did not work for me. Rooting with magisk removed my installed twrp. Could that be a bug in android 10 or latest magisk?
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
HueyT said:
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
Click to expand...
Click to collapse
I was busy with other things and only just came back to this topic. I agree with you, HueyT, Magisk rooting
(which I do according to the Magisk directions which say to patch the boot.img and then flash it)
should not remove the permanent twrp installation on my phone. But it does
remove it on my phone! I've tried it repeatedly.
What I end up with is a rooted Moto G7 running android 10 and when I :
—power off completely
—volume down + power takes me to the stock recovery (not twrp)
—in that stock recovery if I go to the 'recovery' option I get the open android with red exclamation mark. Happens every time.
—long power hold then reboots phone to rooted android 10.
What I have not tried yet is to permanently install twrp again and then, in twrp install Magisk 23 zip. Maybe that will allow me to keep twrp installed.
Do you think so?
It is just frustrating because this is my main phone and I can't afford to mess it up.
Any other suggestions on how to keep twrp installed on the Magisk rooted phone greatly appreciated.
Thanks for replying.
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
A man of few words...
Yep
maybeme2 said:
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Click to expand...
Click to collapse
That worked.
Rooting by installing Magisk.zip from within TWRP allowed me to both root and retain the TWRP installation.
Thank you HueyT.
NP
It's been two years but I did try injecting Magisk from within TWRP. I've also downloaded "factory" images and rooted those, them installed them. If I remember right, I did the injection method with this G7. It's the best way IMHO because the installed image is tailored your your device.
Over the last two years, the Pie around here has been fantastic.
shadow460 said:
Over the last two years, the Pie around here has been fantastic.
Click to expand...
Click to collapse
You can say that again. I've had several system crashes with 10, something I've never had with pie. Even after clearing cache, updating all apps, etc. So has my wife on her own unrooted G7 which just accepted Moto's own ota update to 10.
I do have a TWRP nandroid backup that I did just before flashing 10 and I've often considered going back to pie. But I worry about 'something' else going wrong like it did when moving to 10. It's my main phone and I can't afford to go through all I went through moving to a rooted 10. Wish I hadn't bothered.

Categories

Resources