Database Users

Bootlooping, ADB not detected, can't enable debugging

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

rohanjoshi said:
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
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!

Nexus 7 Bricked!!!

So today my Nexus 7 got bricked by my little child. Somehow my child managed to get to TWRP going to recovery and deleted everything!!!!!. He somehow deleted the backups and the bootloader/baseband versions. My Nexus 7 was running an old version of Paranoind android and it was on 4.23 i believe. Since I now have a new Computer and my recovery/backup files have been erased from my old one I cannot fix my tablet. I currently use Nexus Root Toolkit v1.8.1 by Wug's masterpiece and it freezes when I tried to flash stock and unroot my tablet using the soft- brick/bootloader method.
My tablet is stuck at the bootloader and I have no idea how to fix it. it seems like it cannot get the baseband version according from the bootloader version on the tablet screen since it says n/a.
Here is some information from that says on the tablets screen " when i press start on the bootloader screen on the top left it says " Booting failed" and on the screen it shows google and the unlocked sign.
Does anyone know how to fix this?
edit: I somehow was able to get the bootloader version from the method i tried above. It says 4.23 but it still froze. The baseband version is still n/a tho :\
and it's the Nexus 7 16 GB wifi tablet
Edit 2: when i try to flash stock it says
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.440s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
archive does not dcontain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse

WiFi tablets don't have a baseband version that only applies to mobile networks. Try this
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from one of my 47 iPads running android C3P0

[Q] [Solved]stuck on: sending 'bootloader' cant flash anything?

Hey there,
I tried to upgrade my Nexus 7 grouper using the 4.23 bootloader and some of the stock roms, cyanogenmod and miui as well as slimkat roms, it kinda didnt work out the way I wanted it to, now I am stuck on: sending 'bootloader' (2100 KB) while not having any recovery nor anything else on my nexus...
the bootloader seems broken, because it always doesnt response when I try to flash an img file..
Thankful for any help

Can you get into fastboot mode?
Did you get the bootloader-grouper-4.23.img file from one of the factory images here?
What is the md5?
I've been reading that these factory image bootloaders (JWR66Y & KOT49H) do not work.
Check out these threads:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?p=45043044#post45043044

It seems like I used the bootloader from nakasi-kot49h-factory-5e9db5e1
it has got the md5 hash 797a8ddfe19bfe4c485f8a8c119f1bdd
I tried to flash the 4.23 bootloader from the second link, which is the JWR66V version, but still cannot flash it, because by device freezes and the "Flashing bootloader-grouper-4.23.img" of Nexus Root Toolkit doesnt do anything than being stuck.
edit:
Ok , I managed to get my recovery back via fastboot.exe via "fastboot flash recovery recoveryname.img"

I managed to flash normal custom roms via fastboot and adb sideload, but I cannot change the bootloader from the bricked 4.23 one to the one mentioned in the topics which should be a working one from the nexus 7 JWR66V build.
I always get the error
Code:
sending 'bootloader' (2100 KB).
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
Any ideas?

The Unified Android Toolkit seems to overwrite the broken bootloader easily and after a few attempts of trying to write the factory image with the Unified Android Toolkit and trying out different usb slots, because I often got the error "Unknown Device" and thus Windows 7 could not install any drivers, it worked out.
Thanks

[Q] Cannot update boot loader from 4.18 to 4.23

I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.

Ahkah said:
I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.
Click to expand...
Click to collapse
Use the version from that post. And the command is fastboot flash bootloader not boot.

riggerman0421 said:
Use the version from that post. And the command is fastboot flash bootloader not boot.
Click to expand...
Click to collapse
So it was finally just a dumb typo. Thanks! And of course the questions remain why fastboot did not respond with an error message when I tried to install the bootloader using a wrong command and why Google's original package failed to be installed.

It didn't give am error because it was flashing an image file(bootloader) to a correctly named partition (boot). The error was yours, flashing the file to the wrong partition. Fastboot was following the instructions you gave it. As for the bootloader file not flashing, it has been broken for a while in the factory image. I guess Google isn't worried about fixing it.

Old Nexus 7 2012 - probs downgrading to 4.4.4

Old Nexus tablet been staring out me for a while. Way too slow on Android 5, so attempting to downgrade to 4.4.4.
All goes well until I get Snapshot cancel error - any advice how to fix please?
Appreciate your advice!
CMD output :
G:\Android ADB\Run\Nakasi\nakasi-ktu84p>fastboot -w update image-nakasi-ktu84p.zip
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d490607481e08
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.036s]
Checking 'version-bootloader' OKAY [ 0.024s]
Snapshot cancel FAILED (remote: '(')
fastboot: error: Command failed

Nick987M said:
Old Nexus tablet been staring out me for a while. Way too slow on Android 5, so attempting to downgrade to 4.4.4.
All goes well until I get Snapshot cancel error - any advice how to fix please?
Appreciate your advice!
CMD output :
G:\Android ADB\Run\Nakasi\nakasi-ktu84p>fastboot -w update image-nakasi-ktu84p.zip
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d490607481e08
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.036s]
Checking 'version-bootloader' OKAY [ 0.024s]
Snapshot cancel FAILED (remote: '(')
fastboot: error: Command failed
Click to expand...
Click to collapse
Search YouTube for "How To Get Back To KitKat On Nexus 7 (2012)." I followed a video by RyTech and it was pretty straightforward--I had to show hidden folders to find the AppData folder but it was easy after that.

Unable to access Nexus 7 following previous failed Flash
Think the Nexus 7 has finally bricked. As suggested, I ported the Studio Platform tools across, however the fundamental problem is that previously attempt at Flash will have deleted the OS and I can't get into bootloader as I assume you need the OS to re-enter Developer Mode?
Connecting Nexus to PC, I do get the connecting (PC) audio to confirm the connection, however the display remains blank, despite on/off & Volume up/down combinations - no devices found when 'ADB devices' entered, and as you'd expect, no response to 'adb reboot bootloader' .
Help!
Many thanks.