yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] sparksco:
I mentioned it quite awhile back in the thread.

http://xdaforums.com/showthread.php?p=34101306
[Nexus 7 Android Development] sluflyer06:
derp, I think I needed to be doing less multitasking at work and focus on 1 or the other, I"ve flashed this stuff countless times on my GN, must have had a brain fart...I THINK (not sure) I was trying to write to the wrong partition. Unfortunately I didn't bring my 7 to work today so I'll have to wait until I get home to flash it again. I swear if thats what I was doing I'm gonna hate myself for a few minutes.
[Nexus 7 Android Development] JaZart:
Flashes but my bootloader version stays at 3.34.
[Nexus 7 Android Development] tangcla:
I had to flash mine from fastboot for it to work. The CWM file didn't work.
[Nexus 7 Android Development] shrome99:
Could you please tell me which file you flashed (link to the img)? Also, I assume a cache/dalvik wipe would be required.
[Nexus 7 Android Development] sparksco:
The img is inside the zip. +1 to wiping but I'm starting to think the boot loader is protecting itself from getting flashed in recovery on some devices.
[Nexus 7 Android Development] Protibus:
I saw how many were having issues flashing this boot loader zip and having just flashed AOKP's new 4.2 build today, I thought I'd see how it went, I used TWRP latest recovery, wiped cache, wiped Davlik, flashed boot loader without a problem.
[Nexus 7 Android Development] lmulli:
Ditto when using TWRP. Fastboot worked first time.
[Nexus 7 Android Development] shrome99:
I rebooted to bootloader, and did this - "fastboot flash bootloader bootloader.img" (the IMG extracted from the ZIP in the OP). I got a Signature Mismatch (in red) on the top left corner on the N7 and command prompt said FAILED (remote: (Invalid State)). I'm still on 3.34. What am I doing wrong?

Using latest TWRP, AOKP preview build, and franco kernel r30
[Nexus 7 Android Development] Protibus:
I had flashed this too and thought all was a success until I booted into recovery and saw my boot loader version at 3.34.
[Nexus 7 Android Development] paranoid android85:
Download this file http://www.mediafire.com/?bnr1fo74wwf4su3 then repeat the command line with the correct img name. Then reboot bootloader and you should have it
[Nexus 7 Android Development] Protibus:
I downloaded the factory 4.2 image and took the boot loader from that, flashed using ADB, all set. Easy as pie.
[Nexus 7 Android Development] n7of9:
the zip in the first post flashed fine via CMW, but my bootloader version still showed 3.41

so then i flashed this:

via fastboot commands, and the device wouldn't boot up...restored a nandroid, but now i'm back to where is tarted, rooted JB 4.2 with bootloader 3.41 :eek: :crying:
[Nexus 7 Android Development] paranoid android85:
I had trouble with the zip in the op, downloaded the mediafire one last night and flashed thru fastboot with no problems at all. Did you type:

Fastboot flash bootloader bootloader-grouper-4.13.img

Fastboot reboot-bootloader

?
[Nexus 7 Android Development] n7of9:
yes i did...it's weird isn't it? i even started it with 'fatsboot reboot-bootloader' to make sure everything was working

i just downloaded the nakasi google image and will try the bootloader.img from that, but it seems to be the same one that was in the mediafire link

EDIT: third time's a charm...the bootloader from the nakasi download worked :)
[Nexus 7 Android Development] Protibus:
This is what I ended up doing and flashed via fast boot. Finally had success.
[Nexus 7 Android Development] n7of9:
as did i :good:
[Nexus 7 Android Development] Hellscythe:
Do i need this to flash a 4.2 rom?
[Nexus 7 Android Development] n7of9:
not necessarily, but it's better to have a matched bootloader and ROM (for reasons someone more knowledgeable than me would have to explain)

n7'd from my n7
[Nexus 7 Android Development] Hellscythe:
Thanks mate

After reading a few pages here i got confused.

All i need to do is flash this in recovery and i am done?
[Nexus 7 Android Development] n7of9:
maybe... that worked for some but not everyone

