Related
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Ok, so I rooted my LGOG E970. I figured I better unlock it as well, so I used FreeGee and unlocked it. I tried to download CWM but it said it couldnt download file. So I thought I would reboot my phone. Now, all I get is the google logo, with the unlocked key underneath, and it then goes to the LG logo and back to Google and shuts off. I tried to hold down power and volume down, nothing, and power volume up nothing.:crying:
any ideas? Thanks in advance! I love this phone!
CJ
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
thanks, Just a little more help
aedren said:
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
Click to expand...
Click to collapse
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
ZombieGeek said:
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
Click to expand...
Click to collapse
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
bummer
aedren said:
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
Click to expand...
Click to collapse
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
ZombieGeek said:
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
Click to expand...
Click to collapse
Yeah, I got that too. I don't know if I got it fixed due to changing ROM, using the suggested recovery from the ROM, or if it was due to me restoring my EFS backup.
I flashed the TeamWin recovery found in the PSX instructions. Then I flashed PSX + Latest kernel + Banks Gapps + Banks Google Camera + AT&T NFC fix + SuperSU. I manually restored EFS from an ADB shell while in recovery.
When I booted I had: LTE works, Wifi works, NFC works, Camera works, ART works... The only things failing for me are the following:
Cell provider shows up as "Maritime" (display bug; as mentioned, LTE works fine and I'm on AT&T)
Settings > Developer Tools > Geeky Process Stats (does nothing)
Settings > Lockscreen > Slider Shortcuts (crashes as soon as I tap the middle ring)
LogCat is spammed with "QCOM PowerLock: Failed to acquire lock" whenever my finger is on the screen.
/system/xbin/mount --bind doesn't work (neither does mount -o bind). It gets sorta half-way-there, because the target directory can't be removed, but isn't bound properly it seems.
Other than that, it's been fast and smooth.
I just got the N9005 Note 3 clone and I believe that I have bricked it. I installed CWM using MTK Tools (or so I thought) and downloaded what I believed to be the correct recovery for the phone. Now when it boots, it will stay on for about 10 seconds and reboot and will continue to do so if I let it. When I try to boot the phone into recovery mode instead it goes to a screen that says,
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery. Mode]. <<==
[Fastboot. Mode]
[Normal. Mode]
I can use my volume up key but I can't select anything. No amount of pressing it, or holding it down, or pressing the other buttons selects either of them. I have to pull the battery to get the phone to do anything from there. Which leads me to believe that there was either an error in installing CWM, or it didn't install anything at all and corrupted something else pertinent to the Android system. It's almost as if Android recovery doesn't exist anymore like it was deleted. Is that even possible? I am at a total loss at what to do. Since I can't keep my phone booted for longer than 10 seconds at a time, I can't install CWM (again), which means that I can't factory reset my phone, install any kind of roms, wipe any kind of caches, nothing. Any help that you can provide I would be eternally grateful.
Sent from my SGH-T999 using xda app-developers app
Ok so after a couple of days of frustration and many hours of trial and error and lots of research done on many outlets of approach I found out that I can now boot the phone into fastboot. I booted the phone normally and in the 5-10 seconds that it does stay booted, PDAnet recognizes the phone and in a command prompt I very quickly typed 'adb reboot bootloader' and the phone reboots into fastboot. I immediately did research to find out what to do next. I tired a couple of things and so far I haven't had much success. I typed in my command prompt 'fastboot -w' and it says erasing 'userdata'... and after many minutes it says 'FAILED <status read failed <too many links>>.' Am I doing something wrong? My goal is to factory reset the phone back to the original boot image.
I'm pretty sure this all happened because I flashed the wrong recovery, when I try to boot into recovery (volume down+home button+power button) it brings me to a boot menu where I have 3 options to choose from, recovery, fastboot, and normal boot, none of which I can select. My best guess is that when I flashed the recovery the original recovery that came with the phone was deleted and it has corrupted something in the system which is causing the continuous reboots.
Upon further research I found a debrick image that is specific to my phone. Would that help? I'm going to try it and see what happens.
Sorry for the doosy here and all the questions but any help that anyone can provide would be very appreciated.
I have the same problem on my MTK6577 !
You have fixed your problem ?
Hello. Today i wanted to change my OS on my S3. So i have done it, i wanted to do some upgrades like viper4android. I have broken volume up, so the only way to get into recovery is in android only. So, I installed it, and i have bootloop. I cant boot to fastboot (volume up needed), and ofcourse recovery. I can see only bootloop... I just have to boot into recovery. How to do that? Help, please. Thanks.
Does adb recognize your device? If so
adb reboot recovery
If you don't have adb then go get them via Google
snkmv said:
Does adb recognize your device? If so
adb reboot recovery
If you don't have adb then go get them via Google
Click to expand...
Click to collapse
Well, i tried, but my phone isn't recognized on my pc. I just plug it into pc, and nothing. Tried on netbook, nothing . Dunno why. Its normal?
You have drivers installed?
I know this is an old thread, but I figured it'd be better to hijack it than create a new one.
A while back my phone started randomly freezing and rebooting, last week it just got into a bootloop instead, my volume up key isn't working, so I can't go into recovery-mode nor download-mode (since one has to press volume up to continue), I've tried to use adb, using a script to wait for a connection, then instantly freezing it so it can either send over a file or just boot into recovery, but it seems it doesn't boot up enough for a connection to start. I also tried removing my volume key and manually pressing the volume up key with both a toothpick and a screw-driver (just in case contact with metal would change the outcome), but didn't work. Has anyone found a solution?, Is there a way to boot into either recovery- or download-mode without the need to have the phone turned on first or using the volume up key?
Hi all. I just recently unlocked the bootloader and rooted my LG V30+ following the WTF guide with no issues. However, I installed a "Hide navigation bar" module in Magisk and now the screen is in accessible and I can only reboot the phone. Since I have TWRP installed, I cannot boot into bootloader holding down the volume down and power buttons. Any suggestions? I cannot use adb becuase it says that the device is unauthorized since I cannot allow permisions on my screen ( cant see anything on screen atm).
Blueoval24 said:
However, I installed a "Hide navigation bar" module in Magisk and now the screen is in accessible and I can only reboot the phone. Since I have TWRP installed, I cannot boot into bootloader holding down the volume down and power buttons. Any suggestions? I cannot use adb becuase it says that the device is unauthorized since I cannot allow permisions on my screen ( cant see anything on screen atm).
Click to expand...
Click to collapse
You can boot to TWRP with hardware button dance.
8 sec Power + Vol-, and when it shuts off, release both, immediatly press both again (at the same time), and as soon as the LG V30 logo appears, release power and press/hold it again.
Should get you to the factory reset menu, confirm twice with "yes" (navigate via vol/power buttons), and TWRP should boot fine.
Might take a few tries to get the right timing for that
Click to expand...
Click to collapse
For that, remember the annoying bootloader unlock warning is part of the boot sequence.
Or do a Master Reset and start over.
ChazzMatt said:
You can boot to TWRP with hardware button dance.
For that, remember the annoying bootloader unlock warning is part of the boot sequence.
Or do a Master Reset and start over.
Click to expand...
Click to collapse
So Ive been doing the awesome Hardware button dance but no success. What should I do when I get to the unlock warming menu?
Thanks!
EDIT: The post you link finally got me to boot in recovery. Thanks so much!!!
Cant believe it was that picky!
Blueoval24 said:
So Ive been doing the awesome Hardware button dance but no success. What should I do when I get to the unlock warming menu?
Thanks!
Click to expand...
Click to collapse
Ignore bootloader unlock warning. It's just part of the boot sequence. Maybe it's considered the "logo". Don't let it freak you out.
Sent via open market LG US998 V30/V30+
I must have done this button dance 25 times now, it just goes between unlocked boot warning screen and LG SlimQ screen, over & over again. Still no luck.
eff you LG...
christoophat said:
I must have done this button dance 25 times now, it just goes between unlocked boot warning screen and LG SlimQ screen, over & over again. Still no luck.
eff you LG...
Click to expand...
Click to collapse
Suggestion... Why not boot to TWRP with fastboot commands like in the WTF instructions? Then reboot to TWRP from within TWRP (reboot to recovery, from Recovery) to make sure you are then on your phone TWRP and not your PC TWRP.
Then after you root, use the recommended power menu app to never have to worry about it again.
If you already have root, then just go install that right now.
ADVANCED POWER MENU (root needed)
https://forum.xda-developers.com/showpost.php?p=79573776&postcount=2963
The person who started this thread couldn't do that because they installed something which messed up their screen. They couldn't see the Advanced Power Menu, nor see ADB/fastboot. So they HAD to use the hardware button dance...
Really no one else ever has to do that, except T-Mobile H932 users who don't have fastboot flash commands.
Hi Chazz, been unlocked and rooted with TWRP installed for months now. Wanted to just refresh us998 H, since something in Anxious mod may have been causing some issues. Wiped cache & dal, flashed the zip, flashed magisk 18.1, then rebooted to system. Magisk showing as not installed. Wanted to get back to recovery & reflash magisk....except now I can't for the life of me get back in there. New PC build here, nothing set up yet to be able to do fastboot stuff. Dang this is frustrating.
christoophat said:
Hi Chazz, been unlocked and rooted with TWRP installed for months now. Wanted to just refresh us998 H, since something in Anxious mod may have been causing some issues. Wiped cache & dal, flashed the zip, flashed magisk 18.1, then rebooted to system. Magisk showing as not installed. Wanted to get back to recovery & reflash magisk....except now I can't for the life of me get back in there. New PC build here, nothing set up yet to be able to do fastboot stuff. Dang this is frustrating.
Click to expand...
Click to collapse
In Oreo, did you enable USB debugging and then allow ADB from this PC? You have to install ABD drivers, LG drivers, fastboot drivers, and connect via good USB-C cable. If so go into ADB folder, hold-shift and right click to 'open command prompt here', and type "adb devices". If the PC recognizes your phone then it should say "adb xxxxxxxx authorized". Then type "adb reboot recovery" and it should boot into TWRP. If not then repeat everything and type "adb reboot bootloader" to go into fastboot or bootloader mode. In this mode you can type "fastboot flash recovery twrp.img" where the TWRP-xxx-xxxx.img has to be renamed into TWRP.img before hand (else you have to type the full TWRP file name. The TWRP file has to be in the same directory as the adb folder
I'm good turns out I ended up using my old PC, was able to adb recovery mode, installed 19.2 magisk over 18.1, which then showed up as being installed on the phone and root working. Guess I'll be keeping my old puter around for a while...lol