yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
Yes and no. When I tried the command you gave last night it bounced to the Google screen, which almost made me cry of happy because some of the errors I'd been getting had me dreading the possibility that the blob could have been good but the bootloader.ebt/BCT files weren't. I got "battery is too low" repeated over and over which I've seen before; not surprising given how much I've played with the thing. Wasn't returned to command prompt and --resume commands in another prompt didn't work. Wasn't at all sure that it'd charge in this mode (especially with the screen on) but plugged it into a 2A charger and hoped for the best.

It was off when I got up a few hours later and I had a minor heart attack, but if I run the command now, it bounces to the Google screen and returns me to the command prompt and as you noted, I can download partitions which is HUGE and I'm backing them all up now, UDA first. (As I mentioned, this wasn't my device, so I was dreading having to wipe user data though if that's what it took to unbrick it I'd obviously do it in a heartbeat.)

nvflash --resume --go doesn't seem to be putting me in fastboot with the Vol- button held down, unfortunately. I'm not sure if that functionality is in the bootloader itself or in another partition (e.g. does the bootloader for the Tegra 3 chain to the Android bootloader or is it the same thing?). So I'm going to poke at the partitions on my other device and see what matches bootloader-grouper-*.img and see if it works after I flash that (and boot.img) from the factory image the device was using (JDQ39).

On a technical side note, the flash.cfg you provided is interesting, though clearly it works. I had been basing mine off the partition table of a working device and not only were sizes (which I got by multiplying sectors by sector size) different but IDs were too (e.g. PT was 524288 for me, 4096 for you, partition 5 is SOS for you but EKS for me? Which is somewhat backed up by the androidroot.mobi guide when it suggests backing up partition 5 as EKS. But it may not matter as long as the sizes and numbers are right...)

Absolutely; in fact, if you have a PayPal (you can PM me), I'd like to buy you a beer or something. :) I appreciate your help over the holidays after I was feeling ignored (and at a certain point, ridiculed) for a couple days. We're developers, we play with things we're not supposed to, and sometimes that means we brick our devices. :( But I've certainly learned a lot.
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
I'm glad that worked for you! For the record I got a signature verification error when I tried to do this originally; some other users on the androidroot.mobi thread got one too. As mentioned, if you have issues flashing the bootloader with fastboot you can do it with nvflash --download 4; another user said this precluded using fastboot again in the future but I find that somewhat dubious.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
I don't have a Paypal account at the moment but if I had I would donate this http://xdaforums.com/member.php?u=2677399 for his nexushd2 roms. So if you want you can do this donation for me :)

Or you donate direkt to the flatline guys, as I said they are the true geniuses...

I made download 4 many times for testing with my own backup of this partition. The first time it bricked my device. I made the backup with unlocked bootloader but flashed it back with locked bootloader... You should definetly make the bricksafe.img and a Backup of all Partitions before you flash on this... But after I bricked my device with that I was still able to boot with wheelie and the blob.

But for you I will try to flash an old bootloader on this part an see what happens ;)

EDIT: the 4.3 (JWR66Y) Factory Image for nakasi has a broken bootloader. And if you try to flash it you will get a signature missmatch... (for that reason i recommed the 4.4.2 factory image) Maybe he only tryed to flash this bootloader... And I'm very angry on Google because this faulty bootloader is still online :( maybe you want to leave a Feedback on the download Page of the factory images: https://developers.google.com/android/nexus/images?hl=de#nakasijwr66y

EDIT2: I flashed bootloader 3.41 via nvflash. It worked and the bootloader booted. But as I tryed to flash the 4.23 from 4.4.2 (KOT49H) and got signature missmatch. But I could reflash the 3.41 again via fastboot now I will try diffrent bootloaders...

EDIT3: Bootloader 4.18 from 4.2.2 (JDQ39) works to... It seems there is something wrong with the 4.23 Bootloader google puts in it factory images...

EDIT4: Bootloader 4.23 from 4.4 (KRT16S) works but 4.23 from 4.4.2 (KOT49H) and 4.23 from 4.3 (JWR66Y) not...
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
Brilliant! Of course I missed the HOLD VOL- part the first time (bolding for everyone else :)) and it booted straight into Android, but the fact that it could even do that filled me with glee. Did it again and it put me in the 4.13 bootloader. I flashed the 4.18 stock bootloader that had been on the device before and for some reason it said "Signature match." this time! Don't know why but not complaining!