Sent from my Nexus 4
[Nexus 7 Android Development] Mike:
So essentially I only need to update the boot loader when I plan on updating to 4.2? Is there any problem if you go back to a 4.1.2 ROM while on this 4.2 boot loader?
[Nexus 7 Android Development] sparksco:
I've flashed cm10 4.1.2 ROM on this bootloader and everything works fine.
[Nexus 7 Android Development] sparksco:
I updated the zip in the OP again this time with the bootloader image from the factory images since the one I pulled from my device gives a signature mismatch error. Hopefully people will have more success with this. I've also updated the md5 and other checksums.
[Nexus 7 Android Development] Mike:
Is this necessary to flash or no? I am about to flash my first rom on nexus7. Going with a 4.1.2 base for now
[Nexus 7 Android Development] sparksco:
Not it's not necessary. Think of a bootloader as the base for everything else in the android Operating System. It's the base for the kernel, recovery and rom, and probably other partitions as well. This bootloader ships with 4.2.
[Nexus 7 Android Development] tanoxxx:
Hi,

i tryed the zip for upgrade the bootloader, i used CWM and TWRP recovery, nothing, my bootloader still 3.41 :(

someone can help me please?

Thanks
[Nexus 7 Android Development] paranoid android85:
Try to use adb and flash it through fastboot. That's the only way i was able to upgrade bootloader
[Nexus 7 Android Development] tanoxxx:
Hi, thanks for the reply,

can you explainme step by step what i must to do?

Thanks
[Nexus 7 Android Development] n7of9:
search the forums, or google, how to install and use adb and fastboot...it's not difficult, but the information has been discussed and posted MANY times
[Nexus 7 Android Development] demkantor:
It would be nice if the op changed the wording here.

Firmware should never be flashed via the recovery as there is no check (other than signatures in certain situations) and a corrupt download can easily brick your devices (not limited to the nexus 7 by any means)

Always flash firmware (mainly radios and bootloaders) through fastboot, as if there is an error it will be given to you, if there is an incomplete flash just choose not too reboot until it is fixed and no harm done.

Besides to flash a SPL though recovery can't be done just by simply zipping an image and signing it, which is a good thing or many more people would have expensive paperweights.

Some things up here, follow a guide on how to set up adb and fastboot (they are all over xda including one or two I've made)

Then follow the simple steps to flash via fastboot only.
[Nexus 7 Android Development] shrome99:
I know how to use fastboot, not really sure what IMG file to flash though. The one in the ZIP in the OP gives me an error (see here - http://xdaforums.com/showpost.php?p=34572085&postcount=82) If someone can post the IMG file that worked for them, I'd be very grateful :)
[Nexus 7 Android Development] sparksco:
http://xdaforums.com/showpost.php?p=34612883&postcount=97
[Nexus 7 Android Development] poondog:
Why exactly is it recommended that we update to this bootloader when flashing a 4.2 ROM?

Scott from the cleanrom thread said it is best to, any reason? Or just to match the numbers? Or just to eliminate problems (that I don't have?)
[Nexus 7 Android Development] sparksco:
Why do people keep asking the same questions over and over again?...
[Nexus 7 Android Development] poondog:
Oops sorry

Sent from my CyanogenModded Nexus 7
[Nexus 7 Android Development] Hellscythe:
I can confirm it doesn't flash through recovery.

Bootloader version does not change.

This is very dangerous.
[Nexus 7 Android Development] sparksco:
For some people it does work. Dangerous, hardly...
[Nexus 7 Android Development] Travisdroidx2:
This did work fine for me the first time on mine and my wife's device. Then I reverted my N7 and the second time it did not work. I had to fast boot the image which is very simple and fast. Updated no problem.
[Nexus 7 Android Development] sparksco:
I would tell everyone for good measure wipe cache and dalvik-cache and flash twice maybe even more than twice. It might not work but if it's not going to flash on some devices it's not going to hurt anything by not changing the bootloader version.
[Nexus 7 Android Development] demkantor:
The problem with flashing a bootloader through recovery isn't when it doesn't work but when it does work and you didn't have a complete download.

If the .zip was incomplete or curropt in some way, and the person didn't check the md5sum, and they flashed through recovery, and it worked... bricked.

Learning to use fastboot is simple and will almost 100% eliminate this situation
[Nexus 7 Android Development] ezas:
Yet 9 out of 10 ROM/kernels in these threads are flashable. And most android devices are considered pretty much un-brickable. And most dev's include checksums for their downloads. Is there merit In what you said, of course.

Rather than derail this thread I'd be happy to take a discussion of this to PM or its own thread in the general sub-forum.
[Nexus 7 Android Development] demkantor:
android devices should never be considered unbrickable - here,s a test

open a terminal emulator and type

su
dd if=/dev/zero of=/dev/block/mmcblk0p18
sync
reboot

tell me if your phone/tablet turns back on...

and i don't consider the kernel or ROM firmware rather software, these will not brick your device being flashed through recovery. flashing a radio or Hboot *may* result in a brick. all i was doing was giving a warning... sorry for any disruptions here

anyhow, you are absolutely correct as this is not the place for this discussion, and i will leave it be. @OP, thanks for the post and sorry if i caused any disruptions
[Nexus 7 Android Development] sparksco:
You guys are hilarious! Did you know that the official OTA flashes the bootloader in recovery? Yet you don't see people complaining about bricked devices from it do you?
[Nexus 7 Android Development] sparksco:
I've Update the OP just for you! Now if you don't mind trolling somewhere else! :mad:
[Nexus 7 Android Development] ezas:
I equate this with suggesting someone take the fan off the CPU of a PC and suggesting that this was some kind of evidence that any CPU could suffer thermal failure. While in fact true, the expectation is that people will OC with a fan properly mounted.
[Nexus 7 Android Development] shrome99:
OK, I extracted and flashed the bootloader from the new ZIP in the OP, flashed it in bootloader mode (fastboot flash bootloader bootloader.img) and then did a "fastboot reboot-bootloader" and it works :D Thanks a lot :)
[Nexus 7 Android Development] swieder711:
NICE.

I was finally able to upgrade my bootloader from 3.34 to something new that works (4.13). I can now boot into bootloader and recovery from an OFF state. Could not do that previously!

Using the Zip file thru CWM did not work. I used Wug's toolkit to write the IMG directly into the Bootload.

thanks,
[Nexus 7 Android Development] carlz0206:
can you post how you did it and what version of wugz toolkit? or can i just flash thin in recovery(twrp latest)?

thanks

Edit; never mind already updated mine
[Nexus 7 Android Development] ks2332:
Could I flash this is terminal emulator in on a road trip so no computer
[Nexus 7 Android Development] ks2332:
Bump for an answer :)
[Nexus 7 Android Development] sparksco:
I don't think you can flash bootloader that way. You can't flash it from recovery?
[Nexus 7 Android Development] nexus7owner:
Can anyone post like a tutorial or something to explain how to flash this cause it doesn't seem to work from flashing from recovery.
[Nexus 7 Android Development] sparksco:
There's plenty of guides on XDA on how to use fastboot...
[Nexus 7 Android Development] smirkis:
you could. you need to use the if/of command but I'd check the md5 or you could end up with a dead tablet.
[Nexus 7 Android Development] demkantor:
Don't use dd commands unless you are fully aware of what you do, one little misstype easily can brick...
[Nexus 7 Android Development] smirkis:
if you make it a script, no mistyping possible. but its not as difficult as your making it. but yes if you dd if a file to the wrong partition you can screw stuff up. back in the day this was a big method people used. things just keep getting easier lol
[Nexus 7 Android Development] Push3r:
I Try many Roms! Then i go back to your Rom! Noch Problems, fast, smooth, nice! Great Work respect :D
[Nexus 7 Android Development] sparksco:
Wrong thread but thanks anyways :)

I'll have a new build up soon.
[Nexus 7 Android Development] Push3r:
Yes, wrong thread :banghead: sorry

Downloading new build now, thanks sparksco! TOP :)
[Nexus 7 Android Development] airmaxx23:
I tried flashing this in recovery a few times but had no luck so I installed it via fastboot and everything is fine.
[Nexus 7 Android Development] Mike:
Is this simply newer than the JZ054k (3.41) bootloader?
[Nexus 7 Android Development] nuchdog:
yes
[Nexus 7 Android Development] kapitanbasa:
was flashing like crazy via latest twrp but it just wont stick...flash via fastboot and everything went well...
[Nexus 7 Android Development] shinesthru:
I found that by flashing in TWRP, powering down, booting into recovery, then rebooting into boot loader it stuck fine the first time.
[Nexus 7 Android Development] ikslawlok:
Ils someone knows how sreen capture bootloader ?
[Nexus 7 Android Development] GreyCelt:
This didn't work for me. How do you boot into recovery from a powered down state? I thought the N7 could only get to recovery from being powered down through the bootloader. Unless I missed something, your step of powering down then booting into recovery is not possible. What hardware buttons do you push to get to recovery from being powered off?
[Nexus 7 Android Development] sparksco:
It doesn't stick for everyone for some reason or another. It worked for me and some others. Not sure if there's some magical steps to achieve this or not but it would be nice to know if there's some certain way to make it work 100% of the time.
[Nexus 7 Android Development] shinesthru:
You're right. My mistake. My point is that I powered down after flashing the new boot loader instead of flashing and then going right into boot loader to check if it stuck. It actually did not stick for me the fist 2 or 3 flashes before I powered down post flash. It may not be magic, but it worked for me. Good luck.
[Nexus 7 Android Development] malson:
best way..

The best way to upgrade bootloader is from bootloader menu... download right image from this URL: https://developers.google.com/android/nexus/images , then extract file "bootloader-grouper-4.13.img" and flash it.

How to do? In the official downloaded file there is "flash-base.sh" file with right sequences od commands:

fastboot flash bootloader bootloader-grouper-4.13.img

fastboot reboot-bootloader

Or use tools like Nexus 7 toolkit: http://xdaforums.com/showthread.php?t=1809195
[Nexus 7 Android Development] AZKJS:
Just flashed via twrp but my boot loader still says version 3.34. Looks like I'm going to have to turn on my computer for this one...
[Nexus 7 Android Development] sparksco:
That's a cool story bro. Care to explain why the ota flashes bootloader through recovery?
[Nexus 7 Android Development] awakener777:
Flashing in recovery didn't work for me, had to use fastboot.

This bootloader is so much better than the old one. No more issues.
[Nexus 7 Android Development] demkantor:
Again I'm not trolling you, the ota does flash through recovery but it also automatically does the proper checks for you (md5sum or whatever it uses) there is no other great way to receive an update other then making people download to computer and plug in device etc. Which is probably too much for novice users (as most people are)

That would effectively mean no updates for most if there wasn't an ota.

So again its not that firmware shouldn't be flashed ever in recovery its that people need to be more careful when doing so manually. And its not the issue of when it doesn't flash its when it does flash and the image is corrupt.

I know we have had this conversation before and I'm not trying to hijack your thread but it would have been nice to at least give a warning to people telling them this is available and it works but they would be safer to use fastboot

Any way, thanks for the flashable zip and I hope all is well
[Nexus 7 Android Development] sparksco:
What proper checks is that? It reads your build.prop to see what version of android your on. It checks the device to make sure no other devices can flash (my zip also does this). Then verifies your system to see if you really are on stock or not. There's no bootloader checks or anything before it writes your bootloader. Nor does it check the md5sums. There's no more chance of file corruption with this than with a ota zip so please stop mis-informing people.
[Nexus 7 Android Development] Protonus:
I also couldn't flash this via TWRP. It said it flashed OK, but each time I checked the bootloader it was the prior 3.41 version. I tried wiping cache/dalvik, shutting down after flashing and booting system and then rebooting into bootloader, etc. Basically tried everthing I saw in this thread, to no avail.

Then I flashed via fastboot, and it worked first try.

This is real easy.

0.) You'll need fastboot. This comes with ADB tools, the Nexus 7 toolbox, etc. If you don't already have these things, well, you probably shouldn't be doing this! Getting ADB working on your PC is day one android hacking.

1.) Download the .zip in the OP. Extract it, it will have a .IMG file inside. Copy that .IMG file to wherever you have the fastboot.exe file.

2.) Boot your tablet into the Bootloader (either choose reboot->Bootloader from your power options menu if you are using something like AOKP, or, power off your device, then power it back on while holding VOLUME DOWN + POWER).

3.) Connect the tablet to your PC.

4.) From a command prompt, change directory to where you have fastboot.exe. ie: cd\android\tools

5.) Issue this command (you can copy this, then right click the command prompt window and choose paste).

fastboot flash bootloader bootloader-grouper-4.13.img

6.) Fast boot should say (sans the times of course):

sending 'bootloader' <2096 KB> .... OKAY

writing 'bootloader'... OKAY

finished. total time: x.xxxs

7.) If you see that, it flashed OK. To verify, issue this command:

fastboot reboot-bootloader

That will make the tablet reload the bootloader. Now when you look at the version, it should say "4.13". And you're done.
[Nexus 7 Android Development] MetalMan2:
I too am having issues flashing the bootloader zip from the OP... tried flashing it a million different ways, doing different combinations of things to try to get it to stick, but am still stuck on 3.41.

