[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Yeeeeeaaaaaaaaahhhhhhhhhhhh :cool:

I think my Nexus isn't dead... I experimented all day and all night long with nvflash, read much about the emmc partitions and finally something worked... Now it shows Google with the unlock symbol :)

I think the rest sould be easy..

First I created a flash.cfg. You can do that under linux with bct_dump under Linux. (I used recovery.bct which was created with the blob.bin)

Than I had to remove the line that starts with type= in thefirst section of the flash.cfg file.

here ist my flash.cfg file (16GB Nexus 7)

[device]
instance=3

[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.EBT

[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.SOS

[partition]
name=LNX
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.LNX

[partition]
name=BAK
id=7
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=GP1
id=8
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.APP

[partition]
name=CAC
id=10
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=MSC
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=USP
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PER
id=13
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=YTU
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=UDA
id=15
type=data
allocation_policy=sequential
filesystem_type=ext3
size=18432
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0

[partition]
name=GPT
id=16
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

After that I ran this command:

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

bäääm some output in the terminal (and Google flashed up on the device):

root@jan-notebook:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
Nvflash v1.13.87205 started
Using blob v1.13.00000
USB device not found
root@jan-notebook:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
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

root@jan-notebook:/home/jan/APX#

But you can see there is still a error and I use the create command what should earse everthing so you should only do this if you habe a backup of all imortant partition. But I recommend that you wait while I will test what I can do with that, and look what that error means.

EDIT: Very good in this state I have nvflash acess and can flash partitions...

EDIT2: Yeeeees its booting again, with all data on it, that means no wipe :). First i flashed many partitions (i don think that flashing most of them was unecessary). Tomrrow I will brick my device again and then test what exactly to do...

EDIT3:

Sorry I overread your Post... Yes it was the same error (3)

EDIT4: read here for unbricking: http://xdaforums.com/showpost.php?p=48507424&postcount=16 :cool: