yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] MochiMochi91:
Hello everyone. I see this thread is still mostly active after all these years. I follow it every year or so to see if progress is made. I see there's been quite a bit of success but alas I am not finding it for myself.

My Nexus 32gb Wifi was a victim of the famous update that bricked many devices back in 2016 or so. This device is hard bricked af. No light when charging, no screen, nothing. It's a brick. However, it does get recognized as Qualcomm 9008 in my device manager which seems to give me false hope.

I did follow the first page for this issue:

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

and the problem I have is this seems to only work for a soft-brick. After flashing with MiFlash (and waiting for 6 min) the box disappears and I move onto the next step of running "debrick-flashall.cmd". This fails to recognize a device. I tried to run the extra steps but it seems I need to have access to fastboot already:

boot it in fastboot mode (power+vol-)

if necessary for fastboot, install Google USB Driver

from the service ROM folder check for: fastboot devices

run "debrick-flashall.cmd" (ignore error messages)

I cannot get past this part. Now I do see some motherboards on ebay I am possibly willing to try and install myself. I am moderately experienced with fixing my own devices but far from an expert. Is this the recommended path I should take? I really wish I could get access to the data on this tablet as I had nothing backed up and the ability to gain access to it would bring me a level of unimaginable joy.

Thanks for all the work you've all done to get this far.
[Nexus 7 (2013) Q&A] Sam Nakamura:
Mine went completely broken too, thanks to the Kingston EMMC it wasn't recoverable by any means, so I opted for a new 32GB board from AliExpress, luckily it was a Hynix EMMC this time and installing the hardware itself wasn't hard at all and neither expensive, my 32GB board (N7 2012) was around 20 Euros including shipping! A rather good investment for me personally as I since repairing it a year ago I used it almost daily...
[Nexus 7 (2013) Q&A] n7br:
Hi all, I made a mistake when I was trying to increase my Nexus 7 2013 system partition. Now my tablet is bricked - the screen is completely off. I'm following the unbrick guide #199 but I cannot flash the service rom. The USB\VID_05C6&PID_9008 "Qualcomm HS-USB Diagnostics 9008" device is already registered on COM5 but I got the following error from MiFlash : "cannot receive hello package. MiFlash is trying to reset status!" Does anybody got the same error? I'm using Debian and executing the procedure under a Windows 10 Pro VirtualBox VM.
[Nexus 7 (2013) Q&A] k23m:
Hi, a while ago I simulated eMMC failure by cutting off its power supply track - N7 entered 9008 mode and the unbricking procedure initially worked but ended just like your attempt. While eMMC data can be recovered from most of read-only-broken Kingstons by using off-circuit chip reader, it is rather impossible when 9008 mode can not be fixed by MiFlash. You can replace either the chip or entire motherboard. There are plenty of success stories reported in this thread. Good luck!

:fingers-crossed:

I've never tried it in VB and can only speculate that the serial port "forwarding" is faulty or incomplete between the host and guest. You can image the W10 guest into HDD and run it directly on your PC. It will run long enough ;) to complete the flash. Another option maybe worth trying is a WinPE disc/usb.
[Nexus 7 (2013) Q&A] MochiMochi91:
I appreciate all the quick replies! I figured I'd be waiting years again lmao. I'm going to go ahead and purchase a MB and see what happens. I can't stress how thankful I am for the replies and if I get it working I'll definitely report back with my results in hopes to bolster some hope in other users having this issue.
[Nexus 7 (2013) Q&A] n7br:
Thanks for reply. Unfortunately I could not find a quick solution yet. Maybe I should go to the longer way as you suggest once I cannot contact anyone who uses native Windows - COVID-19 measurement makes this harder. Fortunately or unfortunately I do not have Windows installed in my system however for this case it would save me time. :(
[Nexus 7 (2013) Q&A] Kaar3l:
I bought a Nexus 7 16GB with broken screen for this upgrade purpose.

Desoldered the old chip. Used flux and everything. It wants a lot of heat to come out. That was pretty scary to get it off. But I got it off without any problems.

I soldered the old chip to the usb adapter that I got from aliexpress. To my amazement it worked. I have not been soldering any of the chips with solder balls, only changed some router flash and memory chips with the usual metal "legs".

Now I wanted to put a new chip to the Nexus motherboard. I bought H26M780038FR, that I soldered on the motherboard but the MiFlash gave error not connecting to the chip or something like that. I desoldered that. I think the problem was my bad soldering.

Next I bought SDINADF4-64G. I removed the other chip cleaned everything and tried to solder this on the motherboard. Powering up and using MiFlash again an error. So I gave up for a bit. It sat here 2 weeks and now I thought lets remove the chip and I will wait for the BGA balls and kit to arrive. Luckily I didn't remove the chip, because I had an idea on mid removing that maybe I should nudge very-very-very gently the chip and press on it very-very gently that the chip makes contact with all the solder balls. Now I reflowd chip with nudging and MiFlash didn't give any error. Then tried to boot to fastboot and the screen is on showing: flo 64G.

Thank you very much for a super helpful thread.
[Nexus 7 (2013) Q&A] k23m:
I checked it in a WinPE booted from USB flash drive on a PC without any HDD/SSD. MiFlash installs OK and seems to work, have a look at the attachment -, N7 registers as COM10. I've not tried to re-flash it though. PM me if you need more info.

This is a great success report, and another 64GB flo!

:victory:
[Nexus 7 (2013) Q&A] k23m:
Hello n7br, I can assure you that the Win10x86 WinPE works but I also noticed those "Reached the end of the file" errors and had to restart ALL: WinPE, N7 and MiFlash. Also re-try it on USB2 or USB3 ports. Follow these steps:

install MiFlash

turn off N7 (nothing in device manager or lsusb)

when off press all 3 buttons for 2 seconds

plug in N7 to PC and wait a few seconds

in MiFlash refresh then browse to the data folder and start flashing

after around 88 seconds MiFlash shows some irrelevant errors

flashing is finished, fastboot mode is now available

press POWER + VOLUME DOWN until fastboot mode is displayed (around 10s)

I attached my logs and screenshots.

Good luck!

:fingers-crossed:

BTW, re your original issue with manual repartition - check my "Non-destructive repartition script".
[Nexus 7 (2013) Q&A] n7br:
Hello k23m, I tried several times already the steps you mentioned without success. Then I figured out an icon under WinPE environment to login as admin. So I changed the login and tried all steps again. Suddenly everything worked on my first try as admin!!!! WOW!!!!! Finally my N7 is unbricked and I have access to the fastboot. This is incredible!!! Note: I tried before execute all step by "run as administrator" with normal account and did not work. Somehow the login as admin was needed. Well it's working now and I'm using the Restock rom. It's really nice! There is only the basic apps installed and the performance is much better than LineageOS.

Thanks again k23m for your help and great job with Restock! :victory:
[Nexus 7 (2013) Q&A] Kaar3l:
Well now I tried to reflash timurs kernel and everything went haywire.

I made twrp backups, copied them to computer.

Then I flashed stock flo 6.0.1. Then formatted userdata. After that I couldn't put anything on the userdata partition. Okay I thought something messed up partition table. Then tried to wipe everything from twrp. BTW I used twrp emmc 5.1 mod. I couldn't wipe everything even with dd command.

Then I thought that I would do debrick guide. Okay got MiFlash do it's work but when starting fastboot it still has the newer version, not the old version that would come with debrick.

It seems my chip has gone to read-only? Very weird behaviour.

Before that I only messed with software, didn't touch hardware.

Did I mess up something really bad or how I cannot flash anything. :(

Could anyone give some advice to try something?
[Nexus 7 (2013) Q&A] k23m:
Please post the output of:

fastboot format userdata

fastboot format cache

fastboot getvar all

fastboot oem gpt-info
​

Next, download get-logs.zip

As logs can not be saved on your userdata, get an OTG adapter and a FAT32 flash drive.

Run MiFlash and flash as usual but when flashing is finished, do not proceed with "debrick-flashall.cmd".

Press POWER + VOLUME DOWN until fastboot mode is displayed - can you see the old v3.12 bootloader?

Then run from the 'unbrick' folder...

fastboot flash gpt gpt_both0.bin

fastboot boot twrp.img​

Transfer 'get-logs.zip' to TWRP and install it within 3 minutes from booting TWRP - 'logs.tgz' will be saved on the flash drive, post it here.
[Nexus 7 (2013) Q&A] k23m:
Yes, it is entirely read-only, presumably MiFlash also produced only errors. You reported a soldering issue before and it seems still unresolved, or perhaps excessive heat had shortened the eMMC's lifespan and then it failed permanently during OS re-flashing which involves major NAND re-write.

Before you unsolder it please boot TWRP, connect it and on PC run: adb shell dmesg > dmesg

then compress and post it here for our reference. Thanks in advance.
[Nexus 7 (2013) Q&A] Kaar3l:
I had two USB OTG cables. One didn't do anything but tried the other and managed to pull logs.tgz.

Yeah I might have fried the chip. In a few days I try to reflow and test if it's in read-only again. Then I'll try next chip. :)
[Nexus 7 (2013) Q&A] Kaar3l:
Added dmesg. It doesn't look pretty. :D
[Nexus 7 (2013) Q&A] Kaar3l:
I received a new chip SDINADF4-128G.

Soldered it on and it works fine. I tried not to cook the chips so much as last time. :)

