[Q] JWR66Y nakasi factory image bootloader problem

woldranger · Sep 15, 2013

M.Q. said:
You're welcome I'm glad I could help.

It's a little strange though, I was told by the OP from my thread who helped me through my problems, that the bootloader image you that I used from your link wasn't for the 3G, but actually the WIFI which happened to be identical - at the end of the day, I'm not fussed either way - it's done and I will be selling the tablet tonight

ccjb100 · Oct 1, 2013

Hey BIG shoutout and thanks to everyone in this thread. You all saved my butt today.

I too had the same issue described here.

What happened: I had a friends Nexus 7 that was always failing to update. Attempting to OTA update would always give the Android robot laying down with a red exclamation over it every time. It was still on 4.1.2. Anyhow I took and tried to fix it up. Doing a factory reset and trying again gave same result. Hooked it up to Nexus Root Toolkit and attempted a full factory image load of 4.2.2. That froze/failed trying to send some of img's over to flash. I could still get bootloader but completely borked recovery and would not boot normally. After fiddling with my usb setup I was finally able to unlock the bootloader and then manually reflash stock 4.1.2 recovery. Then I tried again to do a full factory image load of 4.3 (JWR66Y) and immediately failed out of bootloader flash with the "invalid state" error (I was on 4.18 bootloader at the time). At this point I became somewhat concerned. Although I could still boot bootloader it was freezing up sometimes. Anyway, once I found this thread I went back again and tried JWR66V and tried a full load through NRT. Everything loaded perfectly this time (including the 4.23 bootloader from JWR66V) and I booted up normally. I was able to OTA to newest update like normal once I had JWR66V in place.

Thank you so much everyone!

mkrogh65 · Oct 4, 2013

Sooo im stuck on bootloader after trying to install nakasi-jwr66y-factory-1e503532
But it says something about missing
boot.sig
Recovery.sig
And Bootloader is 4.18
And Needs to be bootloader 4.28

At this point im stock and need help before I really mess this up
I can boot into bootloader, and not get further than that.

Can I install JWR66V via wugfresh ?
And bee home free?

Mick

---------- Post added at 09:36 AM ---------- Previous post was at 09:36 AM ----------

---------- Post added at 10:34 AM ---------- Previous post was at 09:36 AM ----------

ccjb100 said:
Hey BIG shoutout and thanks to everyone in this thread. You all saved my butt today. I too had the same issue described here.

What happened: I had a friends Nexus 7 that was always failing to update. Attempting to OTA update would always give the Android robot laying down with a red exclamation over it every time. It was still on 4.1.2. Anyhow I took and tried to fix it up. Doing a factory reset and trying again gave same result. Hooked it up to Nexus Root Toolkit and attempted a full factory image load of 4.2.2. That froze/failed trying to send some of img's over to flash. I could still get bootloader but completely borked recovery and would not boot normally. After fiddling with my usb setup I was finally able to unlock the bootloader and then manually reflash stock 4.1.2 recovery. Then I tried again to do a full factory image load of 4.3 (JWR66Y) and immediately failed out of bootloader flash with the "invalid state" error (I was on 4.18 bootloader at the time). At this point I became somewhat concerned. Although I could still boot bootloader it was freezing up sometimes. Anyway, once I found this thread I went back again and tried JWR66V and tried a full load through NRT. Everything loaded perfectly this time (including the 4.23 bootloader from JWR66V) and I booted up normally. I was able to OTA to newest update like normal once I had JWR66V in place.

Thank you so much everyone!

mkrogh65 said:
Sooo im stuck on bootloader after trying to install nakasi-jwr66y-factory-1e503532
But it says something about missing
boot.sig
Recovery.sig
And Bootloader is 4.18
And Needs to be bootloader 4.28

At this point im stock and need help before I really mess this up
I can boot into bootloader, and not get further than that.

Can I install JWR66V via wugfresh ?
And bee home free?

Mick

---------- Post added at 09:36 AM ---------- Previous post was at 09:36 AM ----------

Installed this one via Nexus root ToolKit v.1.7.2
JWR66V at:
https://dl.google.com/dl/android/aos...y-d341d356.tgz

Now im back "online", and have bootloader 4.28, and android 4.3
System says there is an update, but I guess ill have to OEM lock my bootloader first. (before updating)

If this helps any1

Mike out.

---------- Post added at 10:45 AM ---------- Previous post was at 10:34 AM ----------

