yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] k23m:
Before fixing it must be diagnosed. Please confirm if I got it right - nothing ever is visible on the screen, but it boots OK, connects via wifi and if you check your Google's account on another device, it reports current sync with the Nexus, yes? If so, then clearly the LCD's backlight is faulty. You could disconnect the battery and check the "MB connect SU" cable and the other internal connector (attached) but that's all for DIY. The backlight's power converter is integrated with the LCD and must be replaced together.

Awesome news, the very first Nexus 7-2013-64GB is fully operational! Is the OS rooted? If so, please start ADB, run the commands and post your 'gpt' backup file (5kB) of the 64GB partition table:

adb shell
su
sgdisk --backup=/sdcard/gpt /dev/block/mmcblk0
exit
exit
adb pull /sdcard/gpt

It would be useful for someone in the future.

If you're asking about 64GB partitioning, 459below did it externally with gparted while the chip was soldered to a USB adapter. But it can be done manually on the Nexus in TWRP or with a script - I can modify my sysrepart.zip for this purpose.
[Nexus 7 (2013) Q&A] 459below:
Done! But it's not the only 64 GB Nexus 7 in existence. Here's a 64 GB deb https://www.youtube.com/watch?v=YdpXyen-H9U Maybe the only flo? In any case, I hope others will take this into consideration, when they choose their replacement eMMC and other 2013 Nexus 7s will rise from the dead more powerful than ever before. :highfive:

Yes, after I mirrored the old read-only 16 GB eMMC to the working 64 GB eMMC, I just expanded the userdata partition to fill the rest. AFAIK the userdata partition is always the last partition. As a side note: The tablet was encrypted at the time it broke down. After I soldered the new chip, which had been mirrored from the old one, on the motherboard, fastboot and TWRP were working, but I wasn't able to decrypt the data partition, so I had to wipe. But that's fine. I encrypted my data so that they will not be easily recoverable.
[Nexus 7 (2013) Q&A] echow2001:
Anyone got bricked nexus7 lying around? I'll pay you a lil for em/fix em&upgrade storages if you want. Just looking for bga rework/microsoldering practice
[Nexus 7 (2013) Q&A] Sam Nakamura:
I got one off of eBay for 10 bucks in perfect condition, exept it wouldn't boot beyond Google splash screen, infamous EMMC bug - so I exchanged the motherboard all together (and speakers too as they made a heavy crackling noise) and got it perfectly fixed for just 30 bucks all together. The storage on the replacement motherboard was even a Hynix 32GB, the failing one was the crappie Kingston 32GB one.

What I actually meant to say was that you probably will have more success checking eBay for defective units...
[Nexus 7 (2013) Q&A] echow2001:
5 bucks for that defective Kingston board?
[Nexus 7 (2013) Q&A] Sam Nakamura:
Well I'll gladly "donate" to you if you're interested :) just write me a private message and we can get things going...
[Nexus 7 (2013) Q&A] echow2001:
it won't let me PM you for some reason on labs app or browser, can you just WhatsApp me+1708XXXXXXX

---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ----------

im trying the USB controller on a nexus4 Emmc not dead just too small to get the EFS partition, will report in 4 weeks when it is delivered.
[Nexus 7 (2013) Q&A] Sam Nakamura:
All right, can delete the number now...
[Nexus 7 (2013) Q&A] k23m:
Thank you in advance. User [MENTION=2050626]459below[/MENTION] confirmed this https://www.aliexpress.com/item/USB...t-Flash-Memory-eMMC-Adapters/32844033399.html controller working 100% for data recovery from broken read-only Kingston chips. EFS, IMEI, user data, etc. can all be recovered.
[Nexus 7 (2013) Q&A] echow2001:
So just weld the chip on and plugin to any linux computer? Or would it have to be an Android
[Nexus 7 (2013) Q&A] k23m:
Yes, any Linux PC or live CD without installation, eg. https://www.linuxmint.com/download.php

Alternatively, you can install one of these on Windows...

https://www.diskinternals.com/linux-reader/

http://www.ext2fsd.com/
[Nexus 7 (2013) Q&A] echow2001:
Does it show up as sdX8,9,10 or mmcblk0p8,9,10
[Nexus 7 (2013) Q&A] k23m:
With the USB adapter it will be sdX. On Windows with Linux Reader it will look somewhat different....
[Nexus 7 (2013) Q&A] jhford:
Stuck on Google Logo

My deb boots to the Google Logo and stops. ADB was enabled, but not any longer. ADB Devices returns blank. I can boot into Recovery or Bootloader Mode (Power + Vol Down). Plus, I have tried WUG Fresh and the Unified Android Toolkit (UAT) to return to stock. WUG Fresh fails. The ADB in UAT works, for some unknown reason since ADB does not connect to the device natively, but the return to stock process ends with an error, anyway. I've tried UAT twice with the same result.

