yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] DaWeIII:
My emmc chip is Kingston for sure, I've checked out on the past days. Gonna check the fastboot format cache command, but I'm pretty sure it stucks at "Formatting cache..." just like format userdata would do (i've got Locked bl) so I cannot unlock BL too.

I must say, that when the device is in 9006 Diagnostic mode, the QPST manager still shows i'm in Download Mode. Also, the USB Storage shows on DiskManager when device is on 9006 Mode, not on 9008 (I was wrong).

I've got another Working NExus 7, so if I can help with that, just tell me.
[Nexus 7 (2013) Q&A] k23m:
May I ask you to save and post CODERAM from the working unit?

We tried but it seems impossible on working N7s.

If you are successful then please also describe the process.

:highfive:
[Nexus 7 (2013) Q&A] DaWeIII:
I'll try in the next few days. I'll tell you something if I can get the file from the working one. May I ask what is inside this file? And why is important to get one from a working unit?
[Nexus 7 (2013) Q&A] HTC Tytn user 188:
I got Nexus 7 2013 LTE model from my brother. He used it mostly for Wifi hotspot until one day it updated itself and stuck on google logo. I was losing my hope and throwing this away until i found my way this thread couple of minutes ago. I have tried everything i know and nothing works because bootloader is locked and options are very limited because ADB is not working. He never put it on when device worked. I got gpt-info on attachment.

I was seriously mad about this situation but now i feeling little bit better because Finland have very tight requiments about products so i think if someone else made Asus fix their device i can too. My only worry is that my brother opened device using too much force and bit of glass is broke from corners and Asus will be using it on reason why device is broken. At least he did not screw anything because seal stickers are still on. Before he opened it device was almost mint condition because he always used screen protector and case. What are my next steps? Can you see anything from my attachment? I have wasted hours in couple of weeks trying to get this work.

EDIT: This is what it says when trying to factory reset or reset cache: http://aijaa.com/NHkkNa

EDIT1: I cant install the qualcom drivers. It says it cant find some file when trying to install drivers. Old drivers installs but then it says: Nak response received (1536): Unknown NAK reason Code
[Nexus 7 (2013) Q&A] k23m:
It's sort of like S.M.A.R.T. diagnostics for HDD or SSD. There is no documentation and we have to reverse-engineer it. Current assumptions are inconclusive without a CODERAM sample from a working unit:

PBL_FLASH_DET_OR_RW_ERR,	0x1	(expected 0x0 in working units)
PBL_FLASH_TIMEOUT_ERR,	0x1	(expected 0x0 in working units)
PBL_LOAD_RPM_SBL_ERR,	0x1	(expected 0x0 in working units)

In short, it is Primary Boot Loader's log of eMMC condition.

I note that you have a Kingston eMMC chip which, if you look at the statistics, has horrible reputation.

Please run the fastboot format cache test. The normal output 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

It takes only a second. If your unit freezes there, the eMMC chip is faulty and needs to be replaced.
[Nexus 7 (2013) Q&A] HTC Tytn user 188:
It freezes there. I will contact Asus now and add this topic to my reclamation.
[Nexus 7 (2013) Q&A] Snoob25:
do you still need a CODERAM from a working unit? As far as I remember i have a Kingston chip, if necessary all install driver and stuff and I'll check and grab the coderam!
[Nexus 7 (2013) Q&A] k23m:
You should get a full refund or free replacement regardless of your warranty status because it is clearly a manufacturing fault when defective Kingston chips are used in production. The Kingstons had been failing from day one of Nexus sales back in 2013 and then they supposed to issue a total recall immediately. Instead, the internet is full of N7 eMMC failure horror stories starting 3 years ago and still ongoing. Well, be prepared for denials, quotations and costs.

Absolutely, thank you in advance and don't forget to describe the process as I'd like to try it too (again).
[Nexus 7 (2013) Q&A] Snoob25:
I can't get the file, I followed OP instructions, qcom 9008 mode is recognized correctly, memory debug app recognize the correct COM port, but still i get this message

Tried different usb 2.0/3.0 ports, different cables, by using a usb hub the error was something like a null pointer. This is on a windows 10 x64 machine.

Now I'll google about the error

EDIT i'm seeing the posts from r&d thread, as far as i understood mode 9006 is needed, at the moment i could get it loaded
[Nexus 7 (2013) Q&A] HTC Tytn user 188:
I contacted Asus but seems they are refusing to do anything. Allways a diffrent explanation but result is allways the same that they think they are not responsible. I understand device is old and took while to get to know what is broken with device but they should repair them for selling faulty items in first place. Have the Asus admitted the problem in any part or kingston? Im looking some evidence i could use against them. Anything that could help would be nice. I dont even care the tablet anymore but im angry to see big company selling **** and internet full of people wasting time to repair their problems.
[Nexus 7 (2013) Q&A] VintageGrace:
Does anyone have the chip or is there somewhere I can buy individual chips?

Links?
[Nexus 7 (2013) Q&A] k23m:
Yes, I too get "Unknown NAK..."

They used cheap Kingston chips and now avoid responsibility. I wrote earlier: "Unlike fabless Kingston, Hynix actually produces NAND flash memory. Kingston is known for repackaging B-grade chips of reputable manufacturers and bait-and-switch sales". I wonder if Google's decision to abandon the Nexus brand and ASUS as a manufacturer of their new products had something to do with Nexus 7's unreliability.

https://www.aliexpress.com/wholesale?SearchText=32gb+emmc

More specifically, 32GB FBGA169 VCC=3.3V, VCCQ=1.8V/3.3V, eg:

Samsung KLMBG4WEMC, KLMBG4GEAC

Hynix H26M64103EMR

Note, if you use eMMC v5.0 you will not be able to use Android older than 6.0 without a kernel tweak.

Also, there is no firmware "flash" for N7 and you will have to use either hardware eMMC programmer or JTAG.

Keep the above in mind before purchasing a replacement chip.
[Nexus 7 (2013) Q&A] republicano:
Nexus 7 2013 Manufactures date 2014/12

(bootloader)	partition[30].size 13029359 KB

Toshiba 16GB
[Nexus 7 (2013) Q&A] jorgeg73:
Did you had any luck whit Asus? having the same problem
[Nexus 7 (2013) Q&A] HTC Tytn user 188:
i am fighting against Asus at the moment. Waiting consumer authorities to making their desicion at my case. I offered them deal that they only ship me spare part and i change it myself etc. but they could not do that because they can only send items to b2b which is just excuse.

Asus customer support is very bad compared to many other companies and i suggest to avoid Asus products because of that. It should be easy thought because these days most of their products are bad quality anyway. Be in contact them thought. In your country there might be better people working than here.
[Nexus 7 (2013) Q&A] jorgeg73:
Yes I also had problems whit them in the past had a zenfone 2 z008 and in 4 months stop working Sent it back they were charging 400 for 200 dlls phone I don't remember there excuse..
[Nexus 7 (2013) Q&A] jaybea:
Add another failed 2013 version (purchased in June 2015) to the list - Kingston eMMC according to the Fastboot oem gpt-info command:

(bootloader) partition[30].size 27852783 KB

It won't boot past the Google logo, and it hangs on Fastboot Format Cache. It is locked and has a bootloader version of FLO-04.08. It is running Android 6.0.1

I have sent off a support request to ASUS. Since I am from the UK, I have quoted the Sales of Goods Act 1979, since the failure of a tablet after 18 months of light use means that it is not of "satisfactory quality and fit for purpose". Nothing ventured, nothing gained...!
[Nexus 7 (2013) Q&A] k23m:
Thank you for the report. "EU law gives you a free 6-year warranty" - no worries here :laugh:
[Nexus 7 (2013) Q&A] NTRNSTR:
I was able to use it to unbrick my tablet using this image.

My nexus 7 wouldn't turn on at all and when I plugged it in to a computer it was recognized as Qualcomm HS-USB diagnostics 9008. When I opened it up I saw that the chip was manufactured by Hynix so I downloaded the image and booted the device into 9006 mode by holding volume up and power while it was plugged into the computer (It showed up as Marshall London HS-USB diagnostic 9006) and the flash storage showed up as Qualcomm mmc device. I then used HDD Raw Copy Tool to write your image to the Qualcomm mmc device and when it finished I was able to boot into fastboot:victory:.

I then flashed a marshmallow factory image but the device wouldn't get past the loading animation no matter what I tried so I decided to try an older version and so I flashed an old jellybean image and to my surprise it actually booted:D. I then came across this guide https://xdaforums.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 which said it was an issue caused by a broken persist partition so I used TWRP to wipe it using:

adb shell
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist

Then I rebooted it into the jellybean rom to let it rebuild the partition and finally flashed the marshmallow image which was finally able to boot:victory:.
[Nexus 7 (2013) Q&A] k23m:
It is a great success story in this thread dedicated to bricked eMMCs :)

