[Q] JWR66Y nakasi factory image bootloader problem

Search This thread
G

GuestK00329

Guest
Does anyone else get a "invalidState" and "signature mismatch" message when trying to flash the bootloader.img from the new JWR66Y factory image? Flashing the previous bootloader.img from JWR66V image or JDQ39 image works just fine though.

Latest update:
So it seems that the bootloader from the latest KOT49H build is also non-functional, as someone pointed out. Here are the working bootloaders from JWR66V / KRT16S that others have posted in this thread:

bootloader-grouper-4.23.img
bootloader-tilapia-4.23.img

CRC32
c4eefbd8

MD5
df53028033c9eccf4fe5ba7bc198ce24

SHA-1
7b28b45a035efb9aad9e61ad09b1906eb5508721

The Grouper and Tilapia files are identical. The only difference is the file name :)
 
Last edited:

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
Does anyone else get a "invalidState" and "signature mismatch" message when trying to flash the bootloader.img from the new JWR66Y factory image? Flashing the previous bootloader.img from JWR66V image or JDQ39 image works just fine though.



On the 3g version, same thing :)

C:\Users\Glob>fastboot flash bootloader E:\Nexus\nakasig-jwr66y-factory-bdbb7bd7
\nakasig-jwr66y\bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.277s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.420s
 

GedBlake

Senior Member
Jan 5, 2013
889
606
Ashton-under-Lyne, Manchester, UK
This is weird...

I'm not naturally inclined to fastboot flash a bootloader, unless absolutely necessary - even for curiosities sake.

So I decided to take a closer look at the 4.23 bootloader image files themselves... from both build JWR66V and the very latest build, JWR66V... by running some checksum tests on both.

And here's the kicker... they are different... despite having the same name.

I have no idea why this should be, but it probably explains why some are having problems flashing it.

Here are my findings...

Code:
bootloader-grouper-4.23.img from JWR66V
---------------------------------------

Size:  2.05 MiB (2,150,992 bytes)

MD5:   df53028033c9eccf4fe5ba7bc198ce24

SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721

CRC32: c4eefbd8

Code:
bootloader-grouper-4.23.img from JWR66Y
---------------------------------------

Size:  2.05 MiB (2,151,068 bytes)

MD5:   5bdb2e87370cdb1a7ea14bb0c3e21390

SHA-1: ce2951e59da64fa57d281f47031364050c83f49c

CRC32: 7ab6084b

Make of this what you will...

I'm just puzzled! :confused:.

Rgrds,
Ged.
 
Last edited:

Auth

New member
Aug 23, 2013
3
0
Same here. Also after flashing system image and rebooting I get android warning icon on first loading. I had to push button to reboot device. But after all it works ok. So weird. :silly:
 
G

GuestK00329

Guest
This is weird...

I'm not naturally inclined to fastboot flash a bootloader, unless absolutely necessary - even for curiosities sake.

So I decided to take a closer look at the 4.23 bootloader image files themselves... from both build JWR66V and the very latest build, JWR66V... by running some checksum tests on both.

And here's the kicker... they are different... despite having the same name.

I have no idea why this should be, but it probably explains why some are having problems flashing it.

This is interesting. Is it possible to open or extract the .img files and investigate further what the differences might be?
 

simics

Member
Feb 5, 2012
21
9
confirmed, the BL in 66Y is not working. Keep getting Invalid State on the command prompt and the Nexus screen has red words saying invalid signature.