I don't know what else to do. The device is way out of warranty, of course. But I love it, want to fix it and install a custom ROM, like I had before it broke. That's my story, sad but true. I hope an XDA genius can help.

Thanks
[Nexus 7 (2013) Q&A] k23m:
Now we know your hardware is OK and can proceed to software solutions. If you are not concerned with data loss then just boot recovery and do Wipe data/Factory reset. If it does not help then flash a fresh factory image. If you get an error, please copy and paste it here.
[Nexus 7 (2013) Q&A] jhford:
The best I can do is to boot to bootloader mode, but when I select the choice "Recovery mode" using the Vol Up/Vol Down it takes me back to the Google logo and not to the Android menu where it just hangs. I've tried to flash a new image using NRT and the Unified Android Toolkit, but both fail. So, could you please help me flash a new image? Is there another tool that can handle this of which I'm unaware? I've have flashed so many images on this device that I can't count them. So, I'm no newbie.

Thanks
[Nexus 7 (2013) Q&A] k23m:
No worries. I need a log to see what's going on there.

go to your folder with fastboot.exe and adb.exe

download twrp-3.2.1-0-deb.img to the folder

also unzip and copy the attached "twrp-log.bat" to the folder

in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.3-0-deb.img [Enter]

when TWRP is up and running (may ask for ADB driver) and you see the menu, double-click on

twrp-log2.bat

Note, the above steps must be done withn 3 minutes to ensure complete dmesg log

then you will find a new file

twrp.txt

in the folder

zip up

twrp.txt

and attach it to your next post

Actually, as a new XDA user you may not be able to attach files or post links, so upload twrp.txt to http://pastebin.com and post only the subpage part, eg. from https://pastebin.com/9cat4t4X7 post only this 9cat4t4X7

Cheers :good:

EDIT

connect the Nexus to a PC and boot it in fastboot mode (when off press power+vol.dn) then follow the steps.
[Nexus 7 (2013) Q&A] jhford:
See attched.
[Nexus 7 (2013) Q&A] k23m:
Well, it is a hardware issue after all, but a very simple one. The log is flooded with these errors....

<3>[ 68.764282] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[ 68.783996] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183
<3>[ 68.784454] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[ 68.804016] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183
<3>[ 68.804473] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[ 68.804718] elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_recv_data: i2c_master_recv error?!
<3>[ 68.805206] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183
<3>[ 68.805664] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[ 68.806030] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183
<3>[ 68.806488] qup_i2c qup_i2c.3: I2C slave addr:0x10 not connected
<3>[ 68.824005] qup_i2c qup_i2c.3: QUP: I2C status flags :0x11100c8, irq:183

elan_ktf3k at 0x10 address is the touchscreen control IC and it is not responding. All you have to do is re-seat the wide, silver cable which goes across the battery....

disassemble it https://www.youtube.com/watch?v=IG6A_RBX-v0

disconnect the battery https://d3nevzfk7ii3be.cloudfront.net/igi/T1bQFwmsYTXKYX11.medium

re-seat both ends of the wide silver cable https://www.youtube.com/watch?v=C9PwK9eGrCY

re-connect the battery

:highfive:
[Nexus 7 (2013) Q&A] jhford:
My sciatica woke me up. ? I've done these steps countless times in the past. I live inside the device. But I'll try them, after I wake up again, and report back. But while I'm at, it and since you appear to also suffer from the N7 disease, what ROM are you running and why? I've been using Official LOS 14.1 for months, but deb is no longer supported as of last week. I just received a Fire HD 8 (8th gen) last week (Cyber Monday) and it's notably faster than the N7, albeit heavier and, of course, larger. Plus, the bootloader is locked and the XDA geniuses, like you, haven't figured out how to unlock it and probably never will without futzing with the hardware.

Thanks
[Nexus 7 (2013) Q&A] jhford:
[MENTION=7182780]k23m[/MENTION]

OK. Although the silver ribbon cable seemed perfectly seated, I reseated it, and, although it sat on the Google logo screen for a very long time, it booted. I'm in initial setup right after the Welcome screen. The good news is that it rotates, recognizes the SIM card and the T-Mobile network. However, the touchscreen is essentially unusable. It's very erratic. Some touches work, but most don't. Selecting the WiFi network is impossible. When I tap the correct one the thread for a different one appears, etc. The keyboard is the same. I had this issue before I reported the boot issue here and replaced the entire touchscreen assembly; so, it's brand new. Is there another magical test we can perform to solve this problem?

EDIT:

While waiting for your response, I tried these 3 image files, but none solved the problem.

https://tinyurl.com/y88mkdc8

I then ran boot-ts-unlock.img for return the touchscreen software to its original state.

EDIT:

I also watched one of Max Lee's videos and swapped some of the silver motherboard and daughterboard screws for black screws (I have a mini N7 parts inventory), but that didn't help either.

EDIT:

Also, I just successfully ran fastboot boot twrp-3.2.3-0-deb.img, but it didn't create a new twrp.txt file for me to attach here.

So, could it be a defective motherboard?

Attached are new versions of the 2 files I posted earlier.

Thanks
[Nexus 7 (2013) Q&A] k23m:
So you had replaced the touchscreen and then could not boot anymore. Next you post a general boot issue question without mentioning anything about the touchscreen nor the sequence of events. Then I waste a number of posts and PMs only to find out from the log, not you, that the touchscreen does not work. This is the most inefficient case I have ever seen here.

:mad:

It should go in a single forum post like this:

Q. "I replaced the touchscreen and now my Nexus does not boot. What can I do?"

A. "Do it properly" :rolleyes:​
[Nexus 7 (2013) Q&A] jhford:
My sincere apologies. So, long before writing a post here, I broke the glass on the display and replaced it with a new one (glass only, which was a mistake). It was not responsive. I then bought a display assembly including the frame and installed it. But the tablet wouldn't boot and I found your post and wrote my thread thinking that the new digitizer was irrelevant to the booting issue, or I would have mentioned it, I didn't want to waste anyone's time with irrelevancies.

I've taken it apart many times, but, for the first time, I slightly misaligned the silver touchscreen ribbon cable in the connector when I installed the digitizer, which you discovered - thanks. And, with your help I got it to boot with a new stock ROM, but I now have an unresponsive or erratic touchscreen. Everything else seems perfect.

That's my story, sad but true, and, again, my apologies. I meant no harm.
[Nexus 7 (2013) Q&A] jhford:
EDIT: I figured out how to output the twrp.txt file - the batch file; pretty cool. Hope you're not still mad. See attached.
[Nexus 7 (2013) Q&A] jhford:
You seem to be quite lonely after applying our Trumpian moral standards de jour to excommunicate me. ?
[Nexus 7 (2013) Q&A] Funky Wizard:
Will not boot past Google Screen

I was installing LineageOS on my Nexus7. The install was successful but it did not have google apps on it. So when I tried to install google apps I got error 70. I had trouble getting it to work. I decided to start over and reinstall Lineage OS. I assumed adp was working and began to wipe my device using TWRP. ADP was not working and I could not sideload the install. I tried to install it using an OTG cable but was unsucesful. I shut it off to do some research. Now it will go to Fastboot mode but it will not boot into recovery. It just stays on the Google Screen.

Thanks in advance.
[Nexus 7 (2013) Q&A] k23m:
No worries, just flash TWRP from fastboot: fastboot flash recovery twrp-x.x.x-x-flo.img

Fastboot driver... https://developer.android.com/studio/run/win-usb

As for Gapps, they must be flashed in the same session...

More info.... https://wiki.lineageos.org/devices/flo/install

Should something go wrong, then flash and run factory image before custom ROM... Flashing instructions

:good:
[Nexus 7 (2013) Q&A] Lezz:
Successfully fixed "FAILED (remote: Bogus size sparse and chunk header)"

I just ran into the same issue on my Nexus 7 3G 32GB. So, to report my experience here.

Device stuck on "Google" logo on boot.

I've tried Nexus Root Toolkit v 2.1.9 -> Soft-bricked / bootloop -> Flash Stock + Unroot.

No progress - still stuck on "Google" logo.

Downloaded "Android SDK Platform-Tools package" v28.0.1. tried few things, including fastboot erase userdata. This is how I ran into the error mentioned above (In my case, it was related to userdata, not system. But I doubt it actually matters much. Erasing some other partitions worked OK.)

Following this suggestion by k23m, I've downloaded "twrp-3.2.3-0-flo.img" and performed fastboot boot twrp.img.

Touchpad was still not functioning. So, it was still impossible to use TWRP.

Short googling suggests that touchpad related issues usually come from the cables. In my case, the touchpad started to work after detaching and re-inserting this dual-connector cable (but in my case the board looks like shown here, e.g. they are on the bottom side). Meanwhile, I've detached and re-inserted almost all cables in there. I'm not sure if that affected the FAILED (remote: Bogus size sparse and chunk header) - maybe, after all, they are two completely independent issues.

With touchpad working OK, and fastboot boot twrp.img, I performed wipe from TWRP followed by "Nexus Root Toolkit v 2.1.9 -> Soft-bricked / bootloop -> Flash Stock + Unroot". And now everything works OK!

Thanks k23m!
[Nexus 7 (2013) Q&A] paranormal11:
IMEI Restore after replace EMMC

Hi at all, sorry for my maccaroni english, i try to explain me better as i can.

Thanks to km23 we must be eternally gratefully every day, for his hard work and for his hard work posted here, i think at Asus team missing the most important element: Km23

1 year ago i tried to change the emmc following this thread and i do that succesfully, now my nexus 7 deb is working perfectly except for the Sim connection, obviously because IMEI is 0.

In the past i restore many IMEI, specially with XIAOMI phones, for example take a qcn from a working phone, adjust/correct the IMEI then flash back edited qcn to a 0 IMEI phone and that works very well.

This occur because flashing a wrong/different rom can cause to lost IMEI infos.

But with NEXUS 7 ME571KL don't work, every time i try to get a qcn backup the result is Disk error while writing to file.

I try with qpst to backup IMEI with a qcn backup from a working nexus 7 but when i try to make the backup i always receive Disk error while writing to file.

All the drivers are okay i try the same on 3 different PC with windows 7 and XP but always same result. DIAG mode is correctly enabled but always get same error.

I know change IMEI is a delicate argument, but i think in this specifically case can be important for many users know to restore to regain all the functionality of their Nexus 7 tabs, 4g included.

Today searching deep on the web i found a japanese site (i use a translator) that to gain a special band like 4g , needs to backup a QCN to work on it, and to get a QCN backup from a Nexus 7 with QPST use instead of Qualccom drivers these LG drivers LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1.exe

i didn't try this yet, i try it soon, but if someone know something about rewrite the personal IMEI on the tab i think is very useful for other users, i know that i can get the IMEI back off the old EMMC Chip, but is more complicate, then i ask if another method is possible.

Regards to all want to help and contribute
[Nexus 7 (2013) Q&A] k23m:
Here is a sure way to recover IMEI from your broken chip https://xdaforums.com/showpost.php?p=76926139&postcount=287

Three partitions need to be copied. Alternatively, ask around and use the attached TWRP script to copy it from another device.

I think I had seen people sharing it on this forum but it requires translation.

Good luck!

:fingers-crossed:
[Nexus 7 (2013) Q&A] paranormal11:
With this script i obtain a IMEI tgz file containing 3 img files, then i must extract img files and flash via fastboot on the Nexus with bad IMEI?

Can you show me the command?

If i want to reset IMEI to 0 what command needs? (same situation after flash the factory image on a blank emmc)

Thanks
[Nexus 7 (2013) Q&A] k23m:
IMEI Backup

I have prepared a set of TWRP scripts for IMEI operations:

IMEI-backup.zip

IMEI-erase.zip

IMEI-restore.zip

The backup creates IMEI-backup.tgz in the root of internal storage. You should copy it to your PC first. Next do the erase and see how it goes. If something goes wrong, install the restore (IMEI-backup.tgz must be in the root of internal storage).

Cheers!

:highfive:
[Nexus 7 (2013) Q&A] paranormal11:
Hi k23m, thanks for pappa pronta, with your script in less than 2 minutes i've restored the original IMEI and alll works perfectly!

I've 0 fill my IMEI with your script, then i restore with QPST a QCN backup from a working NEXUS 7 with IMEI edited in Hex, and voilà!

Yesterday i've spent hours trying to flash an IMEI in every way over an existing one, but obviously IMEI not change, with your knowledge less than 2 minutes all ok.

Thanks
[Nexus 7 (2013) Q&A] joheli:
cannot flash userdata

I've been trying to get my Nexus 7 deb 32G working for a while now and just read this threat

The device boots into fastboot just fine and the "fastboot format cache" - command runs within normal parameters, also the chip is probably one from Kingston.