As for the image file you used, I erased the persist partition too because it is not strictly essential. Cyanogenmod, Ubuntu Touch and other custom OSes do not depend on it. I think stock ROMs bootloop because they can not find DRM files stored on the partition.

Also, while I made the image from 32GB Hynix, it should restore boot on any other, including 16GB, eMMC flash memory, but it will require some file system adjustments later.

Congratulations :good:

Cheers :highfive:
[Nexus 7 (2013) Q&A] NTRNSTR:
That's good to know:) could you explain the file system adjustments that would need to be made please, just in case someone else isn't lucky enough to have a hynix chip in theirs.

I really can't thank you and [MENTION=4959164]fuser-invent[/MENTION] enough for your hard work in these threads., If it weren't for you guys I definitely wouldn't have been able to fix it.
[Nexus 7 (2013) Q&A] k23m:
Only userdata's size is different (smaller) on other flash chips, so in TWRP unmount data and go:

wipe - advanced wipe - select data - repair or change - resize...​

How did it happen? Did you damage the bootloader or partition table?
[Nexus 7 (2013) Q&A] NTRNSTR:
I honestly have no idea, the device was previously running stock Android marshmallow, it was never rooted, unlocked or tinkered with in any way. At some point it stopped being able to install updates (it would reboot and begin the installation but would end up giving an error and rebooting)but otherwise continued to work just fine. The screen was cracked so it was just being used as a clock at that point, but one day it shut down and when I tried to turn it on it just wouldn't boot.

