FORUMS

[Q] Nexus 7 Bricked, can't access Bootloader or Fastboot

15 posts
Thanks Meter: 3
 
By awhite2600, Junior Member on 14th August 2013, 06:50 PM
Post Reply Email Thread
I think I may have my Nexus 7 (2012) in a badly bricked state.

I was running Android 4.3, unlocked and rooted with stock recovery. The tablet froze while using GMail. Pressing the home or back buttons just gave me a black screen with the buttons "highlighted" by circles. I waited several minutes and decided to just power off the tablet. When I looked over about a half hour later I saw that the tablet was frozen on the white Google screen. Two more reboots produced the same result.

I did some research and determined that it might be a good idea to try a cache wipe. I booted into the bootloader and selected Recovery. The tablet rebooted to an android on his back with a red triangle and the words "No command" underneath. Attempting to boot back into the bootloader (Power, Vol+, Vol-) produced the same results - red triangle and the words "No command". I could no longer boot into the bootloader. Powering off and powering on normally also takes me to "No command".

I discovered that I can press Power & Vol+ while in the "No command" state. Doing so produces the following text at the bottom of the screen:

E:Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)


I get a menu at the top with the options to reboot, apply update from ADB, wipe data/factory reset and wipe cache. Attempting to wipe cache produces:

-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale


After a few minutes I boot back to the red triangle android.

Attempting a factory reset produces:

--Wiping data...
Formating /data...
Formatting /cache...
Date wipe complete.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
E:failed to mount /cache (Invalid argument)


I've tried using the apply update from ADB option. I can use adb devices to see the serial number. Fastboot doesn't seem to respond and won't list the device. Flashing the factory 4.3 image (downloaded from Google and unzipped) using adb sideload uploads the image and then produces the error:

Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.

...followed by all of the "cache mount / open errors shown previously"

Not sure what else to try. (I'm learning all of this as I go from reading posts on this site.) Is there a way to adb sideload the recovery partition as I suspect that it is corrupt?

Sorry to be so long winded. I figured that too much info was better than not enough. Any help would be greatly appreciated.
The Following 2 Users Say Thank You to awhite2600 For This Useful Post: [ View ] Gift awhite2600 Ad-Free
16th August 2013, 12:23 PM |#2  
Remcotjuuh's Avatar
Senior Member
Flag Groningen, the Netherlands
Thanks Meter: 60
 
Donate to Me
More
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here

http://forum.xda-developers.com/show....php?t=1907796

Sent from my Nexus 7 using xda app-developers app
The Following User Says Thank You to Remcotjuuh For This Useful Post: [ View ] Gift Remcotjuuh Ad-Free
17th August 2013, 05:26 AM |#3  
OP Junior Member
Flag London
Thanks Meter: 3
 
More
Quote:
Originally Posted by Remcotjuuh

So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here

http://forum.xda-developers.com/show....php?t=1907796

First - thanks for responding.

To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.

When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
  • reboot system now
  • apply update from ADB
  • wipe date/factory reset
  • wipe cache partition

The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.

I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.

Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.

Additional help is greatly appreciated. Thanks.
17th August 2013, 05:32 AM |#4  
Member
Flag Moscow
Thanks Meter: 7
 
Donate to Me
More
Quote:
Originally Posted by awhite2600

First - thanks for responding.

To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.

When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with

  • reboot system now
  • apply update from ADB
  • wipe date/factory reset
  • wipe cache partition

The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.

I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.

Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.

Additional help is greatly appreciated. Thanks.

Is it under warranty?
17th August 2013, 05:50 AM |#5  
OP Junior Member
Flag London
Thanks Meter: 3
 
More
Quote:
Originally Posted by xbt-

Is it under warranty?

No. It's about 10 months old.
17th August 2013, 06:24 AM |#6  
cmason37's Avatar
Senior Member
Flag Woodbridge
Thanks Meter: 122
 
More
Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?

Sent from my Nexus 7 using Tapatalk 4
17th August 2013, 08:52 AM |#7  
AndDiSa's Avatar
Senior Member
Flag Heidelberg
Thanks Meter: 4,105
 
More
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.

Sent from my Nexus 7 using xda app-developers app
The Following User Says Thank You to AndDiSa For This Useful Post: [ View ] Gift AndDiSa Ad-Free
17th August 2013, 12:08 PM |#8  
Remcotjuuh's Avatar
Senior Member
Flag Groningen, the Netherlands
Thanks Meter: 60
 
Donate to Me
More
Quote:
Originally Posted by AndDiSa

Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.

Sent from my Nexus 7 using xda app-developers app

He has already said he can only boot into stock recovery, not bootloader.

Sent from my Nexus 7 using xda app-developers app

---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------

Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?

Sent from my Nexus 7 using xda app-developers app
The Following User Says Thank You to Remcotjuuh For This Useful Post: [ View ] Gift Remcotjuuh Ad-Free
17th August 2013, 01:09 PM |#9  
OP Junior Member
Flag London
Thanks Meter: 3
 
More
Quote:
Originally Posted by cmason37

Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?

Sent from my Nexus 7 using Tapatalk 4

The tablet froze during normal operation. (Checking GMail.) I simply turned it off...or so I though. When I looked over about 30 minutes later it was stuck on the white "Google" screen. I was able to boot into the normal bootloader at this point. My thoughts were to then select stock recovery and just wipe the cache. It's been in the "red triangle" and "No command" since then.
17th August 2013, 01:14 PM |#10  
OP Junior Member
Flag London
Thanks Meter: 3
 
More
Quote:
Originally Posted by AndDiSa

Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.

Sent from my Nexus 7 using xda app-developers app

The bootloader is unlocked. I was rooted with stock recovery. I have uninstalled and reinstalled drivers several times. I know for certain that the ADB drivers are installed. I don't have an easy way to confirm that the fastboot drivers are installed - but they should be.
17th August 2013, 01:21 PM |#11  
OP Junior Member
Flag London
Thanks Meter: 3
 
More
Quote:
Originally Posted by Remcotjuuh

He has already said he can only boot into stock recovery, not bootloader.

Sent from my Nexus 7 using xda app-developers app

---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------

Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?

Sent from my Nexus 7 using xda app-developers app

I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.

The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes