Upgrading from 4.1.1 to 4.4.2 on rooted Nexus 7 (2012 model)

[litfoo]

Hello all,

Looking for some advice/guidance please.

Currently have a rooted Nexus 7 (2012) running 4.1.1 and looking to upgrade to the latest KitKat verson 4.4.2

Would I have to sideload the factory image of 4.4.2 from Google?

If so, can someone point me in the right direction for instructions on Windows and MAc.

and if sideloading is not the correct method, what should I do?

Many thanks in advance,

litfoo

 

[Paul627g]

Hello,

I just recently helped a member having issues with their Nexus 7 tablet. In the end we upgraded the tablet to 4.4.2 and used the factory images to do so.

The information in the link below should help you along, feel free to ask questions.

http://forums.androidcentral.com/go...-wont-turn-unless-through-fast-boot-menu.html

 

[litfoo]

Hello,

I just recently helped a member having issues with their Nexus 7 tablet. In the end we upgraded the tablet to 4.4.2 and used the factory images to do so.

The information in the link below should help you along, feel free to ask questions.

http://forums.androidcentral.com/go...-wont-turn-unless-through-fast-boot-menu.html

Many thanks for this - will take a look

I assume it should work even though I am using a Nexus 7 (2012 model) ?

 

[Paul627g]

Many thanks for this - will take a look

I assume it should work even though I am using a Nexus 7 (2012 model) ?

Yes it will be the same process. Just make sure your getting the factory images for the Nexus 7 2012 model from Google's website. They are all located on the same page.

 

[litfoo]

Thanks again

Stupid question, but as I am rooted already (I see the 'unlocked' padlock on main Google screen when I boot up the Nexus 7) does that mean I can skip:

[GUIDE][MAC/PC/LINUX][4.2] Unlock, Root and Flash Recovery

and only have to do the below?

[GUIDE] Nexus 7 - Factory Image Restore

Thanks,

litfoo

 

[Paul627g]

Yes you can skip the unlocking the bootloader process.

Just follow thru with the flashing of factory images portion.

Sent from my awesome HTC One

 

[litfoo]

Yes you can skip the unlocking the bootloader process.

Just follow thru with the flashing of factory images portion.

Sent from my awesome HTC One

Hi Paul

Gave it a go and thought I was there.

Unfortunately it looks like something went wrong somewhere - Cannot seem to boot into the device anymore - get 'Booting Failed'

Stuck on main Google screen with Padlock unlocked and Start displayed within an arrow in top right (can cycle through Start>Restart Bootloader>Recovery mode>Power Off but that's it.

Output from my command window:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Program Files\Minimal ADB and Fastboot>cd fastbootfiles
The system cannot find the path specified.

C:\Program Files\Minimal ADB and Fastboot>cd\\
'\\'
CMD does not support UNC paths as current directories.

C:\Program Files\Minimal ADB and Fastboot>cd\

C:\>cd androidsdkwindows

C:\androidsdkwindows>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

C:\androidsdkwindows>cd sdk

C:\androidsdkwindows\sdk>cd platform-tools

C:\androidsdkwindows\sdk\platform-tools>fastboot devices
015d256487541a08        fastboot

C:\androidsdkwindows\sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [  0.031s]
finished. total time: 0.031s

C:\androidsdkwindows\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [  0.063s]
finished. total time: 0.063s

C:\androidsdkwindows\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [  0.031s]
finished. total time: 0.031s

C:\androidsdkwindows\sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [  0.063s]
finished. total time: 0.063s

C:\androidsdkwindows\sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [  1.500s]
finished. total time: 1.500s

C:\androidsdkwindows\sdk\platform-tools>fastboot flash bootloader bootloader-gro
uper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [  0.469s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.688s

C:\androidsdkwindows\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.016s]
finished. total time: 0.016s

C:\androidsdkwindows\sdk\platform-tools>fastboot -w update image-nakasi-kot49h.z
ip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256487541a08
--------------------------------------------
checking product...
OKAY [  0.016s]
checking version-bootloader...
FAILED

Device version-bootloader is '3.34'.
Update requires '4.23'.

finished. total time: 0.141s

C:\androidsdkwindows\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [  0.031s]
finished. total time: 0.031s

C:\androidsdkwindows\sdk\platform-tools>fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [  1.375s]
finished. total time: 1.375s

C:\androidsdkwindows\sdk\platform-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 36.672s]
finished. total time: 36.672s