As soon as I try to flash userdata, the device gets stuck. I guess the chip is partialy brocken (#3 on the list) but since the device is still locked, it isn't possible to run the "debrick-flashcall.cmd"-command

If there is any way to get this device working again, I'd be open for any suggestions

Greetings, Joheli
[Nexus 7 (2013) Q&A] k23m:
Hi, it looks like the Kingston chip is broken in a somewhat different way but if you wish to experiment with it and check what else is possible then I have prepared a special method to unlock the device.

As you had partially deployed the Unbricking Guide, just try now this...

fastboot boot twrp.img

install the attachment "safe-unlock-n7-13.zip"

reboot

Then try to use the device when it is unlocked with this workaround, meaning edit out any script that tries to "format userdata", OK?

:highfive:
[Nexus 7 (2013) Q&A] joheli:
Thanks for the quick reply, but he problem is, that almost no fastboot-commands are allowed with a locked bootloader, so I can't run fastboot boot...
[Nexus 7 (2013) Q&A] k23m:
Your post references the "debrick-flashcall.cmd" file from the unbricking package and implies that you had attempted to use the unbricking method. The method flashes a temporary bootloader which ignores the lock status, so you can unlock it without erasing userdata with my TWRP zip script...

proceed with the unbricking method up to before "run "debrick-flashall.cmd" (ignore error messages)"

fastboot boot twrp.img

install the "safe-unlock-n7-13.zip"

as your eMMC is not blank, skip "run "debrick-flashall.cmd" (ignore error messages)"

flash new Android but first edit out any script with "format userdata" or "fastboot -w update...." as -w erases userdata

For example in MOB30X script REM -w...

fastboot flash bootloader bootloader-flo-flo-04.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
REM fastboot -w update image-razor-mob30x.zip

and next manually flash....

fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot-bootloader

This may be a useless exercise as the Kingston chip is faulty and can block writing not only userdata but other partitions too.
[Nexus 7 (2013) Q&A] jhford:
Wow

So many uncriticized hyper-verbose posts. I didn't even get a half a point for brevity.
[Nexus 7 (2013) Q&A] k23m:
Here is a criticized low-verbose post. And you got a neg-point for longevity...
[Nexus 7 (2013) Q&A] k23m:
Sure, do "fastboot flash gpt gpt_both0.bin"

You'll find gpt_both0.bin file attached here https://xdaforums.com/showpost.php?p=76284329&postcount=21
[Nexus 7 (2013) Q&A] bez_iom:
thanks for the pointer, but unfortunately I get an error even with this.

C:\Users\t\Desktop\Nexus 7 2nd\gpt_both0>fastboot flash gpt gpt_both0.bin

target didn't report max-download-size

sending 'gpt' (35 KB)...

OKAY [ 0.016s]

writing 'gpt'...

FAILED (remote: failed to write gpt)

finished. total time: 89.529s

presume my emmc is damaged beyond repair unfortunately.
[Nexus 7 (2013) Q&A] bez_iom:
Trying to use sgdisk, how do I push or lauch this via twrp? thanks
[Nexus 7 (2013) Q&A] jhford:
You're funny.
[Nexus 7 (2013) Q&A] decayed.cell:
Worked for me thanks! Also, just in case you can get into fastboot but you still have problems such as formatting userdata partition, you can enter QD Loader by hitting Power, Vol Up and Vol Down at the same time for 10 seconds, and then connect the tablet to the computer
[Nexus 7 (2013) Q&A] ludemon:
I have a N7 that will only start in bootloader mode and although most fastboot commands function, format or erase userdata does not which means that the bootloader cannot be unlocked. I've seached the internet for a solution without success, but then I saw this thread and it seems to be relevant to the problem.

I carried out your button pressing procedure and now have QDLoader showing in device manager. Do I now follow the k32m instructions?
[Nexus 7 (2013) Q&A] k23m:
As your Nexus works in fastboot mode, it is pointless to follow the unbricking instructions. Instead, please follow the "Fastboot Diagnostics" on the first post of this thread. However it looks already that "....the eMMC chip is faulty and needs to be replaced".

It is a sad and thankless news but it will save you time and frustration when trying useless software solutions. You will find a lot of info on hardware repair in this thread.
[Nexus 7 (2013) Q&A] ludemon:
Thank you for your reply. Unfortunately I have already used the MiFlash app since my previous post and now the N7 is permanently in QDLoader mode. :( Each time that I've used MiFlash it stops at status "WriteFile position 0000000000000000, size 0" with the time still counting up.

It seems then that eMMC chip replacement is the only option left, so I'll have a go at that as an interesting project!

Thanks again for your help and for a very informative thread.
[Nexus 7 (2013) Q&A] ludemon:
The Kingston eMMC chip in my N7 is 1322. Should I source a direct placement or an equivalent?
[Nexus 7 (2013) Q&A] k23m:
No Kingston ever again! They have ruined your Nexus and countless other tablets. You will find a number of equivalents referenced a few pages back in this thread. Actually, you may upgrade it to 64GB eMMC if you wish.

:highfive:
[Nexus 7 (2013) Q&A] ludemon:
As it's my first attempt at replacing embedded memory I'll stick with the H26M64003DQR version for now. If successful I'll go for a 64Gb version if I acquire another N7 with a similar problem.