Fastboot shows Variant unknown. I have not tried to copy the chip full yet.
[Nexus 7 (2013) Q&A] k23m:
Please check the variant again, now with fastboot/bootloader v4.

SDINADF4 is eMMC 5.1 - are you using the special software or your own build?
[Nexus 7 (2013) Q&A] Kaar3l:
I installed the 5.1 modded software and it is working like charm. But I wanted also Timurs kernel, so I compiled the Timurs kernel sources with the emmc 5.1 fix and it seems to be working like charm. I use the tablet in car to play music and for gps.

It shows unknown variant, but thats not a problem. The tablet works good.
[Nexus 7 (2013) Q&A] vanzan:
Thank you for the helpful information in this thread. I purchased a N7 on eBay that was listed as "stuck on Google". Foolishly I thought it would be an easy fix. Anyway it was a Kingston and I have ordered a replacement motherboard. Live and learn.

Incidentally I have another Nexus 7 working fine and with TWRP and aosp Ext v7.3 (Android 10). Is there a super easy way to tell if it has a Kingston too? The SD Insight app is not compatible.

Edit: partition[30].size was 256000KB so not a Kingston I hope.
[Nexus 7 (2013) Q&A] echow2001:
I can replace the emmc if you send me the bricked board. got too many flash chips from a lot of liquid damaged chromebook i got in a while back. it might take me a while to get to it since im quite busy but yea id be happy to bring your dead board back to life
[Nexus 7 (2013) Q&A] vanzan:
Very kind offer but I've already disposed of the old board. I booted into TWRP on my working Nexus 7 and ran dmesg and it seems I've got a Toshiba so a bit of good news.

Also I've just noticed that if I'm ever buying another Nexus 7 I should probably try to stay away from the 32GB variant. Since it seems the 16GB is always a Toshiba.
[Nexus 7 (2013) Q&A] k23m:
Yes, we've never seen a 16GB Kingston. As for 32GB models, look for units with charging/USB faults, they are very easy to fix. If it happens to be a still working Kingston then no worries, it may work forever as long as you don't flash new ROMs or do a lot of data rewriting.

:good:
[Nexus 7 (2013) Q&A] tinOFbeer:
Can you share the modified Timur Kernel?
[Nexus 7 (2013) Q&A] Kaar3l:
I am not 100% sure that it was that file that worked.

If it doesn't work I can get the working file from tablet.

https://mega.nz/file/U0QQ1bjK#ftocaflwqN8e2rO5wNL5ChUItXFbdD4JuM-7hbkePUA
[Nexus 7 (2013) Q&A] tinOFbeer:
Thanks a lot. At the moment I have no way to check because I am just looking for a new 64gb memory. Maybe someone has a trusted seller from aliexpress?

Wysłane z mojego GM1910 przy użyciu Tapatalka
[Nexus 7 (2013) Q&A] GekkePrutser:
I have one flo that's currently in a state where it doesn't even register itself to the PC with the Qualcomm Vendor/Device ID :( I have 2 that I was messing with partitions with (in order to install Android 10 LoS 17.1). On the other one I messed up the partition table and I was able to get it back with MiFlash as per this thread. Thanks so much for the instructions!

But this one was working today before I messed with the partition table. I tried to zero the partition table to get it into the qualcomm 9008 recovery mode like the other one but now it just doesn't show up as any kind of USB device at all. Is there any way to force it into this mode? I tried lots of different button pushes so I guess not :(

PS It's the 32GB model with Hynix chip and it was working fine before I started messing with it so the flash should still be good. It's definitely not the cable either as I used the same cable with the working one (which ironically has the Kingston chip :rolleyes:)

@k23m May I ask which track you cut to fake the eMMC failure? I wonder if this'll work for me as the flash itself should be OK. I'm wondering if I cut the trace, then connect the battery so it goes into 9008 mode, then reconnect the trace with a drop of solder, I may be able to flash it.

I also tried disconnecting the battery but that didn't work :( Also don't see any JTAG on the board sadly.
[Nexus 7 (2013) Q&A] k23m:
Use sysrepart-max.zip next time. It safely creates 1.3GB 'system' partition without erasing anything on your tablet. More info here.

Two methods

1. all 3 buttons are pressed for 1 sec, or

2. disconnect USB, press both vol buttons and simultaneously plug in to a PC

it's the IC's power track

JTAG is there but it is no longer needed. The unbricking guide shows a much easier way.

🤞👍
[Nexus 7 (2013) Q&A] GekkePrutser:
Thank you so much for the detailed info!! I'm sure I will get it to work with this.

Edit: It worked, @k23m , thanks so much for your help!
[Nexus 7 (2013) Q&A] kviperr:
Hello! i have nexus 7 2013 lte! I change emmc 5.1 but my tab not work! Take me link for mod rom for nexus 7 2013 LTE.

sorry for my English
[Nexus 7 (2013) Q&A] Aprate:
Hello,

My nexus 7 2013 16Gb finally broke down :( it wont boot past google logo, fastboot will sometimes work but othertimes its stuck, nothing will boot / everything will successfully flash. Also tried the unbricking guide which also didn't help. So it should be the nand right?

After some seaching i tried a samsung partner, and guess what they have chips in stock. Will this chip also work on the nexus 7 2013? KLMBG4WEBC-B031,32GB,FBGA,153P Could not find any 169p 32Gb FBGA chip at the samsung partner.

my tablet most likely has a kingston chip, dont know how to check that for certain, but based on the partition size it has to be.

partition[30].size 13029359 KB
[Nexus 7 (2013) Q&A] k23m:
Try this:

- get the generic 5.1 kernel

- with "Android Image Kitchen" and the above kernel modify twrp-deb.img and Stock/ROM boot.img

Please get RESTOCK then run relog.bat and attach "relog-xxxxxx.zip" to your post.
[Nexus 7 (2013) Q&A] Aprate:
Will do thanks!

@k23m i have run relog.bat and attached the zip file.

twrp is flashing and booting, only now the touchscreen is not responding.
[Nexus 7 (2013) Q&A] k23m:
Firstly, don't worry about your eMMC, you have a solid Toshiba "MMC_NAME=016G92" (y)

Your log...

<3>[ 24.211944] elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_recv_data: i2c_master_recv error?!
<3>[ 24.212432] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183
<3>[ 24.212707] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected

ELAN, the touch control IC, generates an error and stops/slows the boot process. It is very easy to fix.

However, I note a second problem. One of the newest ROMs you tried, LOS17.1 maybe, had messed up some data on the 'persist' partition. Again, no worries, I attached a fix for that - install it from TWRP. Stock ROM will be stuck on boot logo without the fix.

Cheers!
[Nexus 7 (2013) Q&A] Aprate:
Oh, many thanks! I'll try to get my tablet up and running again. The tablet crashed after having repartition and Los 17.1 for a month.

It Boots again! Still dont know why it wouldnt flash the first time i tried... And because of the fix you included it booted. Now i can flash custom again!

Cheers!

@k23m might it be wiser to flash my persist.img backup instead of the fix ?
[Nexus 7 (2013) Q&A] MasterFISHER:
Spoiler content hidden.what am I doing wrong? file size 0 is confusing. Is it a dead memory?

Google Translate
[Nexus 7 (2013) Q&A] k23m:
The first time you also had the primary hardware problem, I guess...

Yes an old, clean backup of persist image would work too but in this particular data corruption context, the fix is equally effective.

(y)

Why are you unbricking? I note that many people do it unnecessarily. The only valid reasons are:

new eMMC chip

damaged bootloader

corrupt GPT

Anyway, when I simulated "no-eMMC" by cutting off its power supply track, I got the same write 0 error...
[Nexus 7 (2013) Q&A] Aprate:
Los17.1 is up and running again. The connector might need to be reseated more often probaby. Did this multiple times already. Might use a little tape on it lol.

And to comment why people use the unbricking tool, in my case i thought the emmc was dead. Tablet did nothing but giving me errors no matter what i did. But a few days later no problems at all anymore. Thanks to you :)
[Nexus 7 (2013) Q&A] jasonnewland:
My PC sees the Nexus 7, Restock sees the Nexus 7, but restock seems to fail when it tries to send the bootloader to the Nexus 7. What am I doing wrong?
[Nexus 7 (2013) Q&A] k23m:
How Restock fails?

If "FAILED (remote: failed to write gpt)", eMMC needs replacement.
If "FAILED (remote: flash write failure)", eMMC needs replacement.

Like this? Then, the reason is clearly stated.
[Nexus 7 (2013) Q&A] k23m:
Hello! Thank you for a very detailed report. MiFlash works for sure and there is no need to struggle with adaptation (if even possible) of the other solutions for N7 unbricking. I attached a log of a no-or-bad-eMMC flash - your logs do not seem to indicate chip failure. Let's see how your x86 flash goes.

Note:

USB port fix

new daughterboard issues
[Nexus 7 (2013) Q&A] SomeSauce:
Hi,

I tried to do it on another machine using WinPE x86. After many uninteresting failed attempts, I found a really intriguing one that also worries me a bit. It looks like it "crashed" while flashing something: it ended with an "unspecified error". I didn't reboot nor unplug my tablet and computer for precaution. The log is attached. Please tell me what would be the wisest to do, thanks!

Update 1: Found that the error code of the "unspecified error", 0xc00cee61 meant that XMLLite's parsing/generation failed because of an "Illegal qualified name character". After poking around in the MiFlash exe, I found out that it does use the XMLLite.dll library! Now, what is this illegal name character? I have no clue.

Update 2: Yup, it reads XML, but I'm a total potato at decompiling so I can't explain where the xml comes from.
[Nexus 7 (2013) Q&A] k23m:
Your log has no "Catastrophic failure" entries like on the above, known bad eMMC log but it does stop or fail at the very first flash write attempt. I attached a complete 'good' log. Hopefully your issues have something to do with MiFlash run environment only.
[Nexus 7 (2013) Q&A] SomeSauce:
Great to hear, thanks for the log. Besides, this error seems to be internal from MiFlash as a google search with miflash and the error code yields absolutely NOTHING! I'll retry another flash, dump the memory and sniff the COM communications to see if there's any XML in there.
[Nexus 7 (2013) Q&A] SomeSauce:
I tried on many different computers, usb ports and everything, and still got the same results :(.

Do you think that I can try to use this tool: https://tarciodownload.blogspot.com/2017/01/tool-studio-emmc-download-tool-flash-as.html to solve my problem?
[Nexus 7 (2013) Q&A] k23m:
Nexus 7 2013 Unbricking Guide for Windows 10 x64 - revised and simplified

If your tablet can boot in fastboot mode, you do not need it.

unpack

N7-MiFlash-min.zip

install MiFlash/MiPhone

turn on and connect N7 to PC

new "Qualcomm HS-USB Diagnostics 9008" device will be registered

install the driver from

Win10-x64-VID_05C6&PID_9008-v2.1.0.5.zip

run MiFlash

click Refresh, note a new device on a high COM port number

click Browse and go to the N7-MiFlash-min folder

click Flash (see attachments)

when flashing is finished after 85 seconds, power N7 off

boot it in fastboot mode (power+vol-)

run RESTOCK, ignore errors and do "Restore original partitions"

Note

- on a new blank eMMC, stock ROM will be stuck on the boot logo. Format the 'persist' partition and flash k23m-persist-fix2.zip using: fastboot boot twrp.img

- Nexus 7 2013 Unbricking Guide for Linux and Mac OS X

- the original guide

🖥️🖱️​
[Nexus 7 (2013) Q&A] k23m:
No, it works only with a newer generation of devices. I've just posted a new unbricking guide for Win10-x64 which you could try directly from your PC without any WinPE USB booting.

The only problem with running the old MiFlash on x64 is an unsigned driver. I extracted a better driver from MiPhone20160401 and attached it above. You will also find there fresh Win10-x64 logs.

🤞
[Nexus 7 (2013) Q&A] SomeSauce:
Thanks for the files! I tried once more using your instructions (I uninstalled the old drivers and installed the one you gave) and, unfortunately, it yet again didn't work. I also tried swapping the USB cable with another, as well as USB ports, but no dice! Why is my device resilient to repairs??? Also, my device sometimes appears as "USB\DEVICE_DESCRIPTOR_FAILURE", the issue randomly disappears after a reboot or an USB port change.

I attached the logs, and here is a video of MiFlash running, so you can see how much time each step takes.

Thank you for your help!

UPDATE: I got a much more interesting log when running MiFlash on another machine. The log is attached as "special_log.log", and there is a brand new error code: 0xC00CEE04. It again seems to be related with XMLLite, and describes an "Unrecognized input signature." The general issue seems to be revolving around XMLLite for some reason.

UPDATE 2: Yup, it's always the same pattern: "StreamWrite address 00000000, size 40960", "Open serial port "\\.\COM20"", "Send configure command", and then it stops with the 0xc00cee04 error.

Do you have any tools other than MiFlash to try? I think it would be useful to try some, so we get more detailed information