Database Info

[Q] HELP Lost root and cannot get it back

Yesterday I rooted my nexus 5 following a guide from teamandroid website for android 4.4.2. Everything went okay and I was able to root it.
Then today I wanted to experiment with xposed framework but realized that I didn't have a recovery when I tried to make a backup. So first I tried installing TWRP through Goomanager but for some reason it would fail after the download. So I decided to install CWM touch trough fastboot. So I installed it and then did a backup. The problem came when I tried to exit. A message appeared and it said "ROM may flash stock recovery on boot. Fix?". I pressed yes, and then it told me something like "Root may have been lost. Try to get it back?" and pressed yes again. I rebooted and thats when supersu dissapear.
I panicked and tried to do the same procedure fro the guide again to get root. I repeated every single step but it wasn't succesful. I thought that maybe CWM was causing the problem so I installed TWRP trough fastboot and did the root process one more time. But again supersu just wouldn't appear back.
I really don't know what else to do. Everything in the stock ROM works fine but I just can't root my phone again. Does anyone know what I can do?
PS: Im not a native speaker.

just flash the latest supersu in your recovery, that is all. did you really search?

simms22 said:
just flash the latest supersu in your recovery, that is all. did you really search?
Click to expand...
Click to collapse
Thanks. It worked. I'm new to this so I wasn't sure what to do.

patrick.star said:
Thanks. It worked. I'm new to this so I wasn't sure what to do.
Click to expand...
Click to collapse
figured as much, rereading your post later, after first read. if you have any more questions, just ask.

Has anyone tried using latest flashfire to upgrade NOF26V?

will this keep the phone rooted like it does ever.
to flash the full image and root again is not very easy for me

It seems that no one is gonna take a try, I will and revert.

Just finished upgrading via flash fire. It worked

What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?

V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
sliding_billy said:
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
Click to expand...
Click to collapse

bush911 said:
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
Click to expand...
Click to collapse
Thanks for investigating. I would have thought you would flash the OTA. Doesn't seem to improve the process if recovery is removed but root isn't.

I did. Didn't work. Downloaded OTA. Flashfire kicked in (I'm using FlashFire Pro v0.55.1). It appeared to process the OTA. I flashed. OTA was not successful. I re-flashed SuperSU to restore root.

Flashfire works great
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.

I just retook the 7.1.2 OTA but did not restart after download. Opened FlashFire it autodetected the OTA, offered to install and I accepted. Everything went fine. Still have Su and on Sharkey kernal

josephpalozzi said:
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
Click to expand...
Click to collapse
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
edit: I was able to update to the Feb security patch, but lost twrp in the process. I tried the steps above again, this time I was presented with the ota available pop up screen which I didnt get the first time around. Even with the "preserve recovery" option ticked, it didnt preserve it. I get "no command" when I try to boot into recovery.

Just used TWRP sideload, TWRP IMG, TWRP install and SuperSU install to update XL to February. About to do Pixel. I've got FashFire installed and waiting until it is working in a more stable fashion. No point in fixing what ain't broke for me right now.

llong31 said:
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
Click to expand...
Click to collapse
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today

mac796 said:
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
Click to expand...
Click to collapse
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.

llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse

mac796 said:
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse

llong31 said:
mac796 said:
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
Maybe I'll try the auto detect see if that helps, in not sure if L speed does. I think most stuff for pixel is systemless
Click to expand...
Click to collapse

Sorry to bump this old thread...how long were ya'll phones 'black' during Flashfire? Mine has been black (but still connected to storage via PC so it's not dead) for like 25 min.
EDIT: After almost an hour, I gave up. I force rebooted the phone hoping Flashfire didn't do anything and it looks like it didn't. Phone booted fine. Going to use the old method and sideload the OTA.

I've used the OTA file from the typical update with FlashFire the past couple months, and I used a file downloaded from Google once before (I don't remember if it was on the phone or a flash drive). The screen didn't stay black very long the times I've used it, I'd guess less than a minute, so apparently something didn't work correctly. Looking through the app and documentation, I'm not sure what you meant by "still connected to storage via PC".

Most up to date rooting method for HTC A9?

Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!

Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?

txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..

JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?

I'm about to start the process trying to root using the above methods.. I'll post again when I have results.

txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.

JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?

txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done

txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.

JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23

txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.

Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..

Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.

TWRP Error "No Command" when i choose Recovery.

Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks

Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?

Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/

Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?

wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.

Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good

wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.

Installing OTA after TWRP + Magisk = fail to boot

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.