These instructions should be stickied; we had a guide for getting the nvflash blobs but not for what to do with them, especially when wheelie doesn't work! (I did try --rawdevicewrite early on to flash bricksafe.img back and for some reason it didn't work, but these steps are even more intuitive.) Thanks for saving my life! :)
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Read the last edits in my post before: many 4.23 Bootloaders are brocken and that is causing the signiture missmatch, because of that your 4.18 bootloader worked... You can use 4.23 Bootloader from the 4.4 Factory Image

But now the irony: it seems that I fullbricked my device with forcing a flash of a brocken bootloader via nvflash :S I can´t even enter the APX Mode it doesn´t shows up in any kind...

EDIT: Got APX Mode again :)

EDIT2: Oh you said 4.13 and not 4.23 Bootloader... Where did you get this bootloader from? I couldn´t find one with that version in a Factory image. Or did you used that modified Bootloader that was used to dump the blobs? Because that would make sense, this Bootloader is modified and so the Googles signiture is brocken ;)

EDIT3: After testing all of the grouper factory-images (and indentifying the Bootloader from 4.3 and 4.4.2 as brocken I want to test ALL the OTA Updates from here: http://xdaforums.com/showthread.php?t=1745781 First by flashing the bootloader it contains with fastboot, than flashing the whole OTA-Package over adb-sideload (of course I have to flash the corresponding Android Version before) and than via nvflash...

If you want you can help me, because I have to do things for school and so I don´t have more time for playig with bootloaders, but you should make a Backup of every bit of your device ;).

And every time I brick my device via flashing a brocken bootloader via nvflash I have trouble entering APX Mode....

EDIT4: I´m not able to enter APX Mode again... I feel just to dump to press two buttons...

EDIT5: I´m trying hard since a houre to get in APX Mode but nothing ;( - but why? APX must work, its in the ROM...
[Nexus 7 Q&A, Help & Troubleshooting] heterodoxy:
I only ever tried to flash the 4.18 bootloader that was previously on the device. I knew there was a possibility others were broken as mentioned in the original thread. It gave me a signature mismatch before, it doesn't now. Again, I don't know why but c'est la vie.

Oh no! As we just proved, that shouldn't be able to happen! :(

The one on the device (and I guess in bootloader.ebt) was the flatline 4.13 bootloader. I was trying to put 4.18 on top of it. I would think the signature mismatch would be done on the new bootloader not the existing one. But either way, flashing the exact same bootloader on top of the exact same bootloader works now.

Sure, I'll try to do that when I have time. :)

I'm wondering if you're just in some really strange run state. Have you tried disconnecting the battery, leaving it disconnected for a minute, re-connecting it, and then trying to boot into APX mode again?
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Yep not only once...

EDIT: How exactly did you enter the APX Mode, and did you had a similar problem?
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Booting again... It seems that the bootloader from 4.4.2 sends our device in a very very deep slep...

Got it working again by disconection batttery and holding vol + all the time while reconecting and pluggin in USB.

I could flash the working 3.4.1 bootloader over the brocken 4.4.2 bootloader with fastboot like in my unbricking Guide described...

So I think I proved that --download 4 won´t cause a signiture missmatch in any case, as long the bootloader you want to flash with fastboot has a valid signiture ;)

And I can´t say it often enougth: the bootloaders from 4.3 and 4.4.2 Factory Images are bad, very bad, don´t even think about trying to flash these!

Go to this Page: https://developers.google.com/android/nexus/images?hl=de and hit Feedback or something an tell Google they hav to remove these bad bootloaders that kill our devices!
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
As far as I know you can enter APX-mode by pressing both, Vol+ and Vol- when starting your tablet.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Hm I flashed 3.41 bootloader after my brick and now i saw fastboot shows me under the serial number: SINGING - not definied yet, what does your bootloader shows you?

And I looked at a updater script from an OTA Update how they write de Bootloader

they must be crazy, no checks at all...

BTW: which device in /dev/block is this?