Thankfully it's fixed and running lineage now and I just have to wait for a replacement screen to arrive:D
[Nexus 7 (2013) Q&A] vfrvulcan:
Did you get anywhere with this?

I have the exact same problem. Fully stock, still locked. Kingston eMMC which I only found out by tearing it down so (attempted) bouncing to Asus may be an issue.

I couldn't get it seen by fastboot drivers but came up with the Qualcomm 9008/9006. I tried to backup the eMMC using HDDRawCopy as mentioned above but it wouldn't read the eMMC. Likewise, trying to write the clean image fails.

Amazingly after trying the 9006 stuff it now appears in device manger with fastboot drivers. Unfortunately fastboot erase cache or fastboot format cache just hangs. Then I tried fasboot boot twrp.img (from NRT), that complained about the locked bootloader so I tried unlocking it but just hangs on erasing userdata.

Any ideas to try and get some (more) life back into it?

Why is it the only device I've never rooted or changed from stock decides to be an @$$?!?
[Nexus 7 (2013) Q&A] jaybea:
No, ASUS were not at all interested and said to take it up with the supplier. I got it from Amazon, and I could try to pursue it through them, but it was simpler to get a Samsung tablet for family use to replace an aging Ipad2 and avoid Asus devices in future.

I did not feel the need to root mine either, as it was good with stock.
[Nexus 7 (2013) Q&A] k23m:
Thanks to your experiments we know now that it is possible to restore fastboot on broken Kingston. Unfortunately nothing more can be done on faulty hardware.

I just searched for it on eBay and note a number of offers including this $30 cheap mobo. While I would not be concerned about the smaller 16GB version, I would ask the seller for a non-Kingston unit.
[Nexus 7 (2013) Q&A] tito_puente:
Since 2013 I'm using my Nexus 7 flo with the stock rom. Now I want to flash a nougat rom and have read about the brick problems. I just checked my internal storage. It seems to be from the manufacturer hynix.

Am I save to flash a custom rom? I have read the first post an it seems that only devices with Kingston AR dangerous to flash?
[Nexus 7 (2013) Q&A] TechnicsKuzya:
I successfully replace 2 Kingston chips (at the 2 tablets) by:

THGBMBG8D4KBAIR (EMMC 5.0)

THGBMFG8C4LBAIR (EMMC 5.1)

