Related
So, basically ever since I've had my phone rooted and had ROM Manager on it, it has had trouble flashing Clockwork Recovery for me. I'll select for it to flash, it will appear to do so, but when I try to boot into recovery, either manually or from ROM Manager, it will just go to the default bootloader. When I attempt to choose Recovery from there, nothing will happen, and I'll have to reboot my phone and attempt to flash CWM again, and again, until it finally boots into it.
This always used to work after about 3 tries though, but now suddenly, it's just not even going anymore.
Is there anything I can do to make this process easier (or actually work)?
Set cwm to erase before flashing.
Sent from my Nexus S using xda premium
Or just use the fastboot command and flash recovery that way.
krohnjw said:
Set cwm to erase before flashing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just tried doing this, didn't work.
NYYFan325 said:
Or just use the fastboot command and flash recovery that way.
Click to expand...
Click to collapse
What command would that be? /noob
The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step
NYYFan325 said:
The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step
Click to expand...
Click to collapse
First off, sorry for taking so long to reply.
That was extremely noobish of me, I had completely forgotten about fastboot.
Turned out that solved it. I'm not sure what was going on, but all seems to be well now.
Thank you for your help!
use qbking77 guide in rooting ns/s 4g it is superb tutorial... go to youtube and type qbking77 ^_^
There was a file you have to delete. Look around Q&A, It's in there
Sent from my Nexus S 4G using XDA App
Ok so either delete these two files below or change the permissions so it has none (000)
"Install-recovery.sh" located in /system/etc
"Recovery-from-boot.sh" located in /system
I know this is not a new subject. but i feel i wont get a response in another thread that is pretty outdated. so im trying to flash cwm recovery thru fastboot but i get an error. I've tried typing the directory path c:\android-sdk\platform-tools\recovery.img. i get "cannot load recovery.img". this is what im typing
fastboot flash recovery c:\android-sdk\platform-tools\recovery.img
and i still get the error. I've even tried moving the recovery.img to c:\recovery.img
but no matter where or how i call it. it wont load. please help guys. I had android sdk install before but i had to wipe my pc clean and i just recieved a replacement nexus s 4g.
Have you tried navigating to the folder where recovery.img is located and typing "fastboot flash recovery recovery.img"
Sent from my Nexus S using XDA App
What do mean navigating? Typing the directory path?
Sent from my Nexus S 4G using Tapatalk
I think he means typing this first:
cd c:\android-sdk\platform-tools\
So how would I type this? I don't I am... please elaborate. Thank
Sent from my Nexus S 4G using Tapatalk
What operating system are you using? Windows?
Sent from my Nexus S using XDA App
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Harbb said:
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
wow. i did everything mentioned. i even redownloaded the recovery image. and i still get cannot load error. i even did it where i renamed it and left it alone the way it was typed
Is your bootloader unlocked? Also, fastboot devices shows a serial number right?
Harbb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
yup its unlocked.
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
let me give this a tried
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow this did it for me... i dont understand bc i typed
fastboot flash recovery rec(tab)
fastboot flash recovery recovery.img.img and i hit enter and it flashed. weird. but thanks dude i greatly appreciate it for sticking it out with me.
Wonderful. You probably have "hide file extensions for known file types" checked. So when you downloaded the original, it ACTUALLY had a .img on the end of it already (which windows hid from you). Windows, unlike unix, cannot differentiate files based on their header, but instead relies on a useless extension in the file name of all places (ie, .img, .mp3 and .jpg at the end of the filename).
And noo problem mate, happy to help.
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Techno Droid said:
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Click to expand...
Click to collapse
weird. i downloaded superuser from the their website and flashed. it didnt show. so i downloaded it from the market and tried running an app that requires su permission and it worked. am i missing something here? why did this work that way?
Flash this su.zip file. There was an older su version that automatically accepted any su access because it wasn't compatible with ICS yet.
thanks. it feels good to finally be rooted. i was stock for 2 days.. lol thanks
cannot load recovery.img
Thanks. the TAB autocomplete worked. I had forgotten about the additional file extension. gotta change that setting. Thanks again
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow, thanks man, you made my day, was about to throw the phone from anger. thanks a million man thank you.
I really don't know why and when, but i've upgrade my TWRP to the new one... and now when i enter in TWRP, they asking for a password... but i've NEVER set a password. I've try to downgrade to few older TWRP, the same password page again.
My bootloader is unlock, i'm on 4.2.1, but how to get rid of this freaking password in TWRP?
You're help is very needed
Rambytes said:
...they asking for a password... but i've NEVER set a password...
Click to expand...
Click to collapse
Mainly it happens when You go to TWRP after flashing it without reboot. Reboot should fix it, if not - reboot tablet after flashing TWRP.
Rambytes said:
I really don't know why and when, but i've upgrade my TWRP to the new one... and now when i enter in TWRP, they asking for a password... but i've NEVER set a password. I've try to downgrade to few older TWRP, the same password page again.
My bootloader is unlock, i'm on 4.2.1, but how to get rid of this freaking password in TWRP?
You're help is very needed
Click to expand...
Click to collapse
Happened to me when I flashed the wrong version of TWRP because I put it in the wrong spot.
cmendonc2 said:
Happened to me when I flashed the wrong version of TWRP because I put it in the wrong spot.
Click to expand...
Click to collapse
Ok and what the solution? Reboot after the flash of TWRP (in fastboot mode) don't solve the problem
Rambytes said:
Ok and what the solution? Reboot after the flash of TWRP (in fastboot mode) don't solve the problem
Click to expand...
Click to collapse
Well what had happened to me was I already had an old version of TWRP on my internal memory and I put the new version on my SD card which I wanted to flash. When I flashed twrp.blob, it flashed a very old version with an incompatible bootloader (whoops) which gave me the password error. So I put the new version on my internal memory, flashed twrp.blob again, and it worked.
cmendonc2 said:
Well what had happened to me was I already had an old version of TWRP on my internal memory and I put the new version on my SD card which I wanted to flash. When I flashed twrp.blob, it flashed a very old version with an incompatible bootloader (whoops) which gave me the password error. So I put the new version on my internal memory, flashed twrp.blob again, and it worked.
Click to expand...
Click to collapse
Ok, I can now booting in TWRP, but why they can't mount nothing????
Rambytes said:
Ok, I can now booting in TWRP, but why they can't mount nothing????
Click to expand...
Click to collapse
mount manually from TWRP settings, just mount what you need.
cmendonc2 said:
mount manually from TWRP settings, just mount what you need.
Click to expand...
Click to collapse
I've do something wrong again.... i'm stuck in the password section...
To trying to reset the password problem, i've flash the older blob i've found on TWRP, the 2.1.4. reboot the tablet, trying to enter in the RCK section, nothing append, like a freeze... so I reboot, flash the newer blob, the 2.6.3.0... reboot... enter in the RCK, and always the password...
i'm going crazy... i'm about to slam the tablet! :silly::crying:
Rambytes said:
I've do something wrong again.... i'm stuck in the password section...
To trying to reset the password problem, i've flash the older blob i've found on TWRP, the 2.1.4. reboot the tablet, trying to enter in the RCK section, nothing append, like a freeze... so I reboot, flash the newer blob, the 2.6.3.0... reboot... enter in the RCK, and always the password...
i'm going crazy... i'm about to slam the tablet! :silly::crying:
Click to expand...
Click to collapse
delete the 2.1.4 trwp from your tablet altogether
The do this exactly from fastboot:
Download the file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Click to expand...
Click to collapse
So put the 2.6 -42 TWRP in your fastboot folder, then run the command.
cmendonc2 said:
delete the 2.1.4 trwp from your tablet altogether
The do this exactly from fastboot:
So put the 2.6 -42 TWRP in your fastboot folder, then run the command.
Click to expand...
Click to collapse
2.6 -42 ?????
and I don't have the usb icon on the VOL- and POWER menu.... but at this screen, I can do fastboot command....
There is a way that can whe chat togheter live on facebook or wathever? Please don't stop to help me, it's very important... Never have problem with my N7 (2013) but this one TF300t is gouing very bad)
[solve] TWRP (wathever the version) ask a Password
ok, i will try to resart form the beginning.
The driver in windows is installed. When i'm on android, I can copy and see the tablet in the explorer. When i reboot the tablet in bootloader mode, again in windows I see a "android device in bootloader", Fastboot command work when I try fastboot -devices, I see the device.
I'm on 4.2.1 but I need to reflash and wipe all the data to install a better custom rom, I know TWRP because i'm using it on my N7...
It's after that... that going really bad for me and I don't know why.....
Can I try to flash with ClockwokMod instead TWRP? Wathever the recovery, I just want to flash a rom inside the TF300T...
Rambytes said:
ok, i will try to resart form the beginning.
The driver in windows is installed. When i'm on android, I can copy and see the tablet in the explorer. When i reboot the tablet in bootloader mode, again in windows I see a "android device in bootloader", Fastboot command work when I try fastboot -devices, I see the device.
It's after that... that going really bad for me and I don't know why.....
Click to expand...
Click to collapse
OK put the twrp 2.6.3.0 file in the folder platform-tools. Rename it to twrp.blob. Then run the command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
cmendonc2 said:
OK put the twrp 2.6.3.0 file in the folder platform-tools. Rename it to twrp.blob. Then run the command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Click to expand...
Click to collapse
Just to be sure, I take the JB version (because i'm on 4.2.1 right)?
OK... I've see my error..... I din't see there is a "special version" of TWRP, the 2.6.3.0 - 4.2......
Ho man... i feel like a big looser!!!!! Ho man very sorry...
Rambytes said:
OK... I've see my error..... I din't see there is a "special version" of TWRP, the 2.6.3.0 - 4.2......
Ho man... i feel like a big looser!!!!! Ho man very sorry...
Click to expand...
Click to collapse
yeah thats what i meant by -42 earlier
did that work?
cmendonc2 said:
yeah thats what i meant by -42 earlier
did that work?
Click to expand...
Click to collapse
yes!!! Working very good! Thanks!
Do you have a good custom rom to suggest? I'm download the CM10.2, but do you have another and/or better one?
Rambytes said:
yes!!! Working very good! Thanks!
Do you have a good custom rom to suggest? I'm download the CM10.2, but do you have another and/or better one?
Click to expand...
Click to collapse
I have a preference towards PAC-man since it combines the features of three of the most popular custom Roms
[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.
aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"
FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading
El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes
El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:
FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
EDIT: Solved it by using Fastboot and flashing the stock firmware without the -w so far everything is back to normal....know to get that dern kernel again
gears177 said:
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
Click to expand...
Click to collapse
First off, does fastboot recognize the device?
DuckRuckus said:
First off, does fastboot recognize the device?
Click to expand...
Click to collapse
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
gears177 said:
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
Click to expand...
Click to collapse
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
DuckRuckus said:
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
Click to expand...
Click to collapse
Ah nice didnt even realize its recognized under fastboot ive tried flashing the stock recovery but it just gives me an error
gears177 said:
Ah nice didnt even realize its recognized under fastboot
Click to expand...
Click to collapse
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
DuckRuckus said:
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
Click to expand...
Click to collapse
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Nevermind got it flag responsible for deleting userdata thanks alot for the help appreciate your time
gears177 said:
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Click to expand...
Click to collapse
It wipes all your data, that's why you remove it from the flash-all.bat script, unless you need to perform a full wipe. Telperion has an excellent guide for installing the lastest software, if you haven't already read it.
I've heard users having back luck flashing kernels in TWRP, as the kernel has something to do with recovery. I always use the method of booting the TWRP image in fastboot, use ADB to push the files to /tmp, and then do an ADB shell TWRP install of those files. TWRP, kernel, then magisk, in that order. I always reinstall all three, just to be on the safe side, and have never had any issues. Takes a little while, but not as long as redoing the whole freaking thing:silly:
Looks like you figured it out, before I finished my reply