C:\androidsdkwindows\sdk\platform-tools>fastboot reboot
rebooting...

finished. total time: 0.016s

C:\androidsdkwindows\sdk\platform-tools>fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [  1.375s]
finished. total time: 1.375s

C:\androidsdkwindows\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Exit without Unlocking
OKAY [  8.750s]
finished. total time: 8.750s

C:\androidsdkwindows\sdk\platform-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [  5.484s]
finished. total time: 5.484s

C:\androidsdkwindows\sdk\platform-tools>fastboot reboot
rebooting...

finished. total time: 0.016s

C:\androidsdkwindows\sdk\platform-tools>

Hope I can sort this out somehow - Advice appreciated

litfoo

 

[Paul627g]

First when you downloaded the factory images from Google did you unzip them as I showed in the thread below?

http://forums.androidcentral.com/go...nless-through-fast-boot-menu.html#post3332112

If so you should have been able to boot into your bootloader, do the following command to verify you have a connection.

fastboot devices

Get a random serial number returned which verifies you have a working connection.


Next go into those unzipped files and click on the " flash all " file and it will handle the flashing from there.

 

[litfoo]

Hi Paul,

Merry Christmas - hope you had a good one.

Not much progress I am sad to say.

I ran your

fastboot devices

and got:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>cd\

C:\>cd androidsdkwindows

C:\androidsdkwindows>dir
 Volume in drive C has no label.
 Volume Serial Number is F025-F1CD

 Directory of C:\androidsdkwindows

23/12/2013  19:28    <DIR>          .
23/12/2013  19:28    <DIR>          ..
23/12/2013  19:30    <DIR>          eclipse
23/12/2013  19:21    <DIR>          sdk
               0 File(s)              0 bytes
               4 Dir(s)  43,140,870,144 bytes free

C:\androidsdkwindows>cd sdk

C:\androidsdkwindows\sdk>cd platform-tools

C:\androidsdkwindows\sdk\platform-tools>fastboot devices
015d256487541a08        fastboot

C:\androidsdkwindows\sdk\platform-tools>

Then I ran the flash-all.bat file and got

...
(bootloader) Bootloader is already unlocked
OKAY [  0.016s]
finished. total time: 0.016s
erasing 'boot'...
OKAY [  0.109s]
finished. total time: 0.109s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [  0.125s]
finished. total time: 0.125s
erasing 'recovery'...
OKAY [  0.109s]
finished. total time: 0.109s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [  0.125s]
finished. total time: 0.125s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [  0.953s]
finished. total time: 0.953s
sending 'bootloader' (3911 KB)...
OKAY [  0.484s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.688s
rebooting into bootloader...
OKAY [  0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256487541a08
--------------------------------------------
checking product...
OKAY [  0.016s]
checking version-bootloader...
FAILED

Device version-bootloader is '3.34'.
Update requires '4.23'.

finished. total time: 0.125s
Press any key to exit...

Not sure why it is saying:

Device version-bootloader is '3.34'.
Update requires '4.23'.

Please advise

thanks,

litfoo

 

[GedBlake]

Hi, litfoo...

The problem could be the bootloader... as seems to be the case from your output...

sending 'bootloader' (3911 KB)...
OKAY [  0.484s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.688s
rebooting into bootloader...

As far back as Jellybean 4.3, there have been known issues fastboot flashing the v4.23 bootloader... specifically the one from Jellybean 4.3 build JWR66Y. See this thread for more details... (it results in 'InvalidState' errors).

Since then, KitKat 4.4 and 4.4.2 have made their appearance on the Nexus 7, and it appears that Google have made an even bigger mess of things regarding the v4.23 bootloader that ships with the factory stock images.

You should read this thread, over on XDA...

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

The upshot of this rather in depth technical thread, is you need to AVOID the v4.23 bootloader from KitKat build KOT49H... and acquire the v4.23 bootloader from Jellybean 4.3 build JWR66V - (and NOT from build JWR66Y, which has similar problems)... and flash that one instead.

Here's my 'take' on what precisely is going wrong for you...

During the fastboot flash process back to Google factory stock, everything (except the bootloader) gets erased, after which the new (v4.23) bootloader overwrites the old (v3.34) bootloader.

For you, this is failing to happen... for possible reasons as given above (ie., it's corrupt, damaged or Google have just screwed it up!).

Since the rest of the factory stock flash process expects to find the new bootloader (v4.23) correctly flashed and in place... AND DOESN'T... it subsequently reports the error...

Device version-bootloader is '3.34'.
Update requires '4.23'

If you want the v4.23 bootloader ".img" file, get it from any of the JWR66V, KRT16O, KRT16S Google factory images.... and NOT from KOT49H.

A valid MD5 signature for the CORRECT v4.23 bootloader ".img" file for WiFi only ('grouper/nakasi') Nexus 7 devices is...

MD5:     df53028033c9eccf4fe5ba7bc198ce24

A copy of the v4.23 booloader known to work (ie., fastboot flash without errors) is available at the bottom of this post, available here.

Download it, and exchange it with the the v4.23 bootloader from KitKat build KOTH49H... and try flashing KitKat again.

Whatever you chose to do... PLEASE BE CARERUL. If the Nexus 7 can be said to have an Achilles Heel or weakness, then it's flasing a new bootloader.

One little mistake... and the device is permanently hard bricked... and from which there is no recovery.

Take care, and thoroughly read the links I've included above.

Good luck... and hope this helps.

Rgrds,
Ged.

 

[litfoo]

It worked!!! O

Thanks very much Paul - appreciate your patience and guidance - thought I was gonna have a bricked device along the way.

As per your advice, I swapped out the bootloader image and that worked.

I had a different MD5 signature but decided to procees anyway.

Delighted when I saw the welcome screen.

Cheers

litfoo

...
(bootloader) Bootloader is already unlocked
OKAY [  0.016s]
finished. total time: 0.016s
erasing 'boot'...
OKAY [  0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [  0.047s]
finished. total time: 0.047s
erasing 'recovery'...
OKAY [  0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [  0.063s]
finished. total time: 0.063s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [  0.891s]
finished. total time: 0.891s
sending 'bootloader' (2100 KB)...
OKAY [  0.266s]
writing 'bootloader'...
OKAY [  0.703s]
finished. total time: 0.969s
rebooting into bootloader...
OKAY [  0.031s]
finished. total time: 0.031s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d256487541a08
--------------------------------------------
checking product...
OKAY [  0.031s]
checking version-bootloader...
OKAY [  0.031s]
sending 'boot' (4992 KB)...
OKAY [  0.609s]
writing 'boot'...
OKAY [  0.188s]
sending 'recovery' (5532 KB)...
OKAY [  0.688s]
writing 'recovery'...
OKAY [  0.188s]
erasing 'system'...
OKAY [  0.047s]
sending 'system' (625382 KB)...
OKAY [ 75.391s]
writing 'system'...
OKAY [ 30.484s]
erasing 'userdata'...
OKAY [  0.891s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 14442037248
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8176
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 3525888
    Block groups: 108
    Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 55.578s]
erasing 'cache'...
OKAY [  0.031s]
formatting 'cache' partition...
Creating filesystem with parameters:
    Size: 464519168
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 7088
    Inode size: 256
    Journal blocks: 1772
    Label:
    Blocks: 113408
    Block groups: 4
    Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [  2.016s]
rebooting...

finished. total time: 166.391s
Press any key to exit...

 

[eawooten]

I don't know if its better to bump an old thread, or start a new one, but here goes nothing.

I'm having the same problem as litfoo was, but I still can't seem to get it to work even after switching out the bootloader image. I've checked and double-checked the MD5s, and I always match the 'correct' bootloader.

Here's output from my flash-all.bat:

...
(bootloader) Bootloader is already unlocked
OKAY [  0.020s]
finished. total time: 0.021s
erasing 'boot'...
OKAY [  0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [  0.020s]
finished. total time: 0.021s
erasing 'recovery'...
OKAY [  0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [  0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [  0.031s]
finished. total time: 0.031s
sending 'bootloader' (2100 KB)...
OKAY [  0.273s]
writing 'bootloader'...
FAILED (remote: ()
finished. total time: 0.851s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
archive does not contain 'boot.sig'
error: out of memory

...and on-screen it shows "Signature match." right before it freezes.

Is anyone familiar with what might be going on with my device?

Thanks for your time!