Repair bootloader with the MiFlash and engeneer ROM, now I can install engeneer ROM 4.2.2, Android 5.1.1 (razorg-lmy48z-factory-9a4845b2.zip) and 6.0.1 (razorg-mob30x-factory-10b7ca08.zip), but can`t official 4.3-4.4.4 it bootloop at "Google" screen? Why? Because EMMC 5.0 and EMMC 5.1?

What about IMEI how I can change it to the legacy for the tablet, now I clone my worked device and all 3 tablets have a same IMEI!? :(
[Nexus 7 (2013) Q&A] k23m:
Sorry for late reply, I missed your post . Yes it's safe but backup your data anyway.

Congratulations, replacing eMMCs chips is no easy task! Did you use a professional BGA rework station or homemade gear?

Android 4 and 5 will not work with eMMC 5.0/5.1 unless the kernel is recompiled with a simple, single-byte mod in drivers/mmc/core/mmc.c. Android 6 will not work unless you have also cloned the 'persist' mmcblk0p4 partition. Go to my collection of N7 stuff and copy p4.zip to backup and p4-restore.zip scripts. They work from TWRP 'install' with OTG flash drive as backup/restore location.

I don't have info on IMEI mod but if you sell it to an overseas buyer there will be no network conflict with cloned IMEI for sure.
[Nexus 7 (2013) Q&A] TechnicsKuzya:
No, I use simple solder station like Lukey 852D+. My first BGA rework - this is not hard. ;)

Did you have Nexus 7 LTE for IMEI backup, I can give you script for backup it!? (I`m in Russia and can use other country IMEI :angel:).

P.S. I`m successfully install stock Android 5 and Android 6, but not stock Android 4.3-4.4.

---------- Post added at 04:19 PM ---------- Previous post was at 03:57 PM ----------

How I can see the log with this trouble?
[Nexus 7 (2013) Q&A] k23m:
Please check my PM message. I wish we had a similar IMEI change guide like eg Mi4c.

As for the code log, here is for example flo-3.4-jb where on line 296 the digit '6' must be changed to '7' in order to work with eMMC v5.
[Nexus 7 (2013) Q&A] TechnicsKuzya:
Thank`s a lot, I will try.
[Nexus 7 (2013) Q&A] SMARTJUAN:
Hello, first thanks for your excellent work, I will try to change my broken Kingstom chip, do not pass the Google logo and I think it is affected by the death of the chip, I would appreciate your help, for the software issue, since I am from Spain and English is not my forte, but I have experience in repairing Bga chips and tools to change it, grateful in advance, I would need a guide with what to do once I changed the chip, can I put one other than Kingstom? Better to schedule it before or once mounted I can do it later, greetings and thank you very much.
[Nexus 7 (2013) Q&A] darekpu:
Nexus 7 2013 and EMMC32G-M525

It is possible to replace bricked Kingston KE4CN5B6A (JEDEC 4.5) by new EMMC32G-M525 (JEDEC 5.1) which is somehow backward compatible ?
[Nexus 7 (2013) Q&A] barbuda:
Very infomative thread!

Another N7 reporting in, 32GB, kingston eMMC bricked (based on 1st post fastboot diagnostics), hangs on "fastboot format cache".

It was found stuck on google logo after charging it overnight, maybe overheating as well. Bootloader is still locked. I keep it factory and latest supported Android/update etc, since it's used by my parents mostly.

