[Q] Bricked N7 2013 LTE

Hi everybody,
I own a N7 2013 LTE (deb) with Android 5.1.1 installed (build: LMY48P). This morning I've tried to turn on my device and it remains stuck on Google logo. :(

The device correctly goes into Fastboot mode but from here I cant do anything:
Start: see the Google logo and stuck
Restart bootloader: correctly reopen the bootloader
Recovery mode: see the Google logo and stuck
Power off: correctly power off

These are the informations showed in the Fastboot screen:
FASTBOOT MODE
Product Name: deb
Variant: deb 32G
HW version: rev_e
BOOTLOADER VERSION: FLO-004.05
BASEBAND VERSION: DEB-Z00_2.44.0_0213
CARRIER INFO: None
SIGNING: yes
SECURE BOOT: enabled
LOCK STATE: locked

I've downloaded Nexus Root Toolkit v2.05 by WugFresh and the device is correctly seen from my windows pc and from NRT (I've succesfully installed USB drivers).
From NRT I've tried to "Flash Stock + Unroot" but I cant flash because the bootloader is locked; so I've tried to unlock the bootloader from NRT, the N7 correctly show the "Unlock bootloader?" screen, I move to "YES" with the volume keys but when I push the power button to confirm, nothing happens and the tablet continues to show that screen (I've waited about 30mins and nothing happens).

I dont care about user data and my photos and videos; I'd like to have my tablet working.

Some questions:
1) is there a way to launch a stock recovery or a TWRP recovery from NRT so I can wipe all data and have my tablet back working?
2) is there a way to see from NRT le log? I'd like to see some more specific error details when I try to unlock bootloader and it fails.
3) do you have some advices? thanks in advance

Thanks guys

How to install Android 6.0 on my Nexus 7 2013?

Hi all,
First at all, sorry for my bad English. I'm trying to install Android M's factory image on my Nexus 7, but I'm very lost. Someone could explain me the process step by step? My device isn't root.
Thank you very much.

[Community] [Whatsapp] G 2013 (12/100)

Moto G 2013 Android Discussion Group On Whatsapp
This is a community for all moto g users who come from all variants of the device
Rules and Regulations
1. No Off Topics are allowed
2. Members should help other members and use respectfull language in the group
3. No members are allowed to get racist or he/she will be banned immediately without prior information being provided
4. If any member spams in group others are requested to contact admin along with the members whatsapp
That's It for now :) Other regulations will be given in the group itself
Reply to this thread to get added :) users will be instantaneously added

Does Google still replace defective N7 2013?

I have a Nexus 7 2013 which I've stopped using because of its buggy Touchscreen. It was purchased directly from Google when it first came out.

Does anyone know if Google still replaces them?

Nexus 7 2013 WiFi - WiFi won't turn on after Marshmallow upgrade - bad Mac Address

Just sideloaded the Mashmallow update from 5.1.1 to 6.0 (downloaded from Google) and the update seemed to go normally - most things work as normal. But the WiFi wouldn't turn on, and it's mac address reports as 02:00:00:00:00:00. That address I know was an issue in the M Preview as a fake address.

I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)

When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.

Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?