---------- Post added at 10:47 PM ---------- Previous post was at 10:15 PM ----------

Hm in normal state it goes to APX Mode if I hold vol+ at reboot. With earsed mmcblk0boot0 I only need to hold Power while connected to PC
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
USP is a 10MB staging area, partition mmcblk0p6. I have a list of the Nexus 7 partitions in my blog.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Hm i overread the topic again and I think that the flash.cfg has not to be correct, because I think the flash.cfg is only for the create command (wich has to fail)
[Nexus 7 Q&A, Help & Troubleshooting] Sangito:
tf300

Even if it wrong, i have a asus tf300/32Go and the flash.cfg of the Nexus 7 you give, make the nvflash command working again, after that i restore the original bct with my recovery.bct and do the restore like you propose and bam everyhing work again.

I think my patition table was damage(the bct), but when i send a new one event if it wrong it unlock the nvflash command long enough to make a restore.

For that thanks Partitionator

You are the best.:good::good::good:
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Thanks for your Reply...

Now we know that we can use any flash.cfg, that looks vaild to nvflash :)

And I forgot the "not" in my last Post ;)
[Nexus 7 Q&A, Help & Troubleshooting] matlock67:
Hi, I think my n7 16gb is bricked, all I get is Google displayed, cannot get to either fast boot or recovery modes, only way to power down is to wait until the battery dies.

Ive nothing to lose in trying to nvflash so have you step by step guide including what software is required plus any links.

If got both win 7 64bit or Ubuntu access.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
If you get the Google logo thats your bootloader how did your tablet get to that point? Have you tried pressing power and vol down just as the Google screen comes up that should bring you into the boot loader and you can use adb commands
[Nexus 7 Q&A, Help & Troubleshooting] matlock67:
when powered on google appears forever, unless I force reboot by pressing on button form 20 secs. Cannot access fastboot or recovery options using pwr Vol- or pwr vol+.

Original issue.

tablet froze (not doing updates) shutdown and restarted, it booted and then displayed No Command.

Tried doing restore using fastboot and recovery, it hung on formatting /data (tried about 4 times), tried to clear cache in recovery (hung as well)

Then could no longer access fastboot or Recovery menus, now only get google displayed when powered on (nothing else).

Have tried using adb via Nexus Root Toolkit , but does not pick up the device

any ideas?

I've ordered replacement motherboard from the US but will take weeks to get to the UK.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
[MENTION=4417599]matlock67[/MENTION] Sorry it sounds like a corrupted partition my only question would be why order from the US I got a 16gb board delivered 1st class for £30 off eBay in fact I think I still have one around somewhere. I ended up not needing it and never sent it back. So I kept it as a spare
[Nexus 7 Q&A, Help & Troubleshooting] matlock67:
Managed to get the device recognised on my PC by pressing vol+ and connecting usb (I loaded naked APX drivers) from here

http://xdaforums.com/showthread.php?t=1514942

the device now shows as a Android Phone > ASUS Transformer prime APX interface

Nexus Root Toolkit , still does not find the device ?
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
I think and I may be wrong here that you can only recover your bootloader in apx mode if you have previously taken blob.bin files through the nvflatline procedure however as you haven't wiped your bootloader it must have somehow become corrupted. I don't think you can recover it without the blob.bin as I'm still getting my head round using apx mode someone else may know differently

NRT will only recognise the device in fastboot mode or booted into the ROM as apx mode is neither and uses different commands to adb it won't be picked up
[Nexus 7 Q&A, Help & Troubleshooting] matlock67:
Thanks for the info, Looks like your right, because i cannot get to fastboot mode I cannot get the blob.bin from my device.

My nexus 7 is 17months old so out of warranty, Will have to wait for new motherboard (was only £16) to come from the states.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
£16 is pretty good I ended up having to buy a n7 with a broken screen as I needed several components(a slight mishap involving 15volts going down the data pins) but I already bought a motherboard so now I have 2 if I hard brick it then I'm sorted:D

Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
Hold on a sec

so hold on my tablet is currently being recognized via usb as "Asus Transformer Prime APX Interface" in the device manager and I can get hold of the chip uid and a few more things when using NVflash in CMD but then I get a "usb write failed" error when flashing so does this mean my 32GB wifi nexus 7 is recoverable or not
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
I'm sorry to say your n7 is hard bricked the mode your in is used to reflash a bootloader however bootloaders are device specific no other n7 bootloader will be suitable except the one the tablet came with apx mode requires you to have previously backed up your specific bootloader. To my knowledge nobody has ever recovered a device from apx mode without the backup. Your best option is a replacement motherboard it's the.only way to fix it.
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
I see what you mean however

I thought it was possible if one had the SBK and another persons backup files and when I execute the commands at the moment I see nothing happening in the CMD after nvflash starts (the process takes forever) and I found this guys comment interesting because he doesnt mention anything about backups

https://productforums.google.com/forum/#!topicsearchin/nexus/nexus$207$20apx/nexus/DRK0S8-RqL4

and also since its wifi version wouldn't it be better to RMA it
[Nexus 7 Q&A, Help & Troubleshooting] svs57:
flash.cfg.txt for 3g 32Gb
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
How did you get this flash.cfg? The flash.cfg I provided for the Nexus 7 16GB is basicly garbage, not even the Partition Names match, and the sizes are looking crazy too...

I found that out AFTER experimenting with the create command, and now I don't have a valid Partition Table on my device

Can you generate a flash.cfg for the 16GB version too if I provide you the necessery files?
[Nexus 7 Q&A, Help & Troubleshooting] svs57:
I got flash.txt for 16Gb model from message: http://xdaforums.com/showpost.php?p=48507424&postcount=16

Then I got partition.txt from my 32Gb nexus:

nvflash --resume --getpartitiontable partitiontable.txt

This file contains partition name and size.

Using this information I edit 16Gb flash.txt and create 32Gb flash.txt

I attached flash.txt 32Gb here: http://xdaforums.com/showpost.php?p=56544414&postcount=40
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
The 16GB flash.cfg looks like the one that i generated. But your 32GB flash.cfg looks valid (look at the partition name and sizes)
[Nexus 7 Q&A, Help & Troubleshooting] svs57:
I used my 32gb flash.cfg when i restore bootloader. It works.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Yes, as I said: the 32GB looks good, but the 16GB makes no sense.
[Nexus 7 Q&A, Help & Troubleshooting] Roboffabike:
No blob.bin, no can do?

So in summary... Without a blob.bin that has been previously created on the specific N7, un-bricking from a corrupt bootloader is impossible?

I am trying to fix a 32Gb for a family member who accepted the Lollipop OTA and his tablet never worked again...
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Sorry, no blobs no unbrick.
[Nexus 7 Q&A, Help & Troubleshooting] Bogdan_97ua:
Hi. Does anyone can tell me how to create flash.cfg with bct_dump please?
[Nexus 7 Q&A, Help & Troubleshooting] mccabet:
Re-partition to change /system size

Has anyone tried to resize a partition using the blob.bin and the nvflash --create commands with a valid modified flash.cfg?

