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.
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!
If you can't boot into fastboot, return it to Asus (or Google). They are the only ones who can repair it. Sorry.
Try the latest official image (4.4.2): https://developers.google.com/android/nexus/images#nakasi
All I can say is follow this guide.
It even says that there is something wrong with the JWR66Y bootloader.
So if you'd like to have 4.3 then proceed as the guide says, if you want 4.4 then simply use the latest (KOT49H) factory image with the same commands.
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:
The Grouper and Tilapia files are identical. The only difference is the file name
Just wanted to make it clear, I still needed this to manually install the 4.4.3 image from Google's Factory Images page.
Flash the 4.23 bootloader from the 1st post in this thread and perform a factory reset. Think that should fix the storage problem. If not, reflash the 4.4.4 factory image, except the bootloader, since it's bugged.A few days ago I updated the Nexus7 of a friend of me from Jellybean 4.2.2 (Bootloader 4.18) to Kitkat 4.4.4 using Wugs Nexus Root Toolkit.
During flashing I got the error that bootloader 4.23 was required. Also I got the errors during flashing concerning invalid bootloader.
Finally I used the suggested "Force flash mode". Using this mode I succeeded to flash the factory image of Kitkat 4.4.4.
Everything looked OK..... But now I found that the bootloader is still version 4.18 Also I found that the Nexus7 changed from a 32GB to a 8GB WiFi Nexus 7. Tomorrow I will try to do a format of /data using TWRP to get the lost storage back, but what to do with the bootloader issue?
Will it be better to reflash back to Jellybean 4.2.2 (JDQ39) containing the current bootloader 4.18, then flash the alternative bootloader from JWR66V, then update to Jellybean 4.3 (JWR66Y) and then the last step update to Kitkat 4.4.4 (KTU84P)?
Or can I flash the boatloader from JWR66V into the current 4.4.4 (KTU84P) installation?
Any advice will be welcome!
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)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! .
Rgrds,
Ged.
bootloader-grouper-4.23.img from JWR66V
CRC32: c4eefbd8
MD5: df53028033c9eccf4fe5ba7bc198ce24
SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
bootloader-grouper-4.23.img from JWR66V
---------------------------------------
Size: 2.05 MiB (2,150,992 bytes)
MD5: df53028033c9eccf4fe5ba7bc198ce24
SHA-1: 7b28b45a035efb9aad9e61ad09b1906eb5508721
CRC32: c4eefbd8
bootloader-grouper-4.23.img from JWR66Y
---------------------------------------
Size: 2.05 MiB (2,151,068 bytes)
MD5: 5bdb2e87370cdb1a7ea14bb0c3e21390
SHA-1: ce2951e59da64fa57d281f47031364050c83f49c
CRC32: 7ab6084b
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://xdaforums.com/showthread.php?t=2150251
I just noticed the same. I'm going to see if rooting and doing a complete wipe helps.