[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕

k23m · Feb 8, 2016

Quick Links

if fastboot mode is not available, try Unbricking Guide
if fastboot mode is available, do RESTOCK

In this thread I would like to consolidate information about eMMC flash memory failures and remedies.

When flash memory fails it becomes inaccessible or unwriteable with errors like the following:

Code:

sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
   or
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E:failed closing /dev/block/platform/msm_sdcc. 1/by-name/misc (I/O error)
E:failed to mount /cache (Invalid argument)
   or
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.

   dmesg...
mmc0: error -110 whilst initialising MMC card

We observe these hardware failure symptoms:

device is totally dead
dead but flashes a few times the white LED next to USB port
dead but with active USB on PC device list
works up to fastboot stage or Google logo
may slowly boot Android sometimes
intermittently Android does not boot or work at all

#1 - eMMC unrelated

#2 - battery fault is most likely

#3 - catastrophic eMMC failure or GPT/bootloader damage, PC registers a new USB\VID_05C6&PID_9008 device, refer to QPST diagnostics below

#4 - partial eMMC failure or OS error, refer to fastboot diagnostics below

#5 - probably eMMC failure, unlocking and TWRP tests are required - post your logs

#6 - unlikely eMMC fault

Fastboot Diagnostics

QPST Diagnostics

Repair Options

ASUS service - apparently they can now do it for free with paid shipping!
motherboard replacement - for example this one "pulled from a working unit" for $25
RIFF JTAG Box - while the box is not cheap it can be used for other devices too (v1 was $109). Optional tool.
off-circuit eMMC programming and chip replacement - it is difficult and expensive but feasible
in-circuit Service ROM flashing - after chip replacement or if eMMC is OK but with damaged partition table or bootloader

eMMC chip replacement

do not replace it with another Kingston
search for eMMC in FBGA 153 or 169 package
you can upgrade it to a higher capacity memory
new high-performance eMMC v5.1 requires updated software, available here

Nexus 7 2013 uses 3 brands of eMMC chips: Kingston, Hynix and Toshiba.

Kingston was initially identified as unreliable in this post a few years ago:

Google Nexus 7 2013 (Asus Razor)
This is bootloader repair package for Google Nexus 7 based on QUALCOMM APQ8064 MCU. Tegra based is not supported !
- GPT is for 32GB chip, hence it's not ticked by default. DO NOT tick it if You have 16GB version
- EFS/CEFS partitions You can tick in case that nothing else works, it's not recommended to try it if You haven't made backup first. In this model, partitions layout is different from all other known Qualcomm devices, hence reading first 512MB for backup wont do any help. Do do proper backup, You have to read 2GB + size (from 0x0000 0000 0000 to 0x0000 9000 0000)
Important ! ! !
- If You have device which hangs on Google logo, and resurrection process hangs at 1%, You'll have to replace the eMMC chip first. Kingston eMMC chips used in these devices oftenly fail and become unwriteable !
Attached Files Asus_Nexus_7.rar (103.60 MB)

The above file is for RIFF JTAG flasher.

Please post your Nexus 7 2013 eMMC maker in this thread.

So far I have collected the following reports:

Code:

BRICKED         Kingston  Hynix     Toshiba
-------------------------------------------
graphdarnell    1                
fuser-invent    1                
aungmyoswe      1                
marc1706        1                
micl9           1                
consumer61                          1*
bl4cKz4cK       1
patmann03       1
CWempe          1
purian23        1
NX3             1
ali1234         1
lowridincrew    1
DaWeIII         1
HTC Tytn...     1
jaybea          1
vfrvulcan       1
TechnicsKuzya   2
barbuda         1
Snoob25         1
Dazmatic        1
459below        1
amix            1
hypochondrej    1
                                 
WORKING         Kingston  Hynix     Toshiba
-------------------------------------------
fuser-invent    1                
k23m                      2      
yosmokinman               2      
Tmzdroid        1                
graphdarnell    1         2      
OrBy                                1
mydian                              1
quickdraw86               1
micl9                     1
tegodwin                  1*
noahvt                    1
Carrick Glen              1*
Axel85                    1
NTRNSTR                   1

*2015 production

To check the chip in working units use this app or dmesg:

Code:

Kingston (MMC32G)
-----------------
mmc0: new HS200 MMC card at address 0001
mmcblk0: mmc0:0001 MMC32G 28.8 GiB

Hynix (HBG4e)
-------------
mmc0: new HS200 MMC card at address 0001
mmcblk0: mmc0:0001 HBG4e 29.1 GiB

Toshiba (016G92)
----------------
mmcblk0: mmc0:0001 016G92 14.6 GiB

It is not so simple with bricked units but this device is exceptionally easy to disassemble. The chip is on the bottom of the motherboard but unlike the top, it is not covered with any shield (the purple chip).

:good:

OrBy · Feb 8, 2016

SD insight says mine is using a Toshiba chip:

Model 016g92, size 16gb, manufacture Apr 2013.

k23m · Feb 8, 2016

OrBy said:
SD insight says mine is using a Toshiba chip:
Model 016g92, size 16gb, manufacture Apr 2013.

The third brand - I updated our stats. Thanks a lot for your post!

mydian · Feb 9, 2016

Mine also says Toshiba chip that was manufactured June 2013. I purchased it in November of 2014.

k23m · Feb 9, 2016

mydian said:
Mine also says Toshiba chip that was manufactured June 2013. I purchased it in November of 2014.

Would you be able to check if dmesg log of Toshiba's chip matches model number in the app? My N7 has HBG4e in dmesg and the app.

quickdraw86 · Feb 9, 2016

k23m said:
Would you be able to check if dmesg log of Toshiba's chip matches model number in the app? My N7 has HBG4e in dmesg and the app.

Mine also has HBG4e in dsmesg and the app... Also may 2013.

Tmzdroid · Feb 9, 2016

I don't think this flash memory problem is mainly on Kingston equipped Nexus 7's. I previously had a device with hynix flash and it would bootloop/restart/hang at Google logo endlessly so I exchanged it for my current device (with Kingston memory ) which runs superb. Is there any way of measuring degrading flash memory over time if there is I'll do it or anything else to solve this issue.

I still have nearly 2 years warranty so am willing to be a Guinea pig.

So after nearly 2 years of daily usage my device is still running like a champ I haven't noticed any performance slowdown over time ?. The touchscreen response improved after I replaced the battery a while back I'm guessing it had something to do with the ribbon cable or the small circuit board attached to the battery ?.

k23m · Feb 9, 2016

Tmzdroid said:
I don't think this flash memory problem is mainly on Kingston equipped Nexus 7's. I previously had a device with hynix flash and it would bootloop/restart/hang at Google logo endlessly so I exchanged it for my current device (with Kingston memory ) which runs superb. Is there any way of measuring degrading flash memory over time if there is I'll do it or anything else to solve this issue. I still have nearly 2 years warranty so am willing to be a Guinea pig

I have Hynix N7 which had a bootloop but this was my fault, I think, because I disabled a service. Now it runs CM12.1 and no more OTAs.

Yes there is a way of measuring flash memory just like SMART in HDD - it was introduced in eMMC v5.0 as "Device Health Report" but our Nexus 7 is probably too old for it. I received a very detailed description of fuser-invent's bricked Nexus 7 with Kingston KE4CN5B6A chip which is eMMC v4.5, without the health report function.

Can you please check the production date of your Kingston? It is possible that only early units were affected and you have nothing to worry about. Kingston does not actually manufacture NAND flash and can use any component available for a product or just change it later.

Tmzdroid · Feb 9, 2016

k23m said:
I have Hynix N7 which had a bootloop but this was my fault, I think, because I disabled a service. Now it runs CM12.1 and no more OTAs.

Yes there is a way of measuring flash memory just like SMART in HDD - it was introduced in eMMC v5.0 as "Device Health Report" but our Nexus 7 is probably too old for it. I received a very detailed description of fuser-invent's bricked Nexus 7 with Kingston KE4CN5B6A chip which is eMMC v4.5, without the health report function.

Can you please check the production date of your Kingston? It is possible that only early units were affected and you have nothing to worry about. Kingston does not actually manufacture NAND flash and can use any component available for a product or just change it later.

It's July 2013 my previous device was pure stock 6.0.1 factory reset etc it wouldn't even turn on 50% of the time I messed about inside with the ribbon connectors and insulating tape and it improved a little. I had to wait 3 weeks for a replacement which I'm very happy with. Have a look at my previous xda posts you'll get the gist of what I'm saying.

Erick Pontes · Feb 9, 2016

i flashed on my nexus 7 2013 one 2012 rom, now he changed to grouper and i cannot use any rom from my 2013, how i go back to the 2013 rom ? since i have signature missmatch

Tmzdroid · Feb 9, 2016

Try the Nexus Root Toolkit (NRT) by wugfresh

k23m · Feb 9, 2016

Tmzdroid said:
It's July 2013 my previous device was pure stock 6.0.1 factory reset etc it wouldn't even turn on 50% of the time I messed about inside with the ribbon connectors and insulating tape and it improved a little. I had to wait 3 weeks for a replacement which I'm very happy with. Have a look at my previous xda posts you'll get the gist of what I'm saying.

I read your thread. It was a hardware fault but not of Hynix or other eMMC which, in Nexus 7 2013, fails either catastrophically or becomes unwriteable. It looks like a battery fault. The Nexus is almost 3 years old and statistically it is time for all batteries to go now.

Have a look at my second Nexus 7 2013, it was dead, unrechargeable and would not start on external power. I replaced the original 4Ah battery with 1Ah from an ancient phone. A much smaller battery was not an issue because I always use it with power supply. I have since changed it to 2x 1Ah batteries because the old 1Ah gradually started to do exactly as you describe: rebooting (a lot) also struggling to boot up while being fully recharged and constantly connected to a charger.

mydian · Feb 10, 2016

Here is my screenshot from SD Insight. How do I check with dmesg? When I type it in the terminal emulator I get pages and pages of stuff and am not familiar with what I'm looking at.

k23m · Feb 10, 2016

mydian said:
Here is my screenshot from SD Insight. How do I check with dmesg? When I type it in the terminal emulator I get pages and pages of stuff and am not familiar with what I'm looking at.

Please type the following in the terminal:

Code:

dmesg | grep mmc0

it will be probably - mmcblk0: mmc0:0001 016G92

Or use this open source app.
Either way do it asap after reboot because dmesg is buffered and soon overwritten.
Thank you for checking it.

mydian · Feb 10, 2016

k23m said:
Please type the following in the terminal:

Code:

dmesg | grep mmc0 it will be probably - mmcblk0: mmc0:0001 016G92

Or use this open source app.
Either way do it asap after reboot because dmesg is buffered and soon overwritten.
Thank you for checking it.

Thanks that was much easier, and you are correct with what it says.

k23m · Feb 10, 2016

Thank you again. I updated the front page with Toshiba info.

:good:

aungmyoswe · Feb 11, 2016

i have too with Kingstone 32G EMMC

so so dead Asus Nexus 7 (2013) wifi

only, connect to computer it will " Qualcomm HS-USB DQloader 9008 "....and nothing , may be dead boot or damage emmc .If anyone have a good N7 2013 device, there is a way to backup the necessary files. Here....
so please,i need that files....

thanks for reading and sorry for my english

k23m · Feb 11, 2016

aungmyoswe said:
so so dead Asus Nexus 7 (2013) wifi
only, connect to computer it will " Qualcomm HS-USB DQloader 9008 "....and nothing , may be dead boot or damage emmc .If anyone have a good N7 2013 device, there is a way to backup the necessary files. Here....
so please,i need that files....
thanks for reading and sorry for my english

Before you can use backup files, the first step is to switch from 9008 to 9006 mode. Does it work for you?

Would you be able to post the Kingstone's production date, the four digits...

:fingers-crossed:

aungmyoswe · Feb 12, 2016

k23m said:
Before you can use backup files, the first step is to switch from 9008 to 9006 mode. Does it work for you?

Would you be able to post the Kingstone's production date, the four digits...

:fingers-crossed:

Photo Here.....Kingstone emmc

k23m · Feb 12, 2016

aungmyoswe said:
Photo Here.....Kingstone emmc

Great shots, thank you, but the date code is under the sticker. If you intend to claim warranty, do not remove it.

Another user reported code 1244 meaning the end of 2012 while still working Kingstones are (so far) from the middle of 2013. It would be interesting to know if there is a pattern here - maybe a bad batch from 2012 only?

[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Attachments

Senior Member

Member

Senior Member

Attachments

Member

Senior Member

Similar threads

Top Liked Posts