mkrogh65 said:
Sooo im stuck on bootloader after trying to install nakasi-jwr66y-factory-1e503532
But it says something about missing
boot.sig
Recovery.sig
And Bootloader is 4.18
And Needs to be bootloader 4.28

At this point im stock and need help before I really mess this up
I can boot into bootloader, and not get further than that.

Can I install JWR66V via wugfresh ?
And bee home free?

Mick

---------- Post added at 09:36 AM ---------- Previous post was at 09:36 AM ----------

---------- Post added at 10:34 AM ---------- Previous post was at 09:36 AM ----------

Installed this one via Nexus root ToolKit v.1.7.2
JWR66V at:
https://dl.google.com/dl/android/aos...y-d341d356.tgz

Now im back "online", and have bootloader 4.28, and android 4.3
System says there is an update, but I guess ill have to OEM lock my bootloader first. (before updating)

If this helps any1

Mike out.

Via Nexus root toolkit.
After OEM lock my bootloader I got Android JWR66Y on my device

Tnx myself

Mike

jb0ne · Oct 5, 2013

Wow I didn't even realize how dangerous flashing your bootloader is. I flashed a stock 4.3 JWR66V on, and flashed a 4.23 bootloader, and have since managed to update to OTA JWR66Y. I had no problems, but now I'm wondering which bootloader I have (V or Y), and whether was I just lucky.

How would I check which 4.23 bootloader I have on my device?

tatazeuz · Oct 6, 2013

jb0ne said:
Wow I didn't even realize how dangerous flashing your bootloader is. I flashed a stock 4.3 JWR66V on, and flashed a 4.23 bootloader, and have since managed to update to OTA JWR66Y. I had no problems, but now I'm wondering which bootloader I have (V or Y), and whether was I just lucky.

How would I check which 4.23 bootloader I have on my device?

They're exactly the same bootloader. Theres absolutely no difference between JWR66V and JWR66Y bootloaders.

GedBlake · Oct 6, 2013

tatazeuz said:
They're exactly the same bootloader. Theres absolutely no difference between JWR66V and JWR66Y bootloaders.

Hi, tatazeuz...

You'd certainly expect them to be identical, wouldn't you?... but they aren't. There's actually a 76 byte discrepancy between the two.

My own investigations (as previously reported), yielded the following puzzling results...

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

And this causes problems when attempting to fastboot flash the bootloader from build JWR66Y... you get 'signature mismatch' and 'InvalidState' errors

.

It's a know issue - as well as this thread, it's also referenced in this sticky by the OP himself.

But nobody seems to know quite why the two bootloaders are different. I've done a bit of Googling around to see if I can find an answer... but so far, I've found nothing.

Probably just one those mysteries that will forever go unanswered

.

Rgrds,
Ged.

tatazeuz · Oct 6, 2013

GedBlake said:
Hi, tatazeuz...

You'd certainly expect them to be identical, wouldn't you?... but they aren't. There's actually a 76 byte discrepancy between the two.

My own investigations (as previously reported), yielded the following puzzling results...

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

And this causes problems when attempting to fastboot flash the bootloader from build JWR66Y... you get 'signature mismatch' and 'InvalidState' errors.

It's a know issue - as well as this thread, it's also referenced in this sticky by the OP himself.

But nobody seems to know quite why the two bootloaders are different. I've done a bit of Googling around to see if I can find an answer... but so far, I've found nothing.

Probably just one those mysteries that will forever go unanswered.

Rgrds,
Ged.

I was aware of this, although I'm pretty sure that somebody screwed when compiling the package, because if you update vía OTA, the bootloader is exactly the same. And since the guy that I replied to updated via OTA, I said that.

jb0ne · Oct 6, 2013

tatazeuz said:
They're exactly the same bootloader. Theres absolutely no difference between JWR66V and JWR66Y bootloaders.

Really? I thought there was some discussion on this thread earlier about different file sizes and md5s for the 4.23's?

tatazeuz · Oct 6, 2013

jb0ne said:
Really? I thought there was some discussion on this thread earlier about different file sizes and md5s for the 4.23's?

The bootloader in the JWR66Y factory image is corrupted, thats why they have different sizes.

jb0ne · Oct 6, 2013

So since mine is working that means I must have put the JWR66V one on? I'd really like to be able to know for sure, but I don't know where the .img file is stored on the device so I can md5 it.

Edit: Eh, I just found the .img file on my hard drive - it's the V one. So I guess I got lucky not going too bleeding edge.

Edit2: Interestingly enough, while the file size is identical to the byte for the V bootloader, the md5 is different! It's
df53028033c9eccf4fe5ba7bc198ce24

I downloaded it from one of the threads here but don't recall which.

ctbaker · Nov 10, 2013

Thanks to everyone that helped in this thread. I just about had a heart attack thinking I just made my daughter's nexus 7 into an expensive brick!

Luxferro · Nov 13, 2013

I also had problems flashing the 4.23 bootloader from googles jwr66y factory images. Thanks for pointing out the previous version of 4.23. It worked fine.

Now I can move on to android 4.4 (kitkat)

hanatha · Nov 21, 2013

Life saver for my Nexus 7 wifi

Thanks everyone. Brilliant that someone found out a faulty bootloader - jwr66y.
Just to share my experience.
After flashing the jwr66v bootloader, I failed to update jwr66y zip so I updated with jwr66v zip.
Later after rebooting the machine, I use system update to bring it to jwr66y.

fushla · Nov 21, 2013

Anyone need to restore their bootloader? It seems both bootloaders (4.4 and 4.3) have been replaced (the size is different than previous ones) at the developer page .... Curious if everything works now.. I'm scared to check though

Sent from my Nexus 7 using XDA Premium 4 mobile app

sheridanmp · Nov 23, 2013

Thanks, works but...

Thanks to the various people that provided the info to load bootloader 4.23. It worked though I still could not flash JWR66Y as I got the same invalid state happening so tried 4.4 (forgotten the code) and that loaded just fine.
Good enough. I now have:
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader version - 4.23
baseband version - n/a
Serial # - long number
Signing - not defined yet
Lock state - unlocked
But the overall response is very slow when using the touch screen etc. Anyone else having this happen?
Thanks again
Sher

bftb0 · Dec 17, 2013

Follow-up: SAME ISSUE WITH KOT49H FACTORY IMAGE

FYI, this same problem also exists with the bootloader image file shipped in the newer KOT49H Google "Factory Image". Thought I would mention it here in case anyone reads through this thread.

[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google

The bottom line (at the moment) is that the correct version of the bootloader file (for flashing with fastboot or nvflash) "bootloader-grouper-4.23.img" is:

2,150,992 bytes long. MD5: df53028033c9eccf4fe5ba7bc198ce24

and is present in the JWR66V, KRT16O, and KRT16S factory images.

The file of the same name which are derived from the JWR66Y and KOT49H Google factory images should be avoided.

malibu_23 · Dec 24, 2013

bftb0 said:
FYI, this same problem also exists with the bootloader image file shipped in the newer KOT49H Google "Factory Image". Thought I would mention it here in case anyone reads through this thread.

[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google

The bottom line (at the moment) is that the correct version of the bootloader file (for flashing with fastboot or nvflash) "bootloader-grouper-4.23.img" is:

2,150,992 bytes long. MD5: df53028033c9eccf4fe5ba7bc198ce24

and is present in the JWR66V, KRT16O, and KRT16S factory images.

The file of the same name which are derived from the JWR66Y and KOT49H Google factory images should be avoided.

This is likely why i cant flash 4.4.2 on my n7 2012 wifi. So what do i do? swap th bootlaoder from krt16s?

bftb0 · Dec 24, 2013

malibu_23 said:
This is likely why i cant flash 4.4.2 on my n7 2012 wifi. So what do i do? swap th bootlaoder from krt16s?

Sure. Or if you are already on the 4.23 bootloader, there is no need to flash it again.

sportscrazed2 · Jan 19, 2014

bftb0 said:
Sure. Or if you are already on the 4.23 bootloader, there is no need to flash it again.

So I replaced the bootloader file downloaded directly from google with the one provided in op and everything worked right away the way it was supposed too. Does nobody at google test this **** anymore?

MTodd88 · Feb 3, 2014

Cannot boot

So the 2nd time I fired up my Nexus 7 it proceeds to tell me that I need to update some files. I tell it to go ahead and now it will not boot up. I get the Google start page and then the "X" logo flashing but that is it. I have read a bunch of stuff around about how to fix the problem but I cannot get any of them to work. I can get to the Recovery page and to the Bootloader page but nothing happens from there. I have tried to wipe the data and no luck. I have tried to use WugFresh's root toolkit but this isnt working either because I apparently do not have USB Debugging enabled and I cannot get the device to boot up in order to enable that option.

Any help would be appreciated.

[Q] JWR66Y nakasi factory image bootloader problem

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Similar threads

Top Liked Posts