yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Cusciolino:
Done yet... result? "Androi 4.4 must have new baseband ver.xxx to run" (summary of error message) and I had to send N7 to rma.

So yesterday I wrote to ASUS to ask info about this problem.
[Nexus 7 Original Development] MoJo:
Just in case successfully had make blobs backup (bootlader-4.13 and FW-PA 2.99) on my Nexus 7 3G. Then installed bootloader 4.23 like here - http://xdaforums.com/showthread.php?t=2175086

P.S. Guys, thanks for tools!
[Nexus 7 Original Development] xmas_spirit:
apx mode

Hi guys,

yesterday I was installing official image 4.2.2 for nexus 7 2012 wifi 16GB model (it was before on bootloader 4.13 with some cyanogenmod 4.2.1)

https://dl.google.com/dl/android/aosp/nakasi-jdq39-factory-c317339e.tgz

^^^

using flash-all.sh, process was running ok until phase "fastboot flash bootloader bootloader-grouper-4.18.img", this phase failed "FAILED (remote: (InvalidState))" and after that device is unusable.

Now nexus is stuck in APX mode, no bootloader, no recovery, no logo, no image - hard brick (was trying everything).

I didnt know this could happen by using OFFICIAL google images and didnt knew about nvflash stuff until today. I am out of warranty also.

I am out of luck, right? Or any suggestions?
[Nexus 7 Original Development] Partitionator:
I'm sory for you...

But AS I said: 4.4.2 Bootsklasse is broken... If a bootloader flash fails you should try to reflash another without reboot.

The only solution I see in your case is to buy a new Main board from eBay...
[Nexus 7 Original Development] svs57:
I made nvflash backup files:

blob.bin bootloader.ebt create.bct factory-config.img partition.txt pt_restore.log

blob.log bricksafe.img eks.img mda.img pt_patch.log recovery.bct

Then I restored twrp recovery. I found that version of bootloader is 4.13 instead of 4.23

I boot n7 3g into apx and tried to flash bootloader:

nvflash -r --download 4 bootloader-tilapia-4.23.img

Nvflash v1.13.87205 started

[resume mode]

sending file: bootloader-tilapia-4.23.img

\ 4005632/4005632 bytes sent

bootloader-tilapia-4.23.img sent successfully

Then device rebooted into system mode.

But now I can't reboot device.

Only apx boot works.

Can anybody help me?

PS

solved

I flashed bootloader-grouper-4.23.img. It works.

It's strange that bootloader-tilapia-4.23.img doesn't work on 3g
[Nexus 7 Original Development] xmas_spirit:
Actually I was installing 4.2.2 and not 4.4.2 version. My reasoning was that this is closest version to version before, and then I would update via OTA to latest. Anyway I tried that fastboot bootloader phase again without reboot, but nexus was in waitinig state and never did it. It looked like fastmode was no longer working.

Thanks for sympathy
[Nexus 7 Original Development] Partitionator:
Hi,

yesterday I showed my classmates how unbrickable my nexus 7 is, by overwriting mmcblk0boot0, and restoring it via bootstraping it with nvflash, and reflashing de bootloader over fastboot... Now I have terrible lags on my Homescreen, and I don't know why or what I should do against ist...

I tryed a factory reset, relocking and reunlocking the bootloader, flashing the factor image, flashing the bricksafe image, overwriting the complete mmcblk0 device with zeros but nothing helped...

But it doesn't lag if I bootstrap it with nvflash, and let it direkt boot to android, without any reboot...
[Nexus 7 Original Development] diesburg:
That's amazing, with this device I wasn't even aware nvflash was something you could even need. I've done things I knew I shouldn't do with screwing around with flashing bootloaders and crap but never hardbricked. Guess I'll be taking advantage of nvflash before its too late. One question is it usable across different motherboards? Because of broken hardware before, I now have 1 full working nexus 7 with 3 extra fully working motherboards(which BTW if anyone's totally bricked I'd be willing to get rid of a couple, pm me) but will this process work for all my extra mobos doing it once with one mobo?

After actually reading I think my answer to that is no because different motherboard is essentially different device. So I'd have to do it once for every motherboard right? To make them all unbrickable
[Nexus 7 Original Development] Partitionator:
Every Mainboard has its own randomly generated encryption key...
[Nexus 7 Original Development] ashik992:
I have two questions.

* The guide mentions Jellybean. So, it is gonna support KitKat(4.4.2)?

* After I made a blob file. Is it still gonna work if I flashed another custom recovery/bootloader/operating system (For example: Ubuntu touch) and I can't get access to fastboot/recovery?

N.B: I'm talking about Nexus 7(2012)
[Nexus 7 Original Development] Partitionator:
The OS doesn't matter... Why should it? Its loaded after the Bootloader.

I tryed flatline with lots of installed bootloaders and got it back working everytime, so if you have blobs there is definetly a way to fix the bricks, but somtimes its hard to find it ;)

4.3 and 4.4 are using the Same bootloader.
[Nexus 7 Original Development] philhouse:
I have a situation where I can only get to APX. Cannot use fastboot or a Tookit to load a ROM.

Would buying and replacing this fix my problem?:

http://www.ebay.com/itm/ASUS-Google...US_Motherboard_CPU_Combos&hash=item258a042aad
[Nexus 7 Original Development] Partitionator:
Yes this should work.

Didn't you have made The blobs for nvflash?

And have you tryed to press the power button for 30sek or disconnecting the battary?
[Nexus 7 Original Development] philhouse:
I don't have the blobs because I only found out about it when it was too late :(

This happened without rooting or unlocking or doing anything with the tablet other than browsing the internet and OTA updates. From the amount of people that have had issues, it seems like a hardware issue.

I tried pressing and holding the power button but it didn't help. This helped in prior instances where the tablet wouldn't work, but not this time.

Thanks, I think I'm going to buy that board and try it out.
[Nexus 7 Original Development] Partitionator:
Have you tried disconnecting and reconnecting the Akku?
[Nexus 7 Original Development] philhouse:
No I haven't. I'll try that later, thanks
[Nexus 7 Original Development] markymark567:
+1 to this question. Others have mentioned downgrading your bootloader then get blobs. But what's the safest way to downgrade bootloader???
[Nexus 7 Original Development] Partitionator:
The OS doesn't matter. Btw 4.3,4.4 and 4.4.2 have the same bootloader, but the bootloaders from the 4.3 and 4.4.2 factory images are broken
[Nexus 7 Original Development] Gloftking:
Help me

Can you please tell me how to to that with some instructions because I am in the same annoying situation as described. my tablet will not even turn on at the moment