sending 'bootloader' (2100 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.438s


Got the "old" 4.23 BL from JWR66V and all is well again.

http://forum.xda-developers.com/showthread.php?t=2150251
 
Last edited:

glitchsys

Senior Member
May 3, 2006
212
67
Sacramento
confirmed, the BL in 66Y is not working. Keep getting Invalid State on the command prompt and the Nexus screen has red words saying invalid signature.

sending 'bootloader' (2100 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.438s


Got the "old" 4.23 BL from JWR66V and all is well again.

http://forum.xda-developers.com/showthread.php?t=2150251

I just noticed the same. I'm going to see if rooting and doing a complete wipe helps.

Wow guys, thanks so much. I've been trying to flash the official 4.3 image (JWR66Y) onto my Nexus 7 and I kept getting:

FAILED (remote: (InvalidState))

when it tried to write the bootloader. It would refuse to write the system image after because it detected the boot loader was still the older version, 4.18 or something. After finding this thread I found JWR66V at:
https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz

Was able to successfully write the 4.23 bootloader from that leaked built, and then I was able to write the JWR66Y image, since it now detected my bootloader was 4.23; It's weird the 4.23 bootloader in JWR66Y is broken but the 4.23 bootloader in JWR66V works just fine.
 
  • Like
Reactions: Pliind and legiong

GedBlake

Senior Member
Jan 5, 2013
889
606
Ashton-under-Lyne, Manchester, UK
This is interesting. Is it possible to open or extract the .img files and investigate further what the differences might be?

Hi, Eregoth...

Unlikely, I'm afraid... bootloader.img files are closed source and nobody knows what they contain except Asus (this is why there is no changelog, detailing the added features of v4.23 over v4.18, for example).

A bootloader is crypto-signed to the unique ID of a given Nexus 7, and when you flash a new one it 'inherits' the previous bootloaders data. The bootloader acts as a kind of security gate keeper and becomes active every time you switch on the Nexus 7. It's a system critical component of the Nexus 7, and without it... nothing happens:(. You can mess up pretty much any partition on the Nexus 7, and still recover from it... and is typically known as a softbrick, and is characterized by such egregious behaviour as bootlooping or refusal to boot... but as long as can you see the White-on-Black Google logo (which is the bootloader) upon boot or the White-on-Black battery charging animation (also the bootloader) when charging from a fully shut down state... as long as you can see these, the device isn't hardbricked and most of the time can be recovered.

If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader. I've used nvFlash before, on another tablet, and it's considerably more flexible/powerful than fastboot (you can change partition sizes, called 'layouts', for example)... but so far, nobody has been able to make nvFlash work on the Nexus 7:(.

This PDF document lodged by Nvidia Corporation with the United States Patent office in 2009 gives some indication of a what a bootloader is and what it's purpose is. Although somewhat technical, and a little out of date, it's worth reading.

-----------------------------------------------------------

All of which, though interesting, doesn't explain why the two v4.23 bootloaders are different. And reading through the posts here on this thread, it's clear there is a problem.

Fastboot flashing a bootloader is a risky procedure at the best of times, and always makes me nervous. And this kind of thing hardly inspires confidence in me.

Unless I've seriously misunderstood something, or I'm missing something, I think the only logical conclusion I can draw is Google have screwed up the bootloader that ships with Build JWR66Y.

I've just done a Google search on this topic, to see if it's been flagged up anywhere else, outside of XDA... but so far, nothing. But it's early days, and build JWR66Y has only been available for around 24hrs... so who knows what may crop up over the next few days. Unless Google quietly fixes the problem, I suspect many people wishing to restore back to stock 4.3 are going to have similar problems as those who have reported on this thread.

Anyway... I guess we'll see what happens...

Still damned odd, though.

Rgrds,
Ged.
 
Last edited:

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
An OTA update re-writes the bootloader also, so even if you do it yourself, or leave google to do it, it she same risk :)
Eg: The OTA update from 4.2.2 has corrupted my Radio partition, and now it seems that i am using a backup radio. Still nobody knows which partition is the radio, so i can fix the issue (the fstab.mmc says that the format of the radio partition is ext4, so if someone will do a dd dump i should be able to restore my radio)



Just received the ota 2mb size, strange
 
Last edited:

_never_mind_

Member
Dec 23, 2012
37
5
bootloader-grouper-4.23.img from the jwr66v and image-nakasi-jwr66y.zip ?

Does it work to use the bootloader-grouper-4.23.img from the jwr66v and then flash image-nakasi-jwr66y.zip ??
 
Jul 13, 2012
39
1
So what can I do to get it to work?! Just saying failed every time :(

Hey guys, sorry I didn't read the thread properly the first time, that's what happens when you rush!
Thanks!
 
Last edited:

Mou1908

Senior Member
Mar 27, 2013
50
6
Roma
I also encountered the same error, but in spite of this the flash went well and I have not encountered problems so far
 

dragon884

Member
Jan 4, 2012
34
5
Hi everyone,

Thought i was the only person having this issue. This is how i sorted my problem and i do hope that it'll fix anyone having this issue. This is what i done. Not a proper fix but at least i didn't see any errors.

1. Downloaded the JWR66V version
2. md5 checked it to confirm that it is the legit image file
0f426a1981338b637aa12ff7bbd197be nakasig-jwr66v-factory-aebc7b11.tgz
3. Used mskip's Toolkit to flash (supported on up to 4.2.2 but you can still use the JWR66V image. Just gives a warning message)
4. Confirmed no errors
5. Turned on my Nexus and did a brief setup
6. Nexus 7 picked up the update and i selected to install
7. After install root
8. Factory reset

Step 8 is optional.
 
Last edited:

Spco

Member
Jan 13, 2012
6
16
This is weird...

I'm not naturally inclined to fastboot flash a bootloader, unless absolutely necessary - even for curiosities sake.

So I decided to take a closer look at the 4.23 bootloader image files themselves... from both build JWR66V and the very latest build, JWR66V... by running some checksum tests on both.

And here's the kicker... they are different... despite having the same name.

I have no idea why this should be, but it probably explains why some are having problems flashing it.

Here are my findings...

Code:
bootloader-grouper-4.23.img from JWR66V
---------------------------------------

Size:  2.05 MiB (2,150,992 bytes)

MD5:   df53028033c9eccf4fe5ba7bc198ce24

SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721

CRC32: c4eefbd8

Code:
bootloader-grouper-4.23.img from JWR66Y
---------------------------------------

Size:  2.05 MiB (2,151,068 bytes)

MD5:   5bdb2e87370cdb1a7ea14bb0c3e21390

SHA-1: ce2951e59da64fa57d281f47031364050c83f49c

CRC32: 7ab6084b

Make of this what you will...

I'm just puzzled! :confused:.

Rgrds,
Ged.
This explains a lot and you're right. I extracted the bootloader from nakasi-jwr66v-factory-d341d356.tar for those who want the bootloader only and want to flash to the latest build.(nakasi-jwr66y)

bootloader-grouper-4.23.img from JWR66V

CRC32: c4eefbd8

MD5: df53028033c9eccf4fe5ba7bc198ce24

SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
 

Attachments

  • bootloader-grouper-4.23.img
    2.1 MB · Views: 23,984
Last edited:

legiong

Senior Member
Sep 13, 2011
65
14
Melbourne
I was able to fix mine after soft-bricking it by following this guide:
http://forums.androidcentral.com/nexus-4-rooting-roms-hacks/224861-guide-nexus-4-unlock-root.html

Apologies for linking to another forum.

The bootloader from JWR66Y failed like everyone else, so I downloaded the 4.3 JWR66V from the link that glitchsys posted above and used the bootloader from that.
After that I was able to use adb to flash JWR66Y downloaded from google.

JWR66Y:
https://dl.google.com/dl/android/aosp/nakasi-jwr66y-factory-1e503532.tgz
 

M.Q.

Senior Member
Aug 8, 2009
73
45
Krakow
I know that this is the Wifi version thread, but in case anyone with 3G have the same question - attached is the 4.23 bootloader for N7 3G extracted from JWR66V
After flashing it I was able to successfully flash the JWR66Y system image.
 

Attachments

  • bootloader-tilapia-4.23.img
    2.1 MB · Views: 7,219
Last edited:

acolin

New member
Sep 4, 2013
1
1
Bricked with grouper-4.23 bootloader

Just flashed the bootloader attached to a message in this thread:
MD5: df53028033c9eccf4fe5ba7bc198ce24
Checked md5sum before flashing.
Flashed fine with
$ fastboot flash bootloader bootloader-grouper-4.23.img
The signature matched message showed up on device, fastboot exited on host, then I rebooted the bootloader using menu, and... it rebooted into black screen of death. I believe this is what they call hardbricked from which there is no return ='(
The only thing I did not-by-the-book is to flash it twice, ie. executed the above fastboot command twice (with no reboot in between).

Others doing the same -- mind this accident.

EDIT: *before* flashing this bootloader I ran ./flash-all.sh which does 'fastboot erase boot', but, as my terminal history confirms, I flashed the bootloader after that (and nothing happened between the bootloader flashing and the fatal reboot).

EDIT: it came back to life on its own. The bootloader-version is 4.23, so it did flash successfully. The only explanation I have is that the new bootloader (4.23) does not start if the battery is too low and its threshold is higher than that in the previous version (4.13), if the previous version even had such a threshold at all. Another possibility of the same flavor is that the battery drained while in bootloader: when the (old) bootloader started the first time, the battery check succeeded, then the battery drained but the bootloader kept running (assuming it does not do battery checks while it runs), and finally after flashing and rebooting, upon starting the (new) bootloader, the battery check no longer succeeded, until I charged it up more.
LESSON: Charge your device to full capacity EVEN IF you plan to keep it plugged into USB during the whole operation.
 
Last edited:
  • Like
Reactions: patsy1000

woldranger

Senior Member
Apr 22, 2012
272
30
I know that this is the Wifi version thread, but in case anyone with 3G have the same question - attached is the 4.23 bootloader for N7 3G extracted from JWR66V
After flashing it I was able to successfully flash the JWR66Y system image.

You, kind sir, are a lifesaver! I was stuck on the very last part and it was telling me about the 4.18 bootloader even though the OP of the thread had walked me through it and gave me the ling to the updated bootloader - what he'd forgotten was that I was on the 3G NOT wifi. I tried yours and I'm up and running :D The battery was dropping and I was getting worried - it took me 9 hours to get it back after the botched attempt to unroot it using wug's toolkit.

Thanks again!


Tomorrow I'm gonna have a go at rerooting it....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    This is weird...

    I'm not naturally inclined to fastboot flash a bootloader, unless absolutely necessary - even for curiosities sake.

    So I decided to take a closer look at the 4.23 bootloader image files themselves... from both build JWR66V and the very latest build, JWR66V... by running some checksum tests on both.

    And here's the kicker... they are different... despite having the same name.

    I have no idea why this should be, but it probably explains why some are having problems flashing it.

    Here are my findings...

    Code:
    bootloader-grouper-4.23.img from JWR66V
    ---------------------------------------
    
    Size:  2.05 MiB (2,150,992 bytes)
    
    MD5:   df53028033c9eccf4fe5ba7bc198ce24
    
    SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
    
    CRC32: c4eefbd8

    Code:
    bootloader-grouper-4.23.img from JWR66Y
    ---------------------------------------
    
    Size:  2.05 MiB (2,151,068 bytes)
    
    MD5:   5bdb2e87370cdb1a7ea14bb0c3e21390
    
    SHA-1: ce2951e59da64fa57d281f47031364050c83f49c
    
    CRC32: 7ab6084b

    Make of this what you will...

    I'm just puzzled! :confused:.

    Rgrds,
    Ged.
    This explains a lot and you're right. I extracted the bootloader from nakasi-jwr66v-factory-d341d356.tar for those who want the bootloader only and want to flash to the latest build.(nakasi-jwr66y)

    bootloader-grouper-4.23.img from JWR66V

    CRC32: c4eefbd8

    MD5: df53028033c9eccf4fe5ba7bc198ce24

    SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
    8
    confirmed, the BL in 66Y is not working. Keep getting Invalid State on the command prompt and the Nexus screen has red words saying invalid signature.

    sending 'bootloader' (2100 KB)...
    OKAY [ 0.299s]
    writing 'bootloader'...
    FAILED (remote: (InvalidState))
    finished. total time: 0.438s


    Got the "old" 4.23 BL from JWR66V and all is well again.

    http://forum.xda-developers.com/showthread.php?t=2150251
    4
    This is weird...

    I'm not naturally inclined to fastboot flash a bootloader, unless absolutely necessary - even for curiosities sake.

    So I decided to take a closer look at the 4.23 bootloader image files themselves... from both build JWR66V and the very latest build, JWR66V... by running some checksum tests on both.

    And here's the kicker... they are different... despite having the same name.

    I have no idea why this should be, but it probably explains why some are having problems flashing it.

    Here are my findings...

    Code:
    bootloader-grouper-4.23.img from JWR66V
    ---------------------------------------
    
    Size:  2.05 MiB (2,150,992 bytes)
    
    MD5:   df53028033c9eccf4fe5ba7bc198ce24
    
    SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
    
    CRC32: c4eefbd8

    Code:
    bootloader-grouper-4.23.img from JWR66Y
    ---------------------------------------
    
    Size:  2.05 MiB (2,151,068 bytes)
    
    MD5:   5bdb2e87370cdb1a7ea14bb0c3e21390
    
    SHA-1: ce2951e59da64fa57d281f47031364050c83f49c
    
    CRC32: 7ab6084b

    Make of this what you will...

    I'm just puzzled! :confused:.

    Rgrds,
    Ged.
    4
    I know that this is the Wifi version thread, but in case anyone with 3G have the same question - attached is the 4.23 bootloader for N7 3G extracted from JWR66V
    After flashing it I was able to successfully flash the JWR66Y system image.
    2
    confirmed, the BL in 66Y is not working. Keep getting Invalid State on the command prompt and the Nexus screen has red words saying invalid signature.

    sending 'bootloader' (2100 KB)...
    OKAY [ 0.299s]
    writing 'bootloader'...
    FAILED (remote: (InvalidState))
    finished. total time: 0.438s


    Got the "old" 4.23 BL from JWR66V and all is well again.

    http://forum.xda-developers.com/showthread.php?t=2150251

    I just noticed the same. I'm going to see if rooting and doing a complete wipe helps.

    Wow guys, thanks so much. I've been trying to flash the official 4.3 image (JWR66Y) onto my Nexus 7 and I kept getting:

    FAILED (remote: (InvalidState))

    when it tried to write the bootloader. It would refuse to write the system image after because it detected the boot loader was still the older version, 4.18 or something. After finding this thread I found JWR66V at:
    https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz

    Was able to successfully write the 4.23 bootloader from that leaked built, and then I was able to write the JWR66Y image, since it now detected my bootloader was 4.23; It's weird the 4.23 bootloader in JWR66Y is broken but the 4.23 bootloader in JWR66V works just fine.