Database Users

Another Can't boot after unlock and twrp install

I'll try to make this brief and to the point as I realize how many people come here seeking help.
I've rooted many android devices (my first was an htc incredible) so I'm not exactly "new" per say, but don't really fully understand what I'm doing either long story short.
Got my nexus 7 today, tested some things with the screen when I first got it (just playing videos to see how bright it is)
I Followed a video suggested (somewhere) on the forums (video here (but I can't post urls))
-Sat down, got the usb drivers from here - Can't post link
-got adb fast boot tools - can't post link
-Downloaded SuperSU
-Enabled usb debugging in settings
-Booted into recovery
-Updated Driver when prompted
-allowed usb debugging after entering adb devices command
-used adb reboot bootloader command
-used fastboot oem unlock command (worked succesfully)
-used flash recovery openrecovery-twrp-2.6.0.0-flo (personally I think it didn't flash correctly because I don't know how to explain issues I will detail below
- (unless this is where I went wrong) rebooted to get into os so I could place supersu.zip on internal storage for rooting
- sticks at glowing X
ADB won't recognize the nexus 7 in recovery or bootloader
Windows only sees the nexus 7 as either
QHSUSB_DLOAD
MTP USB Device
flo
I've tried wiping from recovery, it fails.
I DO seem to be able to get adb to recognize the tablet when it is in recovery mode now.
Adb lists
06d9e78e Recovery
I've tried reflashing Twrp, still can't wipe, Is it possible for me to just install kitkat from recovry straight from adb or fastboot? It's been a while but I was thinking if I could just reset the os it might work. I have razor-krt16s-factory-7235eb0d.tgz ready to go I just don't know how to put it on the tablet without an sd card to transfer with
I have also installed Wugs Nexus Root Kit but since I have no idea what build of 4.3 my n7 is running...it really isn't doing me any good -_-.
any help would be appreciated, I'm stumped but will be continuing to dig for answers.
Thanks

HP slate 7 extreme a plain tegra note?

Just wondering if anybody's tried to flash tn7 ROMs on their s7e? And does the s7e read the same model number as the tegra note? P1640?
Sent from my SGH-I317 using xda app-developers app

I've been stuck trying to figure out how to adb on my slate 7 extreme for weeks. Tried every driver and every cord and port. So while I'd love to confirm that it is the same... I'm still not sure.

Same here looking for a root
Sent from my HP Slate7 Extreme using xda app-developers app

I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?

skysoblue said:
cool. What do you mean by locking up a lot? it often hang and jam? . So i guess, staying at 4.2.2 is the best for now?
Click to expand...
Click to collapse
It will work fine for up to about 10 minutes, then the screen will freeze and the only way to get it back is to hold the power down for 10 seconds and reboot it.
I am back on 4.2.2 right now, but when I have some extra time I might try a few things.

Mobilla said:
I was able to root it after some playing around,
you need to use the universal naked drivers (Nvidia Shield) for both adb and fastboot.
To unlock you have to specifiy the vendorid to fastboot:
fastboot -i 0x03F0 oem unlock
The util in the TN7 dev forum will not work out of the box for the S7E because it doesn't specify the vendor id to fastboot, but the supplied files will work (you can modify the .bat if you want to add the "-i 0x03F0" to fastboot). You can boot CWM to install root.
Installing the 4.4.2 system and boot partitions works and it will boot, however i am having trouble with it locking up a lot.
Click to expand...
Click to collapse
Is it possible to just have root set up on 4.2.2? Would like to keep all partitions stock if possible (as well as the bootloader). Would this help with stability issues? Sorry if these are noobish questions but thanks in advance

Dude you gotta give us a detailed guide on rooting puuuhleeaase

nejinikko said:
Dude you gotta give us a detailed guide on rooting puuuhleeaase
Click to expand...
Click to collapse
+1
I tried a chinese program without luck. I just bought a keyboard which works with the wrong layout in 4.2 and works perfect with 4.4 which I have on my other devices..therefore I am really looking forward flashing it!

Almost plain tegra
Hi, I agree with @Mobilla I installed android 4.4.2 from this link but be extreme careful, backup your rom first, KitKat works fine but randomly android freeze all system, I tested ClockWorkMod recovery and work flashing root file SuperSU-v1.94.zip but I don't test backup from recovery, well maybe someone can help us to know why kitkat freeze chinese root method is complicated I rooted with this method I don't read chinese I click some buttons and it works. Sorry with my English, I'm from El Salvador, I speak Spanish

I couldn't run 4.4 more than about 10 minutes before locking up, so I went back to 4.2.2 (rooted).
You can download the stock 4.2.2 update.zip from HP's website if you experience the same issues
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
The rooting method is the same as for the TN7 with the exception of fastboot commands you need to specify the vendorid (e.g. fastboot -i 0x03F0 oem unlock) I didn't try the Chinese tool.
You can flash root from recovery once it is unlocked.
I tried looking for what was causing the lockup but I couldn't find anything in the logs. If anyone has any tips for hunting down the problem I would be happy to try.

CWM
Hi, I tested CWM from this link and it works with nandroids backup, but the default storage is strange: /storage/emulated/sdcard0 but in this dir I can't move or delete that backup and use storage space I use a root explorer and can't move or delete, CWM works to root the device with SuperSU-v1.94.zip :good: but not for backup, see ya!

Rooting Slate 7 Extreme
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.

Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download http://forum.xda-developers.com/showthread.php?t=2627654
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse

sparkly81 said:
Hi @duocdx.bt good tutotial in
9. Remove the usb cable and reboot
you can reboot with this command:
fastboot -i 0x03F0 reboot
:good:
Click to expand...
Click to collapse
Thanks! Edited that in and fixed the link to the super tool. Hopefully this is clear enough to newer users such as myself Hopefully HP starts releasing stable updates for us but if not, things aren't too bad with root :good:

What can I do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

What can i do?
hi, I also install my hp slate 7 extreme with 4.4.2 tegra note7 version, like you my android is blocking a few minutes later, how I return to my 4.2.2 rom if I haven't the stock recovery but yes the update.zip from hp.

duocdx.bt said:
Ok, so I played around with the Tegra Note tools and figured I'd be happy with root on 4.2.2 as it allows me to use link 2 sd to move apps to my sd card. What tripped me up was the vendor id for fastboot. I understood that I'd have to type it out with the unlock command but I just kept punching in 'fastboot devices' to check if the tablet was being detected by fastboot... obviously not the way to go. Hopefully this brief summary of what I did can be helpful to someone else:
1. Download Nvidia Tegra Note 7 Super Tool 2.2
2. While your tablet is off, enter fastboot by pressing volume up + power, you'll see a couple options here - press volume down once and then the power button to select fastboot protocol.
3. Get your usb cable and plug the tablet into your pc.
4. Run the impactor program included in the super tools bundle. Select 'driver scan' from the USB menu, this will load fastboot drivers for your tablet.
5. Start up a command prompt and move it over to the super tool directory
6. Make sure your tablet is seen by the pc by typing "fastboot -i 0x03F0 devices"
7. Unlock the bootloader by typing "fastboot -i 0x03F0 oem unlock" you'll be warned that this voids your warranty, also you'll wipe anything currently installed on the tablet
8. Install CWM recovery by typing "fastboot -i 0x03F0 flash recovery Bat-CWM-Recovery.img"
9. Remove the usb cable and reboot (this is what I did, you can actually just use the command "fastboot -i 0x03F0 reboot")
10. Configure your freshly wiped device, reattach it to your pc with the usb cable and mount internal storage
11. Copy "SuperSU-v1.94.zip" from your tegra super tool folder over to internal storage
12. Turn off your tablet and re-enter fastboot by pressing volume up + power
13. Select recovery, you'll be in CWM. Select install zip from sd card, internal files will be shown so install the SuperSU zip you copied into internal storage earlier.
14. Reboot and you'll have root.
Hope this makes sense, I haven't had any problems with this setup and being able to move apps to the sd card is great.
Click to expand...
Click to collapse
Succesfully rooted my HP Slate 7 Extreme 4409ra Tablet ty!

I have a Slate 7 Extreme 4400ca, and today installed the update listed on the HP webpage:
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6617231#N147
after a non-destructive installation, 'about tablet' reports that I'm running ANdroid 4.3, kernel 3.4.57-gc102837
Not 4.4 yet, but this should be helpful.
I haven't tried rooting yet.

Just a update on a simple way to root stock 4.2.2 slate 7 extreme
http://towelroot.com
Download apk
Install
Restart
Enjoy
Worked for me.

[Q] [Help!] Forgot to activate USB debug mode before wiping, but CWM works

I decided to go to Android 5.0.1 from CM10.2 on my Nexus 4. I guess I did not think it though that well and relied on some crappy guides too much.
I have CWM Recovery 6.4.3 installed, so I thought I just place the factory image on the phone and install it via CWM. So:
1) Copied occam-....tgz on the phone;
2) Rebooted into CWM recovery;
3) Did wipe cache/format system/wipe dalvik;
4) Went to install .zip menu... and figured out that the file is no longer on my phone.
I thought OK, I do it via ADB and cable, so installed ADB, drivers etc. and connected my phone to my computer. However, adb does not see it most of the time (when at logo, bootloader, recovery) and only once adb managed to see it (*some number* device unauthorized) while the phone was at Google logo. And I realized I forgot to set up the USB debug option. What are my options now? I can go into CWM recovery, but ADB does not see the device, as I forgot to set up recovery before flashing. Help, please?
The computer sees the phone as MLP, but I still cannot see its storage in Explorer, so I cannot copy the .zip file.

Update
I managed to make adb recognize the phone, but consistently says that it is not authorized, which makes sense. And there is not way I can mount it as an external storage .

first of all, you have a serious lack of knowledge. not activating USB debugging in android settings has no effect whatsoever on ADB usage ability when you are in recovery mode. Secondly, installing factory images is not done through recovery (the downloaded factory image zip is not even flashable so it would work not in recovery), as factory images also contain RADIO and BOOTLOADER images that are flashable through fastboot (not the recovery). The only thing from factory image that you could flash via recovery is a zip file named - in case of 5.0.1 factory image - image-occam-lrx22c.zip (you can find it if you unpack the downloaded factory image on your PC). And this zip file is a classic ROM (system,userdata,boot,cache,recovery partitions). However, even if you were to flash the correct zip (rather than the zip containing entire factory image complete with ROM, RADIO and BOOTLOADER) Android 5.0 (or 5.0.1) comes with updated RADIO (maybe bootloader aswell, i did not check), so you are supposed to update that aswell prior to switching to 5.0/5.0.1
now here is what you should do:
1. download 5.0.1 factory image from gooogle
2. make sure you have ADB and drivers for Nexus4 correctly set up (in order to check wheter it works go see point 3 of this instruction set)
3. boot to fastboot mode (vol down+power) and check if 'fastboot devices' gives you back device id (you should open command prompt in platform-tools folder, where both adb.exe and fastboot.exe are present)
4. proceed with this instruction, start at step 8 http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ (in step 11, name of zip file is the one that is INSIDE downloaded factiory image file (image-occam-lrx22c.zip) and you either do the single zip flash or flashing each of .img files separately (system,boot,userdata,cache,recovery)
ps. 1st android 5.0.1 boot after flashing will take up to 15 minutes. (it took 10 in my case)

Update 2
Thanks dzumagos! Sure, I do not claim to be a specialist by any means. I managed to successfully install Cyanogenmod many times, so thought I would give this one a go as well.
I read your post after I fixed the issue. Basically I did exactly what you suggested, but following another guide and it worked fine, also took it around 15 minutes to load the first time. I noticed I do miss a few tricks from Cyanogenmod

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself

How do I Activate USB debugging

Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!

Hello, I have exactly the same issue.
I would be really grateful if someone could help us.

i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv

Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(

what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea

Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.

i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC