Develop Bugs

[FIXED][Q] Error sideloading OTA update 4.4 kitkat

So, i used wugfresh's app to sideload the update. Got a "set_metadata_recursive: some changes failed E: Error in /tmp/update.zip (status 7)" error
any ideas on why im getting this and how to fix the problem?

dalbig said:
So, i used wugfresh's app to sideload the update. Got a "set_metadata_recursive: some changes failed E: Error in /tmp/update.zip (status 7)" error
any ideas on why im getting this and how to fix the problem?
Click to expand...
Click to collapse
Better use CMD function from Wug's toolkit then adb sideload yourpathtoupdate.ziphere, i used it and wrked like a charm.

Spyr0s said:
Better use CMD function from Wug's toolkit then adb sideload yourpathtoupdate.ziphere, i used it and wrked like a charm.
Click to expand...
Click to collapse
what are the commands???

dalbig said:
what are the commands???
Click to expand...
Click to collapse
Boot to stock recovery, go to recovery menu (button combination can be tricky in fallen android), choose adb update with vol and power button then type in cmd window
adb sideload update.zip
where update.zip enter the full path to the file eg C:\User\Downloads\update.zip

ok got it but i got the same error... im fully stock but do you thing being rooted could cause this??

dalbig said:
ok got it but i got the same error... im fully stock but do you thing being rooted could cause this??
Click to expand...
Click to collapse
No, i was rooted when adb sideloaded the update. Maybe you have a bad download and need to redownload.

ok.. cool... but now im in a recovery bootloop too.
UPDATE: got myself out of the bootloop unrooted and started the process again. SUCCESS!!
i used this to get myself out of the bootloop: http://forum.xda-developers.com/showpost.php?p=45671279&postcount=3
copied the file to the image directory and clicked on the batch "nowipe" file

Do you guys know if the sideload method will work with the lte version?
Edit: Nevermind. There is no update zip for the lte version yet.

I get the same error on my N7 2012, how do you solve this without wipe?

snap
Deeco7 said:
I get the same error on my N7 2012, how do you solve this without wipe?
Click to expand...
Click to collapse
Also getting the same problem (N7 2012 WiFi, not rooted). factory reset didn't help.

Flashing the full OTA image using a modified (without the -w flashboot option) flash-all.bat worked for me!

Update to 4.4.2 solved
I updated to 4.4.2 with a Nexus 7 2012 from 4.3 via OTA. Then the devices did not start, keeps in boot logo. That's what I did:
(for mac)
Dowload the attached file android.zip
Unzip it in any folder you create
Type this in google "Factory Images for Nexus Devices" and download the image from your device
Uncompress the tgz files at the same folder as the fastboot file (from the zip which is attached here)
Turn of your device
Press Power button + volume up + volume down to enter to the fastboot menu
Connect your device to your computer (a mac in my case)
open a terminal
Type this:
./fastboot oem unlock
./fastboot erase boot
./fastboot erase cache
./fastboot erase recovery -> I got the clockwork mod recovery and this command deleted it and installed the android one. I think this command is not necessary
./fastboot erase system
./fastboot flash bootloader bootloader-grouper-4.23.img -> this gave me an error
./fastboot reboot-bootloader
./fastboot update yourimagefile.zip
Where yourimagefile.zip is the image which belongs to your device downloaded from the Factory Images for Nexus Devices webpage
Then the devices reboot twice and starts updating the Android System to 4.4.2
I assume that it will work with fastboot.exe file in windows
I hope it will help someone :good:

^This guy
Had to create an account to say thank you, rogerillu! I've been racking my brain over this for the past week. Your solution worked perfectly for me.

This thread *almost* fixed my similar issue, except my bootloader was outdated and there appear to be some issues with certain Nexus 7 bl updates. Coupled with this thread to get my bootloader sorted out, it appears I'm good to go.

[Q] need help unbricking nexus 7

okay, so i tried to return my rooted nexus 7 to stock using wugfresh toolkit. for some reson it failed when flashing to stock and locked the bootloader. now whenever i try to unlock the bootloader to flash stock manually i get this...
[email protected]:~$ fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (No such device))
finished. total time: 31.426s
[email protected]:~$ fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (No such device))
finished. total time: 121.599s
[email protected]:~$ fastboot oem unlock
Anyone have any suggestions? i have tried multiple usb cables and multiple computers. also it is not recognized by windows but fastboot is recognized in linux.