What files are actually in blob.bin file? Anyone know if there is anything that would prevent creating a new partition layout?

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Yes Trier it but wasn't successfull...
[Nexus 7 Q&A, Help & Troubleshooting] ichigo_kurosaki:
help.:(

my grouper bricked 2 days ago. cause unknown..now i'm attempting this flatline recovery and nvflash thingy to bring the dead back to life (i can still access bootloader/fastboot)..i have followed instructions at the nvflash guide site but i can only go as far as flashing the flatline recovery, booting into it then going to Advanced > Wheelie and celecting the one option inside it..i can only get as far as

attempting to mound data...

and nothing more. i have the naked drivers and the nvflash (dunno how to use it)..now my problem is how can i access steo 1 of wheelie? i am suspecting that i am missing something here? i don't have the wheelie binary. for some reason that is not included in the download links for needed files here. to b honest the instruction there are a bit confusing to understand..or is it just because they didn't provid the wheelie binary? please..i hope you can help me..i need my n7 badly as i use it for many things.:(
[Nexus 7 Q&A, Help & Troubleshooting] ichigo_kurosaki:
i'm on the 4.23 bootloader. tried flashing everything manually after learning to setup the SDK (been using the NRT for a while now) still nothing..erased what needs to be erased (except bootloader ofcourse) manually via fastboot..flashed everything accorfing to sequene in the instruction..all goes well until well..bootloader flashing..which always fails.

To be specific i am confused by these (see screenshot attactments (note, these screenshots are borrowed from transformer nvflash..:D

you see, i can get here

and here:

and finally here:

but when i click to accept whatever it says, i don't get here (wheelie menu):

instead, the flatline-grouper recovery just displays

flatline CWM Recovery v1.0RC1

E:can't mount /cache/recovery/command

E:can't mount /cache/recovery/log

E:can't open /cache/recovery/log

E:can't mount /cache/recovery/last_log

E:can't open /cache/recovery/last_log

so llike what i said earlier maybe i'm msissing something here..the whelie binary something..
[Nexus 7 Q&A, Help & Troubleshooting] zakaria9:
help

i have 2 tablet same nexus 7 2012 32gb tilapia

how to get blob.bin, bootloader.ebt, recovery.bct files ???
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
No chance if you haven't already created them on the working device.
[Nexus 7 Q&A, Help & Troubleshooting] jakobsjoqvist:
Hi there!

Yesterday I backed up my blobs but since that I can't update the bootloader. My intension is to use 5.1.1, but at the moment I am stuck at the 4.13. Do you know how to flash an another bootloader, at the moment I get the error "BadParameter" no matter which bl it is.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
There is no 5.1.1 Bootloader...

But you can try to flash the Bootloader from an OTA update in the Recovery.

But there shuldn't be a Problem in using the flatline Bootloader (4.13) as far AS I know it is based in the last official Bootloader (4.23) wich came with Android 4.3.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
Hmm ... I am not sure, but 4.13 != 4.23. If I understood right, you need to flash the 4.23 bootloader first before you can install a KitKat / Lollipop based ROM, but I might be wrong. [MENTION=559200]jacobs[/MENTION]joqvist are you trying to flash the bootloader or the boot partition? Try to update your bootloader first by flashing it via fastboot:

fastboot flash bootloader <bootloader-4.23>.IMG
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
You can flash every stock Rom, you just need to extract the zip and flash every partition (Boot/system) by hand.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
... yes, but probably you need to have 4.23 bootloader to boot a KK / LP kernel due to different parameters needed for the kernel on boot time.
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
The cmdline should be included in the boot.img

And it tested it, it worked, without any problems...
[Nexus 7 Q&A, Help & Troubleshooting] jakobsjoqvist:
When I try to flash the 4.23 bootloader it looks like this:

[IMG="Attempt to flash 4.23 Bootloader"]http://i.gyazo.com/454c8974ca279e583726e1fb8a885581.png[/IMG]

I have also tried to use Wug's toolkit, both flashing the bootloader itself but also returning back to stock(which includes flashing the bootloader), both times I got the same error as in the picture above.

Thanks for your help, its appreciated!
[Nexus 7 Q&A, Help & Troubleshooting] jakobsjoqvist:
After further searching and tests i've recognized the problem, the bootloader partition is gone. But do anyone know how to reformat the bootloader partition?
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Make sure you have valid nvflsh blobs.

Than search in the 4.3 OTAs a bootloader.raw (should be in the root of the zip) than dd it to the USP/staging partition and reboot.
[Nexus 7 Q&A, Help & Troubleshooting] jakobsjoqvist:
Can you please write or link to a guide that shows how to dd the bootloader.raw to the USP/staging partition?
[Nexus 7 Q&A, Help & Troubleshooting] Partitionator:
Why? You don't need to mess with Bootloaders. Just flash boot.img and system.img from the Factory Image you whish and you'll be fine. No problem with the flatline Bootloader, as I already said...

To flash the Bootloader through there are to ways:

1. Just flash a pre 4.3 Stockrom and install the OTAs, the OTAs will Update your bootloader.

2.

dd if=bootloader.raw of=/dev/block/platform/sdhci-tegra.3/by-name/USP
[Nexus 7 Q&A, Help & Troubleshooting] jakobsjoqvist:
Should I be in fastboot mode when

dd if=bootloader.raw of=/dev/block/platform/sdhci-tegra.3/by-name/USP

?