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

[arkady789]

Yes:

1. get CROSS - Custom ROM Scripted Setup
2. run repartition.bat
3. select: ultimate
4. reboot
5. install LOS18

If error, run relog.bat and attach "relog-xxxxxx.zip" to your post
and run RESTOCK with "restore original partitions" YES

Great, works, thank you for fast and Correct reply.

 

[Kaar3l]

I have the 128GB EMMC 5.1 flo device. I was running latest stock image. Now I wanted to upgrade to lineage 18.1. So I tried the CROSS script. It did something but I cannot install rom with the twrp that is for flox device. I think it might be issue with the 5.1 EMMC.
How could I compile flox twrp that would support emmc 5.1?
Do I also need to patch and recompile lineage?

 

[k23m]

I have the 128GB EMMC 5.1 flo device. I was running latest stock image. Now I wanted to upgrade to lineage 18.1. So I tried the CROSS script. It did something but I cannot install rom with the twrp that is for flox device. I think it might be issue with the 5.1 EMMC.
How could I compile flox twrp that would support emmc 5.1?
Do I also need to patch and recompile lineage?

Both TWRP and ROM kernels need the eMMC patch. They should support it by now, it is a very old issue. Ask the devs to re-compile the kernels. A really trivial change is required, a simple 1-byte mod.

 

[Kaar3l]

Both TWRP and ROM kernels need the eMMC patch. They should support it by now, it is a very old issue. Ask the devs to re-compile the kernels. A really trivial change is required, a simple 1-byte mod.

Thanks!
I tried to compile kernel but failed on the first go.
Then I cleaned everything and tried to build again and success.
I will describe what I did:
1) Installed with RESTOCK stock image. Then flashed emmc 5.1 kernel that is available in this thread. Verified that everything is working. I used the modified twrp that is available here. (twrp-3.3.1-0-flo-k2.img)
2) Then I used CROSS as I needed bigger partitions for Lineage 18.1. When using cross I used lineage-install-3-flox.bat and I didn't want the CROSS to reflash my twrp that was working with eMMC 5.1.
3) I compiled kernel and swapped out the boot.img from lineage-18.1-20210712-nightly-flox-signed.zip. As I had twrp for flo I had to change the flashing script from flox->flo, so it could flash.
4) Flashed the modded lineage. And it booted.

So the 128GB Nexus 7 with eMMC 5.1 and bigger partitions is working.

 

[jhford]

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:

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:​

1. device is totally dead
2. dead but flashes a few times the white LED next to USB port
3. dead but with active USB on PC device list
4. works up to fastboot stage or Google logo
5. may slowly boot Android sometimes
6. 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​

If your bricked unit still works in fastboot mode then please do the following tests:

1. boot the Nexus in fastboot mode (when off press power+vol.dn)
2. connect it to your PC
3. on PC run:
   
   fastboot oem gpt-info
   fastboot format cache​

You can run the fastboot app from Windows or Linux...

• on Windows get RESTOCK and run it from the 'data' folder
• or run it from live Linux

If you get "partition[30].size 27852783 KB" then your eMMC chip is from Kingston (very high failure rate).
If the format command freezes at any stage, then the eMMC chip is faulty and needs to be replaced.
The normal format output takes only 1 second and is:

Creating filesystem with parameters:
    Size: 587202560
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 7168
    Inode size: 256
    Journal blocks: 2240
    Label:
    Blocks: 143360
    Block groups: 5
    Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'cache'...
OKAY [  0.359s]
sending 'cache' (10984 KB)...
OKAY [  0.359s]
writing 'cache'...
OKAY [  0.484s]
finished. total time: 1.203s

QPST Diagnostics​

Please upload your bricked device's memory dump for investigation. Just try the unbricking guide.

• download "New Qualcomm 2012.rar"
• extract the "fre" folder
• connect your N7 to PC and when asked for a driver point it to the above folder
• download "New_Qualcomm_QPST-2.7.422.zip"
• extract it and run "setup.exe"
• run Start/QPST/MemoryDebugApp.exe
• in Memory Debug keep clicking "Browse" until you see a new COM port
• in Memory Debug click "Get Regions"
• in Memory Debug select and save "CODERAM.BIN"
• upload "CODERAM.BIN" here

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:




The above file is for RIFF JTAG flasher.

My Nexus 7 JTAG collection:

• Asus_Nexus_7.rar
• Asus_Nexus_7.txt
• nexus7 jtag.jpg
• RIFF Box JTAG GettingStarted.pdf
• RIFF Box JTAG Manager Setup v1.56.exe

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

So far I have collected the following reports:

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:

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:

This board is not the same as my deb boards. Is this a flo board?

 

[jhford]

Thanks!
I tried to compile kernel but failed on the first go.
Then I cleaned everything and tried to build again and success.
I will describe what I did:
1) Installed with RESTOCK stock image. Then flashed emmc 5.1 kernel that is available in this thread. Verified that everything is working. I used the modified twrp that is available here. (twrp-3.3.1-0-flo-k2.img)
2) Then I used CROSS as I needed bigger partitions for Lineage 18.1. When using cross I used lineage-install-3-flox.bat and I didn't want the CROSS to reflash my twrp that was working with eMMC 5.1.
3) I compiled kernel and swapped out the boot.img from lineage-18.1-20210712-nightly-flox-signed.zip. As I had twrp for flo I had to change the flashing script from flox->flo, so it could flash.
4) Flashed the modded lineage. And it booted.

So the 128GB Nexus 7 with eMMC 5.1 and bigger partitions is working.

@Kaar31. Wow. I'm impressed. Apparently you have a flo, but I have 3 debs. Would it be feasible for you to modify your step-by-step, above, so that I can upgrade my debs to 128GB, also? Much appreciated.

 

[jhford]

I just rebuilt the software for my N7 2013 deb. I was all finished the way I wanted inclukding followmis's excellent LOS 18.1 Rom, but it noticed that Magisk v.23 was apparently not installed, even though I was pretty certain that I had flashed it, also. So, I booted back into recovery (TWRP 3.4.0-0) and flashed Magisk, but the device continuously bootlooped on the Google flash screen. I hate to start all over from scratch. Can anyone help?
Thanks

 

[ipdev]

I just rebuilt the software for my N7 2013 deb. I was all finished the way I wanted inclukding followmis's excellent LOS 18.1 Rom, but it noticed that Magisk v.23 was apparently not installed, even though I was pretty certain that I had flashed it, also. So, I booted back into recovery (TWRP 3.4.0-0) and flashed Magisk, but the device continuously bootlooped on the Google flash screen. I hate to start all over from scratch. Can anyone help?
Thanks

Flash the lineage 18.1 boot image from the ROM zip.
Unzip the lineage zip file and you will find the boot.img file.
You can flash it using fastboot or install it using TWRP's option to installl image files.

That should get you out of the bootloop.

Fixing Magisk is OT for this thread.

Cheers.

 

[ZiAndoid]

Sorry guys noob here!

I am trying to fix my Nexus 7, and after alot of effort I have established that I have a faulty eMMc IC. I have found a cheap replacement FBGA 153. However one step I am not sure of is that will I still need the JTAG Box or can I just solder the blank eMMc and update it using RESTOCK.

Sorry if I have missed something which makes my query seem daft! This was all new to me 2 days ago...

 

[k23m]

I am not sure of is that will I still need the JTAG Box or can I just solder the blank eMMc and update it using RESTOCK.

Hi, after soldering a blank eMMC follow the Nexus 7 2013 Unbricking Guide .

 

[MirtaX]

Hi there, have you isp location for ME571KL or schematic motherboard? Thanks

 

[underflash]

Hey, I have used flo-deb_clamor_repartition_20201203 and then installed official Android 11 LineageOS 18.1-flox without any problems from stock ROM. Device started lagging terribly, some apps take ages to open, a lot not responding messages, tablet literally unusable. eMMC is HYNIX HBG4e // 31GB MAY 2013, I have formated and wipe it 4-5 times without any errors. Also tried limiting background processes to 4 and used fstrim.bat from CROSS 2.5. No significant change.

The only idea comes to my mind is repartition to make system partition bigger, now it is 1.4GB with 290MB free. Any other solution?

 

[k23m]

Hey, I have used flo-deb_clamor_repartition_20201203 and then installed official Android 11 LineageOS 18.1-flox without any problems from stock ROM. Device started lagging terribly, some apps take ages to open, a lot not responding messages, tablet literally unusable. eMMC is HYNIX HBG4e // 31GB MAY 2013, I have formated and wipe it 4-5 times without any errors. Also tried limiting background processes to 4 and used fstrim.bat from CROSS 2.5. No significant change. The only idea comes to my mind is repartition to make system partition bigger, now it is 1.4GB with 290MB free. Any other solution?

Hello, try the following.

1. RESTOCK restore original partitions and verify N7 performance. If all OK...
2. CROSS flox with sysrepart-ultimate and default gapps

If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.

Unless you're sure of a hardware issue, reply in CROSS' thread.

 

[telep]

Hi i have tried to use clamor repartition script, and in that process tablet got disconnected from pc, i restarted tablet, but it won't boot. I've tried to use restock but it can't write it gives error failed, i can boot to bootloader. Is there any software fix or i must change emmc?

 

[k23m]

Hi i have tried to use clamor repartition script, and in that process tablet got disconnected from pc, i restarted tablet, but it won't boot. I've tried to use restock but it can't write it gives error failed, i can boot to bootloader. Is there any software fix or i must change emmc?

Hi, double-check it with Fastboot Diagnostics and if confirmed, replace eMMC.

 

[telep]

i got this, second screenshot is from relog if it helps

 

[k23m]

i got this, second screenshot is from relog if it helps

Please post a getlog.bat log as text, not image. Also if possible, retry relog.bat from a different PC.

 

[telep]

I tried everything yesterday and it wouldn't work. This morning i tried and restock went thru first time.

 

[jhford]

I can't seem to download MiFlash. Solution?

 

[jhford]

I can't seem to download MiFlash. Solution?

Please ignore. I found it at the Xiaomi website.