[Nexus 7 (2013) Q&A] rohanjoshi:
Bootlooping, adb not recognized, softbricked.

So, where do I start?

I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).

It restarted after the update and I've been stuck in a bootloop at the "4 circles".

I have done the following:

- put the device into the boatloader

- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)

- this was what my output looked like

Flash Stock + Unroot...

------------------------------------------------------------------

sending 'bootloader' (3911 KB)...

FAILED (remote: Bootloader is locked.)

finished. total time: 0.006s

rebooting into bootloader...

OKAY [ 0.006s]

finished. total time: 0.006s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-04.02

Baseband Version.....: none

Serial Number........: 08e8df8e

--------------------------------------------

checking product...

OKAY [ 0.003s]

checking version-bootloader...

OKAY [ 0.003s]

sending 'boot' (7018 KB)...

FAILED (remote: Bootloader is locked.)

finished. total time: 0.027s

Booting up your freshly flashed stock device...

------------------------------------------------------------------

Wait for your device to finish booting up...

- It may appear to be boot looping; just wait...

- It could take 5-10 minutes; please be patient...

When its finally booted back up, please remember

to re-enable USB debugging if you plan on using

the toolkit to perform other operations.

NOTE: If this process was too quick and your device

is still in bootloader mode, then flashing stock may

have failed or been incomplete. Simply check the

log above: if you notice it skipped steps because it

didn't meet certain requirements, like the bootloader

or baseband version, then consider enabling 'Force Flash'

mode in the toolkits options menu and trying the

'Flash Stock + Unroot' processs again. Cheers.

Press any key to exit...

​

- And no, I have not tried the force flash.

- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).

- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.

- I've tried some brute-force methods inspired by things I've seen here, as in:

un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe:

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot erase system

fastboot flash system system.img​

- My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.

I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.

I appreciate all your help :)