• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Nexus 7 (2012) Ruined Bootloader

asrock73

Lurker
Nov 13, 2013
6
4
So first off, I looked through the forums and found nothing like this, I could have easily missed something and I apologize if I did.

So I had a custom ROM on my Nexus 7 2012, I went to restore to stock to get the kitkat update last night. Apon reboot it was stuck in the flashing nexus X. I got it to restart but the boot loader is completely corrupted, and I feel pretty confident I have ruined my tablet.

The symptoms:
I can boot in to bootloader, if I try to start the Recovery mode, I get "Booting Failed"
I can plug it in to my computer and NRT can see the tablet in fastboot mode, I can even restart the tablet back to bootloader.
I have tried to boot new bootloaders on it but keep failing.
I tried to put the stock OS on it with NRT and I get the following results:

Flash Stock + Unroot...
------------------------------------------------------------------

erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
erasing 'recovery'...
OKAY [ 0.012s]
finished. total time: 0.012s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.050s]
finished. total time: 0.050s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.998s]
finished. total time: 0.998s
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.020s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 0.010s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d24a42840120f
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.010s]
sending 'boot' (4896 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.160s

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...



ODIN does not see the tablet, and it also fails if I try to use my Windows PC command prompt to flash the table.

Any thoughts or suggestion please? Or I am correct to believe I have ruined my tablet? I thank you all for any help!

P.S. - Be aware I am still very much a noob, and I am still learning.
 
Also if I attempt to flash the bootloader img using the command prompt I get :

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cdc:
'cdc:' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>cd c:\
c:\>dir
Volume in drive C is Gateway
Volume Serial Number is 1E2B-4CDE

Directory of c:\
01/28/2013 06:29 AM <DIR> Adams Business Forms
11/13/2013 12:46 AM <DIR> Android-adb
05/08/2013 06:00 AM <DIR> components
05/04/2013 07:52 PM 0 END
05/04/2013 07:52 PM 0 extensions.sqlite
11/13/2013 07:01 PM <DIR> nakasi-jwr66y
10/22/2013 02:52 PM <DIR> OpenELEC-RPi.arm-3.2.3
07/13/2009 10:20 PM <DIR> PerfLogs
10/07/2013 06:18 AM <DIR> Program Files
11/13/2013 12:08 AM <DIR> Program Files (x86)
06/08/2013 04:19 PM <DIR> Riot Games
11/13/2013 05:52 PM <DIR> Temp
06/07/2013 09:06 PM <DIR> Unreal Anthology
12/07/2012 08:13 PM <DIR> Users
11/13/2013 05:53 PM <DIR> Windows
2 File(s) 0 bytes
13 Dir(s) 390,797,029,376 bytes free

c:\>cd c:\nakasi-jwr66y
c:\nakasi-jwr66y>fastboot devices
015d24a42840120f fastboot

c:\nakasi-jwr66y>fastboot erase boot
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s

c:\nakasi-jwr66y>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s

c:\nakasi-jwr66y>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.010s]
finished. total time: 0.010s

c:\nakasi-jwr66y>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.050s]
finished. total time: 0.050s

c:\nakasi-jwr66y>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.995s]
finished. total time: 0.995s

c:\nakasi-jwr66y>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s

c:\nakasi-jwr66y>
 
Upvote 0
After a quick charge, using the original ASUS cable and USB 2.0 port it worked.

Again, THANK YOU both for the help. I hope one day I get as good as you all.


There is nothing worse than thinking you maybe bricked your device when the solution is easily achievable by asking a great community of people willing to help.

:)

You have helped others by confirming a solution to the problem, others with a similar issue in the future that search for an answer will possibly find their solution in this thread as a result.

Glad we were able to help.
 
  • Like
Reactions: h4x0rj3ff
Upvote 0
Cable cable cable.. What USB cable are using?

Try a different one, and when you have tried that try third one.

Try all three cables again in a different USB port, preferably one physically attached to the computer.

Try a forth cable.

It seems fine until it gets to data transfer, gotta try cables first.

massive thanks for this too! this was driving me crazy.
 
Upvote 0
Cable cable cable.. What USB cable are using?

Try a different one, and when you have tried that try third one.

Try all three cables again in a different USB port, preferably one physically attached to the computer.

Try a forth cable.

It seems fine until it gets to data transfer, gotta try cables first.
YOU saved my ass... thanx...
 
  • Like
Reactions: scary alien
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones