[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
How to unbrick

So here is the shorten way to recover your device from a Fullbrick:

First: I´m not an expert for that and this is the result of many houres of testing, so I don´t think its the best way to unbrick, but at the moment its the only one and it works.

And I can saftly say if you don't have the blob bin and you screwed up your bootloader I can't help you, nobody can help you, you have to buy a new Mainboard. If you have your blobs follow this guide:

you need:

your blob.bin with bootloader.ebt and recovery.bct

Linux (only to generate your flash.cfg)

nvflash binarays from here: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/

a working bootloader.img from a factory image and a boot.img (you can use one from a factory image) (I used 4.4, the bootloaders in 4.3 and 4.4.2 are corrupt!)

I recommed to use the boot.img of your actual installed rom/kernel.

First you need to generate your flash.cfg. I've done this wit dump_bcd under Linux. I got this with the package cbootimage under Kubuntu.

I generated it from my recovery.bct. After that you have to remove the line that starts with type from the device section in the flash.cfg.

(maybe someone wants to write this part more accurate because bct_dump doesn't work anymore on my PC)

If you have a 16GB Nexus 7, I think you can use the attached one (you have to rename it), but no guarantee if it doesn't work.

Than you put all this files together in a folder (nvflash, blob.bin, bootloader.ebt, recovery.bct, boot.img, bootloader.img/bootloader-grouper-4.23.img, flash.cfg).

Than you go with a terminal there. Under windows you just have to remove the sudo ./ at the begining of the commands and maybe you should run it as Admin.

First we bootstrap it to the nvflashmode. Of cause your device has to be in APX Mode.

WARNING: If you execute this command you have to reflash the bootloader even if you have a working installed because it will wipe your installed bootloader (I think)

sudo ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin

You can see I used the --creatte command there. It will fail (so nothing will be wiped, but im not responsibile if it will wipe something) and its only there to allow me to use the --setbct command.

After this command you should see Google on your device and your terminal should produce a output like that (the error ist as said from create):

Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d2bc285340e0f
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc285340e0f
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 0

sending file: recovery.bct
- 6128/6128 bytes sent
recovery.bct sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.ebt
- 2146912/2146912 bytes sent
bootloader.ebt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 0 3
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0

The next command will flash a kernel (however without flashing a kernel it won't go to fastboot mode) and than bring set your device into fastboot mode. You have to hold Vol- after/while hitting enter till its in fastboot mode. If you don't hold vol- it will boot to android and you have to start from the begining.

sudo ./nvflash --resume --download 8 boot.img --go

Now you should be in fastboot mode and the last step is very easy:

simply reflash the bootloader:

fastboot flash bootloader bootloader.img

or in case of the lastet bootloader

fastboot flash bootloader bootloader-grouper-4.23.img

Now your device should be unbricked :)

If not you can try to bootstrap it again to nvflash mode and than flash your bricksafe.img

nvflash --resume --rawdevicewrite 0 2688 bricksafe.img

And if you need you can reflash the other backed up Partitions too:

nvflash --resume --download 5 eks.img
nvflash --resume --download 13 factory-config.img
nvflash --resume --download 14 mda.img

After that your device should at least go to fastboot mode again :cool: If not let me know and I will try to help you.

If I helped you please hit the thank button, it took me a few days to test this all and it was a lot of work to write this. And please thank the guys that created flatline too, they are the true geniuses :).

EDIT: If you have trouble with this way, try (in nvflashmode) to download the flatline recovery to partition 7 (it will straigth boot to ist) and reinstall the flatlinebootloader.

I onetime I unbricked my device the firstway I hat terrible lags, after, and the only way I found to fix them was to reflash the flatlinebootloader (after that i could flash any bootloader without lags)...