Can't wipe or factory reset Nexus 7 (2102) using multiple methods

[barrymcsorley]

A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:

* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache

It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.

I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader ([GUIDE] Flashing a Factory Image with fastboot / return to stock - xda-developers) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...


*** Trying with ADB manually ***

C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device


C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device


C:\android-sdk\platform-tools>adb reboot-bootloader

C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot

C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s

C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s

C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s

C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s

C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s

C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s

C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s

C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s

C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.zip
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........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 2.203s]
rebooting...

finished. total time: 165.625s

*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------

erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s

sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s

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........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.266s]
rebooting...

finished. total time: 1197.719s

 

[dancing-bass]

using ADB commands kinda scare me so I rely on Wugs. Have you tried reverting to an older factory image (say 4.1.2 JZO54K for example) and then letting the tablet itself update? Wugs does have a setting for a device stuck in bootloop. I (thankfully) haven't had any problems with my 2012, so I'll keep an eye on this thread.

 

[Tosus]

I have this exact same problem with my device. It always appears to do what you ask, but once you reboot none of the changes took effect. Other threads have seemed to imply this may be a hardware problem that would require an RMA, but that it may be covered by warranty. I'll let you know if I learn anything.

 

[pwllheli]

Me too.
GroundHog Day every time I try anything. Obeys commands... but back to Square 1.

 

[barrymcsorley]

I've tried going to older releases of 4.1.2 all the way up to 4.4 and all seem to flash fine but then reboot and it's the same old 4.2.2 with crashing apps! The more I read about this the more it seems to be hardware related - possibly motherboard. Pretty gutted if I can't fix it by flashing a software build....

 

[DWEIL]

Has anyone been able to confirm that this is a hardware issue. I have an N7 2012 as well, and it is exhibiting the same "zombie" behavior described above.

I've come to the conclusion that the source of the problem is that my N7 is, for some reason, in read-only mode. I have explored changing file permissions, but no luck so far. I compared the root directory permissions of my Nexus 5 with my N7 2012 and the main variance was the entry for the SD storage:

Nexus 7
d---r-x--- root sdcard_r 2014-06-10 13:33 storage

Nexus 5
drwxr-x--x root sdcard_r 1970-07-23 04:56 storage

I'd be grateful if anyone has any additional info or suggestions on this problem. I have another N7 (2013), so I do have a tablet that works. Still, I'd like to have the 2012 model working and available as a backup.

Many thanks.

 

[Alex M7]

Same bug on my Nexus7 (2012) 16 GB Wifi (not rooted, original ROM) Android 4.4.2. Since yesterday, if I try to swipe cache, factory reset but also simply delete an app or even an user profile, when I restart the tablet all returns back like a zombie!!!

 

[barrymcsorley]

I've given up on my Nexus 7 now as just can't seem to make any change to it! The file permissions you noticed sounds promising and hopefully someone can follow up on that....

For me I'm looking at getting a cheap 2013 model or waiting for a new version to come out. I was advised that it might be a CPU or motherboard hardware issue but without knowing for sure I don't want to spend money trying to bring it back to life - plus the instructions to replace them are not for the faint hearted!

It's a shame but my Nexus 7 is now gathering dust in the drawer where all the old gadgets go to die....

 

[DirtBikeDaddy]

I've just recently taken my Nexus 7 to TechKnow Space, and for $60 it's now running some custom ROM. I'll try talking TechKnow into installing the factory ROM for me (no extra charge) and report back to you smart people. I'm just not into all this "coding" like the rest of you

I love the Android OS, but please don't make me learn something new just to use it... LOL

Cheers
DBD

 

[barrymcsorley]

Hi DBD,

I'd be interested to know how TechKnow got that customer ROM on there or even the factory ROM. I've tried loading all those too and when I reboot it comes back to the same old crashing screen but maybe they're using a different method?

 

[KDblr]

Hello all,

I know this is an old thread but stumbled upon it after many hours of trying everything I know.
I'm having the same issue with my Galaxy Nexus, I know this is a Nexus 7 thread, but the symptoms are the same and at the end of the day it's a Nexus Device

Device Info
• Galaxy Nexus
• Stock 4.3 ROM
• OEM Unlocked
• Rooted
• Been using it this way since January now.

This morning as I unplugged it from the charger it decided to reboot itself every 2 mins.

Here's what I've tried
• Wipe Cache , Dalvik Cache
• fastboot format of : cache, system, userdata
• fastboot system.img, boot.img, userdata.img from stock images
• Re-lock and unlock OEM (which is supposed to delete all data)
• Wipe/Factory reset from Clokworkmod recovery
• flashall.sh with original factory image from googles dev site
• Load Cyanogenmod 10.2 via adb and install via recovery (Clockworkmod)

None of the above have worked :'(
I'm at my wits end. I've looked all over and haven't found a solution yet

Unfortunately
• The galaxy nexus was never officially sold in my country (India) to begin with
• The phone is old and support for this model has ended
• So no warranty either ways

I'm praying this isn't a hardware issue, and that this would be sorted with a simple software tweak. But I am handing it over to a phone repair shop tomorrow to test the hardware...

Wanted to know if anyone else has managed to find a solution?

 

[KDblr]

Hello Hello hello...hello...

Don't know if anyone is still paying attention to this thread, but thought I'd post a status update anyway.

After handing the phone over to phone shop for servicing. I've been told that

• The Power module is damaged
• Specifically the Boot IC
• The slightest rise in temperature is making the phone reboot

So there you have it. It's costing me Rs. 3,400 ( $55 approx ) to get it fixed, (Parts + Labor)
They're also giving me a 3 month warranty on the spares...

Hope this works
and more importantly, I hope this helps some of you.

Hello all,

I know this is an old thread but stumbled upon it after many hours of trying everything I know.
I'm having the same issue with my Galaxy Nexus, I know this is a Nexus 7 thread, but the symptoms are the same and at the end of the day it's a Nexus Device

Device Info
• Galaxy Nexus
• Stock 4.3 ROM
• OEM Unlocked
• Rooted
• Been using it this way since January now.

This morning as I unplugged it from the charger it decided to reboot itself every 2 mins.

Here's what I've tried
• Wipe Cache , Dalvik Cache
• fastboot format of : cache, system, userdata
• fastboot system.img, boot.img, userdata.img from stock images
• Re-lock and unlock OEM (which is supposed to delete all data)
• Wipe/Factory reset from Clokworkmod recovery
• flashall.sh with original factory image from googles dev site
• Load Cyanogenmod 10.2 via adb and install via recovery (Clockworkmod)

None of the above have worked :'(
I'm at my wits end. I've looked all over and haven't found a solution yet

Unfortunately
• The galaxy nexus was never officially sold in my country (India) to begin with
• The phone is old and support for this model has ended
• So no warranty either ways

I'm praying this isn't a hardware issue, and that this would be sorted with a simple software tweak. But I am handing it over to a phone repair shop tomorrow to test the hardware...

Wanted to know if anyone else has managed to find a solution?

 

[nexus fan]

well guess what my nexus has excatly the same issue.. reset it, use rootkits it follows all commands.. wipe all date but on rebooting its like it was .. no app can be deleted.. can remain on for hours on toolkit or in recovery mode but when u start using it after reboot it keeps rebooting... since u gave it for repair i have to do the same.. where did u give it.. google has no service centres and samsung guys refused to repair it saying its not released in INdia.. pls clarify... thanks

Hello Hello hello...hello...

Don't know if anyone is still paying attention to this thread, but thought I'd post a status update anyway.

After handing the phone over to phone shop for servicing. I've been told that

• The Power module is damaged
• Specifically the Boot IC
• The slightest rise in temperature is making the phone reboot

So there you have it. It's costing me Rs. 3,400 ( $55 approx ) to get it fixed, (Parts + Labor)
They're also giving me a 3 month warranty on the spares...

Hope this works
and more importantly, I hope this helps some of you.

 

[Happy Di]

I have the same thing occurred in my Galaxy Nexus. Almost, I did everything you have done.
* Wipe fact and data, & wipe cache
* successfully flash image in Odin mode and fastboot mode. None of them successfully in last 1 week.

thank you for posting your experience in here.

 

[B. Diddy]

Welcome to Android Central! This thread is about the 2012 Nexus 7 from Asus, not the Samsung Galaxy Nexus phone. The Nexus 7 doesn't support Odin.

 

[Pathh11]

Is this question still unanswered? Same problem with my Nexus 7 with KOT349H: soon after some OTA 'update' in Feb it started the rebooting after c. 5min. I do a hard-reset / factory reset and get warnings etc, but nothing happens. Same with not remembering a wifi password, remembering that I deleted apps etc. Everything goes back to old status when restarted. Now finally on holiday so looking at what I can do. Is it hardware or software? What to do?

 

[fed123]

Just joining the crowd. Same issues except that I am on lollipop. If this is the end, the old gadget served me well. Luckily, I also have the LTE 2013 version running well on Kit Kat.

 

[joanne w]

I have had this exact problem with my 2012 nexus 7. Google not interested and Asus said it sounded like hardware. I have hung on to it in case anyone ever comes up with a fix

 

[natehoy]

Unfortunately, the common symptom here is that portions or all of flash memory seem to have become un-writeable (and therefore un-erasable). I can't think of anything except a hardware issue that would cause this - if it was software then recovery mode should be able to overwrite it with fresh software that works properly.

The memory is soldered on to the motherboard, so that's it for your motherboard, I'm afraid. I think motherboards for the Nexus 7 2012 are available fairly inexpensively and it's not a terribly hard job to swap it out to my knowledge. Might be a fun hobby project without too much risk or expense.

 

[smuttlegiaco]

had this issue also. we used the tablet as a test device for our games and after a while trying everything I could think off to make it work again, I trashed the damned thing in a fit of rage.