I read thru the entire thread, I wouldn't care much about reviving the device or replacing the chip, but more about a way to recovery user data. Parents have years of pictures and videos of the grandchildren :(. I didn't know the eMMC problem of the N7 until this happened :(. I trusted the device too much and use it as the repository for all the media for parents. I am hating myself now for now setting up auto backup for them. Much appreciate any help for data recovering.
[Nexus 7 (2013) Q&A] Snoob25:
Well, I write again in this thread.

Same here, found the tablet turned off after leaving it charging overnight, no response. 32gb kingston emmc obviously.

At first PC showed qualcomm 9006 mode, then after few unplug-replug it turned to qualcomm 9008 mode, then after another try i could boot fastboot mode, and then I verified the dead emmc chip with fastboot commands. I can boot twrp.

I have few questions:

- If I buy a nand chip and I have the possibility to use JTAG, can I use JTAG on the new chip after soldering it to the motherboard, without the need to write the new chip externally?

-If I buy a chip, can I use your hynyx emmc image ( https://xdaforums.com/showpost.php?p=69738741&postcount=135 ) on whatever brand I find?? And then just use factory images to write bigger partitions?

Really thank you
[Nexus 7 (2013) Q&A] k23m:
Thanks for your report - I'll update our statistics. I'm working on a N7'13 kernel capable of accessing read-only, broken eMMC chips, but it will not help if your bootloader is locked. If your data was

not encrypted

, then you can recover it this way:

get a heat gun

heat up the eMMC chip and remove it ASAP before it overheats!!!

send it to a data recovery service or access it yourself with an eMMC programmer (see the links in my post #1)

Good luck :fingers-crossed:

Q1 - no need to write the chip externally if you're using the JTAG "RIFF Box" which includes "bootloader repair package for Google Nexus 7 based on QUALCOMM APQ8064" - see my post #1. I note that they released v2 of the "Box", so please confirm that you will get a N7 bootloader package before you purchase it.

Q2 - I think you can use my Hynix image on any chip because the only difference is in the size of

the last

"userdata" partition which can simply be "repaired" later in TWRP. Note however that I compressed the image a bit too much by erasing the "persist" partition, which should not be a problem if you intend to use a custom ROM like LineageOS but on a factory image you will have to make a workaround.

Cheers :highfive:
[Nexus 7 (2013) Q&A] Manish54:
My Moto Z has been dead for months, the PC wont even detect it, suddenly my PC detected it and i ran the blankflash file, it gave me an error saying cant locate storage.. EMMC.... something. What can i do?
[Nexus 7 (2013) Q&A] barbuda:
Thanks for the advice. Got a quote from nearby data recovery shop, they want $400 minimum to start with. That's too much :(. I will probably just hold on to the device until I get access to a chip reader or some affordable service comes around.
[Nexus 7 (2013) Q&A] k23m:
I came across an incredibly cheap USB eMMC controller without flash memory which may work as a reader of broken Kingstons. While you can easily remove the eMMC chip from N7, soldering it to this controller is not so simple. Please get a quote for "BGA chip soldering" from an electronics service workshop, but again, this is an UNTESTED method and you may waste your time and money.

If you go ahead, note that your newly assembled USB drive will not work on Windows because it has no support for ext4 filesystem and you'll need a Linux OS. Fortunately you can run live Linux without installation on any PC.

If you, or anyone else, try the USB controller, please reply and share your observations.
[Nexus 7 (2013) Q&A] barbuda:
That USB eMMC controller is very interesting indeed! It does support the 169 pins on the Kingston chip based on my google search. I may give it a try once I confirm a way to transfer the chip to the controller with good chance for success - I have the one and only chip to play with after all :/.
[Nexus 7 (2013) Q&A] barbuda:
While playing with QPST and 9006/9008 mode, I was able to get CODERAM.BIN. Not sure if it has useful info, uploaded anyways :)
[Nexus 7 (2013) Q&A] davefiddes:
This is an excellent result. Thanks for giving some hope and really useful part numbers!

Can you share some more details on how you got your blank emmc chip working? Your post(s) imply you didn't program the emmc chip before soldering the new or connect to a JTAG programmer. If so this would be a real breakthrough.

From having read this thread and others it seems that a software based recovery programming operation should be possible once the faulty flash is replaced. It's just that the magic bit of information to bootstrap the recovery process and get the bootloader partitions re-instated to the emmc is missing.
[Nexus 7 (2013) Q&A] Dazmatic:
An idea of how to get a blank emmc chip working would be great? I'm capable of replacing an emmc chip on the board, no problem, it's the flashing that seems to be eluding me? without getting an expensive programmer (£80+) it's not really worth it considering I can just get a replacement motherboard for half that amount.
[Nexus 7 (2013) Q&A] k23m:
Here is a 4-step, $6-idea...

solder a new chip to this USB controller

write this N7'13 image to it

remove and re-ball the chip

solder it to the mobo

Yeah it's sub-optimal, but doable.

BTW, can you do "Fastboot Diagnostics" from the 1-st page of this thread or have a look the eMMC IC to confirm it's a Kingston?
[Android Q&A, Help & Troubleshooting] Konner920:
I got this nice phone for 20 bucks at walmart but i cant find any roms or recovery. i wanna make a nandroid backup so others can restore their phones
[Android Q&A, Help & Troubleshooting] Deleted member 7662912:
Here ya go XDA,maybe this will help some of you.

(Might upload other partitions later,but not today)

Download System.IMG here:

http://ow.ly/Gx8t3042SMg

Instructions Included (Requires a basic understanding of adb)
[Android Q&A, Help & Troubleshooting] xXCoolGuYXx:
So did you ever get the twrp for the coolpad?
[Android Q&A, Help & Troubleshooting] Deleted member 7662912:
Nope.