thanks in advance
[Nexus 7 Original Development] Partitionator:
Do you have the blobs?
[Nexus 7 Original Development] Gloftking:
Unfortunately not and I have no clue how to operate this software
[Nexus 7 Original Development] Partitionator:
Without blobs or a working bootloader on the Device, the only way is to replace the Mainboard :( Sorry.
[Nexus 7 Original Development] USBhost:
But they work just fine
[Nexus 7 Original Development] shinji257:
So really quick question. I'm on bootloader 4.23. Do I have to downgrade to stock 4.13 first or can I just start the process off with flashing the flatline modified bootloader?

EDIT: It's done... So now then I guess the question is can I stay on the modified 4.13 or should I go back to 4.23? I got the necessary files.
[Nexus 7 Original Development] AndDiSa:
For newer versions of the OS (>=Android 4.2) you will need the 4.23 bootloader.
[Nexus 7 Original Development] Partitionator:
I thougth there was not (offical) 4.13 Bootloader, I think flatline modified the Version, that you can indentify their bootloader.

At the Moment I'm on 4.4.4 Wirth the 4.13 bootloader with no Problems
[Nexus 7 Original Development] shinji257:
Yea. The flatline bootloader is 4.13. I'm also mainly wondering because I did a backup on the 4.13 using their recommended steps then when I went back to 4.23 I did it again (for the heck of it?) and found that my bricksafe changed from 4.13 and 4.23. Anyone know what it contains?
[Nexus 7 Original Development] Partitionator:
It should contain the Bootloader, but i think if you boot it with wheelie some parts from the eMMC are used like mmcblk0boot0.

But I found a way to completly bootstrap it from your blob with nvflash even if the eMMC ist total empty...

If you are interested in playing with your bootloader :D: http://xdaforums.com/showthread.php?p=48507424#post48507424
[Nexus 7 Original Development] Gloftking:
trying that right now

I tried that but it says [resume mode] and stays there and doesn't move from there

any ideas
[Nexus 7 Original Development] KrzychuG:
A quick question. My N7 died during updating apps from play store. It was working a bit slow before that and it stucked in APX mode after powering it off. ASUS replaced mainboard on warranty. It came back with 4.4.2 installed with 4.23 bootloader on in. I Installed flatline recovery, installed flatline 4.13 bootloader, generated blobs, made all the suggested backups and saved it in some safe place. Now, if i update the software to 4.4.4 (stock or custom) or future L (if it gets it) and bootloader to 4.23 (or higher in future) will i still be able to access nvflash and recover it just in case with the blobs i created or i have to keep the flatline 4.13 bootloader in order for that (whelie --blob blob.bin and the rest) to work?

I'm guessing the flatline 4.13 is mandatory here but just want to make sure.
[Nexus 7 Original Development] burnsyboo:
try this (;

you have to first use wheelie --blob blob.bin to boot the device from apx mode into nvflash mode and then you can use nvflash -r --download 4 bootloader.bin and it should flash the bootloader and then you can unplug your usb cable and hard power the nexus off by holding the power button for 10+ secs and then try booting into your new bootloader
[Nexus 7 Original Development] Partitionator:
Your blobs will work for lifetime with your device. It doesn't depend on anything in the emmc.
[Nexus 7 Original Development] KrzychuG:
Good to know, thanks. Still, i suspect emmc simply died (despite the fact that my tablet very, very lightly used for those 2 years) on the previous mainboard so they won't help in that case anyway.
[Nexus 7 Original Development] Partitionator:
Yes the Samsung emmc is a Problem...
[Nexus 7 Original Development] svs57:
Can't flash BL using nvflash

Nexus 7 (2012) 3g 32Gb

I made nvflash backup: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/

Backup was successful.

Then I try to flash back stock bootloader:

wheelie --blob ./blob/blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d456da347fa0c
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

# nvflash.1 --resume --download 4 nakasig-ktu84l/bootloader-tilapia-4.23.img
Nvflash v1.5.66719 started
[resume mode]
sending file: nakasig-ktu84l/bootloader-tilapia-4.23.img
- 2151072/2151072 bytes sent
nakasig-ktu84l/bootloader-tilapia-4.23.img sent successfully

Devices rebooted into system. But seems bootloader didn't flashed.

If I try to reboot device it go into APX mode.

I also try to flash 413bl.img. The same result.

How can I restore stock bootloader?
[Nexus 7 Original Development] Partitionator:
You can flash it via fastboot.
[Nexus 7 Original Development] svs57:
Can you explain me how if I can't boot bootloader?
[Nexus 7 Original Development] Partitionator:
Partition 4 isn't the Bootloader, i think it was the boot.img/kernel or recovery (not sure).

If you flash the Partition that contains the Kernel it will continue the boot process, if you hold vol down while flashing it will enter fastboot mode, there you kan flash a new bootloader.

If that doesn't work you could also write back your bricksafe.img.
[Nexus 7 Original Development] svs57:
VolDown + Power doesn't boot bootloader for me. All instructions I read have the same command to flash bootloader

nvflash -r --download 4 bootloader.img

I attached partitions I got from device.

Can you look at this file and tell me which partition is bootloader

PS

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

Didn't help.

Device boot only one times
[Nexus 7 Original Development] Partitionator:
Sorry you are rigth. Partition 8 ist the kernel. Flash the Kernel (boot.img) while holding vol down and your device should go in the feastboot mode.
[Nexus 7 Original Development] svs57:
Already flashed stock kernel and recovery. Doesn't help.

I repeat that device boot system. But only after I flash bootloader and only once.

Seems that everything works except bootloader
[Nexus 7 Original Development] Partitionator:
Are you holding vol down while flashing the kernel to partition 8 till the fastboot mode appers?
[Nexus 7 Original Development] svs57:
No. I don't think that problem in kernel. It boot when I flash bootloader.

I have cutom kernel before. It also boot. But I flash stock kernel using nvflash
[Nexus 7 Original Development] Partitionator:
I know that the Kernel isn't the Problem. But the best thing ist when you flash the Bootloader via fastboot and the only working way I found to leave the nvflash mode an continue boot, with the bootloader contained in the blob.bin ist to flash a kernel. If you hold power down while the boot continues the bootloader from the blob.bin will go into nvflash mode.

If that doesn't work you can flash your bricksave.img back:

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

That should fix your bootloader too.
[Nexus 7 Original Development] svs57:
Can't understand. I flash bricksafe.img. Didn't help. Then I flash again bootloader-tilapia-4.23.img and hold VolDown.

fastboot 4.13 loaded. I erase and flash boot, bootloader and recovery. Successful.

But bootloader didn't boot again. If I repeat the same procedure I see 4.13 bootloader instead of 4.23.
[Nexus 7 Original Development] Partitionator:
Flash the androidroot recovery and reflash the bootloader (advanced-->wheelie--> step1)
[Nexus 7 Original Development] svs57:
How can i boot recovery?
[Nexus 7 Original Development] Partitionator:
flash it as kernel
[Nexus 7 Original Development] svs57:
Done. Flashed flatline_grouper.img into boot partition. Recovery booted. Advanced -wheel - flash bootloader

But it doesn't help. Bootloader version 4.13. It boot only once.

Also I can't flash bootloader 4.23 using 4.13 bootloader

Two kind of error depends of what file I try to flash:

fastboot flash bootloader bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.399s

or

fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (BadParameter))
finished. total time: 0.400s

ps

Is any way to flash bootloader from booted system?

Something like

dd if=bootloader-tilapia-4.23.img of=/dev/block/platform/sdhci-tegra.3/by-name/[B]?[/B]
[Nexus 7 Original Development] Partitionator:
Try the bootloader form the 4.4 Factory Image
[Nexus 7 Original Development] svs57:
Have tried.

Do you know about what's files in blob directory and how to use it? I know only about blob.bin

blob.bin blob.log bootloader.ebt create.bct pt_patch.log pt_restore.log recovery.bct upload.response

I see in log files that's wheelie write to partition table:

...
LOG: writing pt...
LOG: done
...
[Nexus 7 Original Development] Partitionator:
Does the fastboot mode show Signature missmatch in the top left corner if you get the InvalidState error?
[Nexus 7 Original Development] svs57:
Yes

---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------

root@ssmirnov:/home/ssmirnov/nvflash# fastboot flash bootloader ~ssmirnov/nakasig-ktu84p/bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.400s
root@ssmirnov:/home/ssmirnov/nvflash# ls bootloader-grouper-4.23.img ^C
root@ssmirnov:/home/ssmirnov/nvflash# fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
OKAY [ 1.196s]
finished. total time: 1.455s
root@ssmirnov:/home/ssmirnov/nvflash# md5sum bootloader-grouper-4.23.img ~ssmirnov/nakasig-ktu84p/bootloader-tilapia-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 bootloader-grouper-4.23.img
fca9f2b0d164bd743129341f20b11f53 /home/ssmirnov/nakasig-ktu84p/bootloader-tilapia-4.23.img
root@ssmirnov:/home/ssmirnov/nvflash#

---------- Post added at 01:44 PM ---------- Previous post was at 01:37 PM ----------

If I flash bootloader-grouper-4.23.img with md5:

df53028033c9eccf4fe5ba7bc198ce24

fastboot in left up corner:

Signature match
[Nexus 7 Original Development] Partitionator:
That means that the file that you are trying to flash isn't OK. Some factory images have a brocken bootloader.

Are you sure that your device is tilapia and not grouper?
[Nexus 7 Original Development] svs57:
I'm sure I have tilapia. I know that some BL are broken.

I read that correct BL has md5:

df53028033c9eccf4fe5ba7bc198ce24

And also that tilapia and grouper BL are the same

But I can't flash it. Neither from nvflash nor from fastboot.

No error but it not booting
[Nexus 7 Original Development] Partitionator:
Ok next Idea: Flashing a bootloader via staging like the OTAs do:

Download a OTA that contains ja bootloader.raw an extract it.

Then boot your device in the recovery and push the bootloader

adb push bootloader.raw /sdcard/bootloader.raw

And then write it to the staging Partition with dd

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

And reboot and hope the best:

adb reboot bootloader
[Nexus 7 Original Development] svs57:
Ok. Will do. Takes some time to download.

KTU84P-from-KTU84L doesn't contains BL.
[Nexus 7 Original Development] Partitionator:
Yes bootloader doesn't changed since 4.3 oder 4.2.2..

JZO54K-JRO03S contains a BL, i attached it to the post, but it's a grouper...
[Nexus 7 Original Development] svs57:
~ # dd if=/sdcard/bootloader.raw of=/dev/block/platform/sdhci-tegra.3/by-name/U
SP
4185+1 records in
4185+1 records out
2142860 bytes (2.0MB) copied, 0.276879 seconds, 7.4MB/s

Doesn't boot...

May be EMMC memory is dead?
[Nexus 7 Original Development] Partitionator:
You wanted to know what to doo with the other Files: http://xdaforums.com/showpost.php?p=48507424&postcount=16
[Nexus 7 Original Development] svs57:
I read this. But I havn't flash.cfg for 32g version and don't know where get it

---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------

I try but dump_bcd ended with error code 61 without any output
[Nexus 7 Original Development] Partitionator:
Maybe theres a way to convert your partition.txt to a flash.cfg.

You could also ask someone with a tilapia with 32GB.
[Nexus 7 Original Development] svs57:
Many thanks. Works!

I attached flash.cfg.txt for 32Gb created from partition.txt. I Change flash.cfg 16Gb with correct partition size and name.

Good luck
[Nexus 7 Original Development] Partitionator:
What works? Only the Converting of the File or your Tablet?
[Nexus 7 Original Development] svs57:
Bootloader works. 4.23 now. I can do normal boot, enter bl and recovery.

Thanks again.
[Nexus 7 Original Development] Partitionator:
:good:

Oh good. Nice to see that I helped you :o

I took me houres to find the correct syntax of the command ;)
[Nexus 7 Original Development] mrchezco1995:
is this for N7 WiFi + 3G only?