And I can't flash in fastboot... since about a month and a half ago my N7 isn't detectable by a PC regardless of which USB port or USB cable is used. Strange thing is that OTG and charging all work just fine. I think it's a hardware issue, but somebody had a somewhat similar problem, and flashing the 4.13 bootloader fixed it for him.

So, I just wanna check and see if anybody has any further thoughts for me (other than returning/repairing my current N7...).
[Nexus 7 Android Development] AZImmortal:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

What million different ways are you referring to? As far as I know, there are only two ways to update the bootloader, either the flashable zip or fastboot. Have you tried getting your Nexus 7 detected on a different computer? And is it only fastboot that doesn't get detected?
[Nexus 7 Android Development] Protonus:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

Make sure you have usb debugging on in dev options. Try toggling it.

Try switching your usb computer connection mode, under storage, to MTP from PTP or vice versa, then plugging the cable

Try other pc's

Try connecting to a pc while you're in recovery instead of booted normal
[Nexus 7 Android Development] MetalMan2:
When I say "a million different ways" I am referring to the order in which I try things, and all flashing through recovery. For example: boot into bootloader, then boot into recovery and flash the bootloader zip, then boot back into bootloader and check to see if the new flash took. Or booting straight into recovery from system and booting into bootloader after flashing the bootloader zip. Etc.

I'm not even talking about fastboot because I don't have access through fastboot. ADB doesn't find the tablet either (because the PC doesn't register the Nexus 7 is connected).

You can bet I've tried all of these things, but went ahead and tried them again without luck. The problem is that there is no detection between Nexus 7 <--> PC other than the tablet recognizing power input and subsequently begin charging.

There's a thread where a number of people have reported the same issue I've had. Most of us have experienced this problem after using car chargers

http://xdaforums.com/showthread.php?t=1821536
[Nexus 7 Android Development] Southrice:
Had all the same problems as everyone else, So I used the nexus 7 toolkit, now on 4.13 :) FINALLY.
[Nexus 7 Android Development] sparksco:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

Just download and install pdanet it has all the correct drivers and will install them for you.
[Nexus 7 Android Development] MetalMan2:
Not sure how that would help me, since I already had all the drivers (and they were installed properly), and this thread is related to flashing the bootloader in recovery.

But I had PDAnet working with my N7 back when its USB worked
[Nexus 7 Android Development] sparksco:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

I never said that was related to this thread. Others (including you), went off topic about the fastboot and SDK subject. I was just trying to help you, jeesh!
[Nexus 7 Android Development] MetalMan2:
I understand you're trying to help, and I appreciate your willingness to help (please forgive the abrupt and rude attitude of my last post), but what I really need help with is with getting the bootloader to stick when flashed in recovery :)
[Nexus 7 Android Development] gemj95:
Is this the latest avaiable bootloader?

I ask that because when i bought my Nexus 7 it had the version 4.21 or so...
[Nexus 7 Android Development] Haad:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

Do i need to backup all my data from storage before i flash the new bootloader??

Sent from my Nexus 7
[Nexus 7 Android Development] Wally72:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

I used the Tool Kit to unlock and root my new Nexus. But my Nexus was with 4.1.1 after rooting, so I flashed the stable CM-10. After a while, I decided to upgrade to CM-10.1 and that's when my issues started. It flashed fine but after rebooting my N7 I was always stock on bootloops.

Long story short, it was my bootloaders version. Because I rooted while with 4.1.1, my bootloaders didn't upgrade. All was ok because I stayed on 4.1 using CM-10. When my issues started, I tried flashing the zip on the OP but wasn't working. Then, I took the image and tried to use adb...but my device wasn't recognized.:eek: Doing some research, I had to un install the drivers/and restart my pc, with finally installing the drivers againg with the Tool Kit. I placed the image in the same folder of the Tool Kit and flashed the image with adb. Everything went smooth after un installing and installing back the drivers. The good thing about flashing the image is that it doesn't wipe your device.:thumbup:

Thank you OP for the zip. Now my N7 is running 4.2.1 without issues!
[Nexus 7 Android Development] tgamble160:
Re: [Bootloader][Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

It would be smart to make a nandroid. But I had zero issues using the latest twrp. Just downloaded flashed and finished.

sent via nexus 7 in boss made @ quad core 1.9 ghz