Get to a windows laptop. Boot to fastboot. Go into control panel, device manager, find the tablet connected to the computer. Download the latest Google USB drivers and unzip them. Right click the device in device manager, click update driver. Click find on my computer, and navigate to the folder with the drivers you unzipped. Click OK until they are installed.
Open cmd as admin. Try again.
If that doesn't work, do the same thing, but instead of have driver on my computer, select choose from a list of installed drivers, and choose Android ADB USB Interface. Click OK to the warning and install the driver. Open cmd as admin again and try it.
One of those should work. Had the same problem and that's how I fixed it.

SwoRNLeaDejZ said:
Get to a windows laptop. Boot to fastboot. Go into control panel, device manager, find the tablet connected to the computer. Download the latest Google USB drivers and unzip them. Right click the device in device manager, click update driver. Click find on my computer, and navigate to the folder with the drivers you unzipped. Click OK until they are installed.
Open cmd as admin. Try again.
If that doesn't work, do the same thing, but instead of have driver on my computer, select choose from a list of installed drivers, and choose Android ADB USB Interface. Click OK to the warning and install the driver. Open cmd as admin again and try it.
One of those should work. Had the same problem and that's how I fixed it.
Click to expand...
Click to collapse
problem in windows is fastboot devices doesnt show up my tablet in cmd, fastboot isnt even a command even though i have all the drivers and adb..

You need to open the command prompt window in the directory the fastboot files are in unless you set it up as a global variable. Hold shift and right click in the folder where the fastboot files are and select open command prompt here.

SwoRNLeaDejZ said:
You need to open the command prompt window in the directory the fastboot files are in unless you set it up as a global variable. Hold shift and right click in the folder where the fastboot files are and select open command prompt here.
Click to expand...
Click to collapse
yea i got it to work but its still stuck on erasing user data

Is anything happening on the tablet?

SwoRNLeaDejZ said:
Is anything happening on the tablet?
Click to expand...
Click to collapse
its just still at the unlock bootloader screen

Did you press the button to select yes? Sometimes, you have to really mash the thing to get it to register.

yea..its been erasing user data for 45 mins in cmd and still on unlock bootloader

well after all the waiting it failed again..it said FAILED <status read failed <too many links>>

You are not alone. Many users including me having same problem. Can't unlock bootloader. No one has fix for it yet.

This is why I don't use toolkits and never recommend them either.

nhizzat said:
This is why I don't use toolkits and never recommend them either.
Click to expand...
Click to collapse
All toolkits do is send terminal commands to automate a process. They are perfectly safe to use and can often save time and headaches.

I'm in the same situation as others here and created a post on the Google help forum because I've not seen Google respond to this issue.
https://productforums.google.com/forum/m/#!category-topic/nexus/nexus-7/lJxoEm1LvMg

Oneplus 3 Boot Loop

So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1

If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY

anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"

revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.

anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now

Errr... fastboot can unlock the bootloader. fastboot oem unlock

emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.

never ever relock your bootloader while you in custom OS

oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me

revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.

Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.

Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.

emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.

anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works

U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post

^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).

Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.

rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?

revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.

ADB does not see device in bootloader

I have the driver installed and see it in my device manager, but adb does not see it.
Any suggestions?

gatortuba said:
I have the driver installed and see it in my device manager, but adb does not see it.
Any suggestions?
Click to expand...
Click to collapse
Update your SDK, try a different cable, for starters.

Badger50 said:
Update your SDK, try a different cable, for starters.
Click to expand...
Click to collapse
It sees it when the device booted up.
How would the cable make a difference?

gatortuba said:
It sees it when the device booted up.
How would the cable make a difference?
Click to expand...
Click to collapse
Outa curiosity, when the phone is on in normal mode, I assume you have USB debugging on correct? If you go to your sdk platform tools, and open a command prompt, and type abd devices, do you get your phone ID to display? As far as the cable, there have been many many reports that trying a different one fixed the problem.

What are you trying to do? ADB won't work when booted at the bootloader, Fastboot will. If you type:
Code:
fastboot devices
Does your computer report back what it sees now?

RMarkwald said:
What are you trying to do? ADB won't work when booted at the bootloader, Fastboot will. If you type:
Code:
fastboot devices
Does your computer report back what it sees now?
Click to expand...
Click to collapse
That seem to work, 711KPNY0535039 fastboot
How do I flash magisk from there or twrp?
TWR gives me the error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic

gatortuba said:
That seem to work, 711KPNY0535039 fastboot
How do I flash magisk from there or twrp?
TWR gives me the error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic
Click to expand...
Click to collapse
I don't know.
Have you tried the instructions for it from this thread?

ADB only works while the device is booted & in recovery.
FASTBOOT is what you'll need while in the bootloader.
If you want to have root with Magisk go to their thread, https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176, and follow the detailed instructions the OP has provided. If you don't feel comfortable or confident you can follow them... root probably isn't for you.

EvilDobe said:
ADB only works while the device is booted & in recovery.
FASTBOOT is what you'll need while in the bootloader.
If you want to have root with Magisk go to their thread, https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176, and follow the detailed instructions the OP has provided. If you don't feel comfortable or confident you can follow them... root probably isn't for you.
Click to expand...
Click to collapse
Thanks for all of the help. Got Magisk installed and tethering works

EvilDobe said:
ADB only works while the device is booted & in recovery.
FASTBOOT is what you'll need while in the bootloader.
Click to expand...
Click to collapse
Thank you for this.

EvilDobe said:
ADB only works while the device is booted & in recovery.
Click to expand...
Click to collapse
It also works while booted to OS/ system

Update magisk failed, now can't boot anymore

Hey guys I have an unlocked google pixel 2 XL running TWRP 3.3.0.0, Resurection Remix V7.0.2. and for root I was using Magisk.
I updated Magisk using the recommended installation method. The installation failed, I don't fully remember the error, but it was something along the lines, "partition not found" . After that the magisk updater recommended that I reboot. I did so but now there is the error message "Your device is corrupt. It can't be trusted and may not work properly. Visit link on another device: g.co/ABH ". You can skip the message by hitting the power button. After that You get the normal unlock warning and then the phone got stuck in the google boot screen.
After that I tried entering the recovery but that also didn't work. The phone got stuck on the TWRP boot screen.
So next I tried to reflash the recovery but I got the following error:
Sending 'recovery' (40960 KB) OKAY [ 0.975s]
Writing 'recovery' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.

schpongo said:
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.
Click to expand...
Click to collapse
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.

Badger50 said:
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.
Click to expand...
Click to collapse
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
If you can get into twrp, which you stated you can't, it might work. However, I would first flash the magisk uninstaller zip if you can get into TWRP. If none of that works, then you'll have to fastboot the factory image without the -w so as to not wipe data. You may also try flashing the stock boot.img to see if it'll boot up as well before having to get too drastic with anything else :good:

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.

schpongo said:
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.
Click to expand...
Click to collapse
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?

Badger50 said:
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?
Click to expand...
Click to collapse
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?

schpongo said:
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?
Click to expand...
Click to collapse
USB-C to USB-C have been notorious for being rather "finicky" and not necessarily working in all cases. What does is USB-A to USB-C cables/cords -- seem to work in all cases.
I'm unsure as to why your data is not showing; whether it's not decrypting or not reading it... question;did you employ a screenlock/fingerprint lock before while the device was working? Because if you did, and it’s not asking for it to “decrypt”, then something more critical is going on and not being able to read your /data and/or /system
In any case, the main reason I wanted to chime in was to bring up something that you might be aware of already, but I wanted to confirm; when using Linux or macOS, you address the flash-all.sh file, and not attempt to launch the “flash-all.bat”.
However, it’s best if you could start from step 1 and download/re-download the Full Factory image, extract the .zip so it shows the 6 files within. Then, at this point and to make sure to cause no further issues, you should get rid of the flash-all.bat file – therefore only keeping the flash-all.sh and the flash-base.sh. Also, to retain any data, supposedly you would remove the “-w” from flash-all, but that’s how it goes for Windows and the flash-all.bat batch file; I’m unsure how to go about the same for Mac or Linux. After making sure you have the 5 correct files, move them on over to the platform-tools folder that contain the adb & fastboot .exe files – also, this would be a good time to make sure you have the most up-to-date platform-tools because, more often than not, not having the most up to date version is what usually causes most hiccups; latest version is “r29.0.5-darwin”.
And, after all of that, if you are still having issues, if you could post your output logs (if you remove the “exit” from the flash-all.bat file, it would keep the output window, but then again, that’s how to to it in a Windows environment…), it would be most helpful as to figuring out where/how things are going wrong. Usually/most likely it’s either platform-tools aren’t up-to-date or using different cords and/or on a different computer seems to be the resolutions at that point.
Hopefully this ends up being helpful…good luck!

Don't try to install twrp. Fastboot boot it