Hi there, I have a question.... Does this tool will only work on Nexus 7 WiFi + 3G (Tilapia) variant or will work too on WiFi only (Grouper) ? Was thinking to backup my blobs just to be safe or no need to for wifi only variant?

I got 4.23 bootloader btw......
[Nexus 7 Original Development] Partitionator:
It was desinged for the Wifi only variant but it also works with the wifi + 3g variant ;). Bootloader doesn't matter, so it should work for you :)
[Nexus 7 Original Development] mrchezco1995:
You sure? Can I go back to 4.23 after backing up my nvflash?

I'm running stock rooted 4.4.4 btw....
[Nexus 7 Original Development] Partitionator:
Yes
[Nexus 7 Original Development] KrzychuG:
Mind sharing how did you do that? I got stuck on my N7 (16GB) on 4.13 bootloader after backing up all the files required for nvflash. Now, i wanted to update to L and can't due to bootloader issues. I've got the correct file, but fastboot always denies flashing it.

C:\Nexus 7\2\nvflash-tools-win32>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
FAILED (remote: (BadParameter))
finished. total time: 0.406s

I also see the "Singnature match" message on top of the screen. I've tried to restore everything from scrach using nvflash like described in here but it ends up with the same error in fastboot.

In fact, it's a bit worse than before and i stucked in APX mode and can boot to fastboot only from that via "nvflash --resume --download 8 boot.img --go", but that's all. Afrer reboot it lands in APX again. Flashing that "nvflash --resume --rawdevicewrite 0 2688 bricksafe.img" doesn't really seem to help.
[Nexus 7 Original Development] svs57:
What i did is descided here

http://xdaforums.com/showpost.php?p=48507424&postcount=16
[Nexus 7 Original Development] Partitionator:
Try fastboot erase misc before flashing the bl
[Nexus 7 Original Development] KrzychuG:
Will do as soon as it starts working in APX mode again. I tried to flash bricksafe again, it went fine but now it's not even being detected in APX. All i see is unkown device popping up after a 20-30 seconds when plugged in to PC. It's possible that bettery died despite being 100% charged 2 hours ago. Too bad it won't charge in that state. Will have to disassemble it later on and charge it that way.

Huh, it's even funnier since i got mainboard replaced 2 months ago on warranty which just run out and made all the backups just to secure it for the future. It doesn't seem to help me much so far, in fact quite the oppsite but will see ;P

PS. I hate nVidia based devices, they're nothing but trouble in case if sudden death.
[Nexus 7 Original Development] Partitionator:
Try removing battery and hold vol+ while reconnecting and then press power while still holding vol+
[Nexus 7 Original Development] Partitionator:
Try flashing the flatline bootloader fromnthe flatline recovery.
[Nexus 7 Original Development] KrzychuG:
Hard to say if it does anything. Flatline recovery flashes and boots fine. Flashing flatline bootloader from that recovery seems to work (no error message), but after rebooting it still says 4.13 and i still can't update it to 4.23 - same error message as before. In fact, i most likely been using flatline bootloader since the day i flashed it for backup. I also noticed that my partitions were messed up and could not be mounted. I assume it's due to the attempt of flashing 5.0. Formating them in recovery did the job but it doesn't affect bootloader.

// Update:

Hah, fixed it. It's the flatline bootloader that mess it all. You have to flash original, unmodified 4.13 (no idea why the one i had on my disk didn't work) and then you can do whatever the hell you want. It's all here.

Thanks for your time, your "unbricking tutorial" brought back fastboot after all so that's confirmed.