[REF] Nexus 7 Stock OTA URLs

osm0sis · Dec 12, 2013

oldblue910 said:
Yeah, the bootloader is probably named after an older version while actually being the correct version. That's been happening ever since JBQ left and someone else picked up doing the factory images.

The version number didn't change with the OTA though.. Also check it out:

7b28b45a035efb9aad9e61ad09b1906eb5508721 *jwr66v-bootloader-grouper-4.23.img - 2101kB
ce2951e59da64fa57d281f47031364050c83f49c *jwr66y-bootloader-grouper-4.23.img - 2101kB
7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16o-bootloader-grouper-4.23.img - 2101kB
7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16s-bootloader-grouper-4.23.img - 2101kB
1c25b3a40d47b8681b84761efb0750eb84d63f06 *kot49h-bootloader-grouper-4.23.img - 3912kB

Seems to me that "the real" 4.23 is the one that came with 66v (the initial version to contain it) and then again in KK up to krt16s, and these other 2 are anomalies, one for having a different checksum right in the middle of the other 3 which are the same, and the other for being big and possibly completely wrong. I'm going to check them out in HxD and see if I even want to venture flashing it.

Edit: 66y had a weird "msm-radio-update" header tacked on which is the only difference there, but still probably shouldn't be trusted over the other matching 3.

And kot49h is looking completely different, to the point where I think they f*cked up and included the flo-deb bootloader by mistake. It mentions partitions grouper-tilapia doesn't have like sbl1-3 and aboot. Downloading razor to be sure.

Edit 2: Confirmed. It's actually bootloader-flo-deb-04.02.img; That's a pretty gross oversight since it would likely brick our devices to flash it.

I checked everything else in the nakasi one and it all seems to be correct except for the bootloader, but still, it's sad that we can't trust the factory images anymore.

oldblue910 · Dec 12, 2013

osm0sis said:
The version number didn't change with the OTA though.. Also check it out:

7b28b45a035efb9aad9e61ad09b1906eb5508721 *jwr66v-bootloader-grouper-4.23.img - 2101kB
ce2951e59da64fa57d281f47031364050c83f49c *jwr66y-bootloader-grouper-4.23.img - 2101kB
7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16o-bootloader-grouper-4.23.img - 2101kB
7b28b45a035efb9aad9e61ad09b1906eb5508721 *krt16s-bootloader-grouper-4.23.img - 2101kB
1c25b3a40d47b8681b84761efb0750eb84d63f06 *kot49h-bootloader-grouper-4.23.img - 3912kB

Seems to me that "the real" 4.23 is the one that came with 66v (the initial version to contain it) and then again in KK up to krt16s, and these other 2 are anomalies, one for having a different checksum right in the middle of the other 3 which are the same, and the other for being big and possibly completely wrong. I'm going to check them out in HxD and see if I even want to venture flashing it.

Edit: 66y had a weird "msm-radio-update" header tacked on which is the only difference there, but still probably shouldn't be trusted over the other matching 3.

And kot49h is looking completely different, to the point where I think they f*cked up and included the flo-deb bootloader by mistake. It mentions partitions grouper-tilapia doesn't have like sbl1-3 and aboot. Downloading razor to be sure.

Edit 2: Confirmed. It's actually bootloader-flo-deb-04.02.img; That's a pretty gross oversight since it would likely brick our devices to flash it.

I checked everything else in the nakasi one and it all seems to be correct except for the bootloader, but still, it's sad that we can't trust the factory images anymore.

Holy crap! It's really amazing how sloppy the factory images have become since JBQ left.

tylercarter · Dec 12, 2013

oldblue910 said:
Holy crap! It's really amazing how sloppy the factory images have become since JBQ left.

Tell me about it. lol. How embarrassing posting broken links like that.

Sent from my Nexus 4 using Tapatalk

TheManii · Dec 12, 2013

Out of all the KOT49H factory images, so far the only ones with issues are the nakasi/nakasig bootloader files.
Everything (for all devices) else seems to both be correctly named and the correct contents.

Currently all the links on developers.google.com/android/nexus/images are correct (as in they point to actual files)

But yes since JBQ left the vast majority of factory images either have:

incorrect names
incorrect contents
both
missing files, in one case: missing everything except the script to flash them

There have been more errors in the factory images in the past quarter then there have been for the entire history of android,
though we didnt formally start getting factory images until the NS.
There may be reporting bias as #1 isnt really that big of a deal

At least not from goog itself, some previous devices did get some form of factory image from the original manufacturer, but they dont really count.
Nor were they always as complete as the current ones (ie generally a factory image every release with some exceptions)

Vyom · Dec 13, 2013

Well, it looks like Kitkat update hates me. I am unable to flash latest OTA KOT49H update.

I have TWRP Recovery installed with MultiROM and triple boot. (Stock Kitkat, CyanogenMod Jelly Bean and Ubuntu Touch). And now I am not able to flash the zip file for KOT49H update. I faced the same problem while updating from JB to KK, when I just had to reformat everything and start from scratch. But it doesn't seem right to flash *everything* as soon as an update comes (specially a 0.0.2 update).

So please help me out here! Following screenshot maybe helpful:

chi_heng · Dec 13, 2013

Sorry, misread your message earlier. Had no experience with Multi-boot, so can't tell that may be the cause of your failed OTA update. The updater script in KOT49H does contain a section to check the integrity of the stock Rom before writing them over with the updates, so I wonder if it may have looked wrongly at the other roms you have in your machine and halted the update process as it couldn't find what it expected.

Vyom said:
Well, it looks like Kitkat update hates me. I am unable to flash latest OTA KOT49H update.

I have TWRP Recovery installed with MultiROM and triple boot. (Stock Kitkat, CyanogenMod Jelly Bean and Ubuntu Touch). And now I am not able to flash the zip file for KOT49H update. I faced the same problem while updating from JB to KK, when I just had to reformat everything and start from scratch. But it doesn't seem right to flash *everything* as soon as an update comes (specially a 0.0.2 update).

Vyom · Dec 13, 2013

chi_heng said:
Sorry, misread your message earlier. Had no experience with Multi-boot, so can't tell that may be the cause of your failed OTA update. The updater script in KOT49H does contain a section to check the integrity of the stock Rom before writing them over with the updates, so I wonder if it may have looked wrongly at the other roms you have in your machine and halted the update process as it couldn't find what it expected.

Thanks for the reply, and as much as I want to find the solution for this problem, I decided I won't be installing this particular update (4.2.2).
The reason for this decision being the fact that Google have decided to remove a very useful feature or rather the ability to turn off the privacy settings for individual apps. (Refer this article: https://www.eff.org/deeplinks/2013/...cy-features-android-shortly-after-adding-them)

So, until Google decides to re-enable the same, I am going to choose privacy over security.

Imoseyon · Dec 14, 2013

Vyom said:
Well, it looks like Kitkat update hates me. I am unable to flash latest OTA KOT49H update.

I have TWRP Recovery installed with MultiROM and triple boot. (Stock Kitkat, CyanogenMod Jelly Bean and Ubuntu Touch). And now I am not able to flash the zip file for KOT49H update. I faced the same problem while updating from JB to KK, when I just had to reformat everything and start from scratch. But it doesn't seem right to flash *everything* as soon as an update comes (specially a 0.0.2 update).

So please help me out here! Following screenshot maybe helpful:

You're failing this check:

Code:

apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35") || abort("\"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35\" has unexpected contents.");

If you're brave enough you can flash this zip that I just put together:

http://www.box.com/shared/zbntry3ihffuliqp5f2z

Do a full backup first though.

fozzie · Dec 14, 2013

Imoseyon said:
You're failing this check:

Code:

apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35") || abort("\"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35\" has unexpected contents.");

If you're brave enough you can flash this zip that I just put together:

http://www.box.com/shared/zbntry3ihffuliqp5f2z

Do a full backup first though.

The LNX partition is the kernel partition iirc, do just needs the stock boot.img flashing.

Imoseyon · Dec 14, 2013

fozzie said:
The LNX partition is the kernel partition iirc, do just needs the stock boot.img flashing.

yup the zip i posted skips the kernel partition check along with others. Just flashing stock kernel may work but another check may fail.

RusherDude · Dec 14, 2013

No 4.4.1 OTA URL for Nexus 7 (grouper/tilapia)?

I find this strange, since Nexus 4,5,7 (flo/deb) and 10 got it before 4.4.2..

oldblue910 · Dec 14, 2013

RusherDude said:
No 4.4.1 OTA URL for Nexus 7 (grouper/tilapia)?

I find this strange, since Nexus 4,5,7 (flo/deb) and 10 got it before 4.4.2..

Yep, but grouper and tilapia didn't. It's happened before. The only device that ever saw 4.3.1 was the 2013 N7 LTE. There's plenty of historical precedent for it.

Sent from my Galaxy S4 Google Play Edition using Tapatalk

keneth_c · Dec 15, 2013

oldblue910 said:
Yep, but grouper and tilapia didn't. It's happened before. The only device that ever saw 4.3.1 was the 2013 N7 LTE. There's plenty of historical precedent for it.

Sent from my Galaxy S4 Google Play Edition using Tapatalk

No 4.4.1 for tilapia. 4.4.1 was skipped. We straight on 4.4.2 from 4.4

--
Sent from my Samsung S3 (GT-i9300) using Tapatalk

Vyom · Dec 15, 2013

Imoseyon said:
You're failing this check:

Code:

apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35") || abort("\"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5109760:c804e149ffe3595235595a35a25096d53e1c5ea2:5111808:40ea9855a3b10fd1e65ace0fc3b7bb19bec8bf35\" has unexpected contents.");

If you're brave enough you can flash this zip that I just put together:

http://www.box.com/shared/zbntry3ihffuliqp5f2z

Do a full backup first though.

I successfully updated to 4.2.2 after flashing your zip file. :good:

Thanks so much man!

PS: And as expected, AppsOrb stopped working after this update. Well, Google I hope you will bring it back in later updates.

osm0sis · Dec 15, 2013

Vyom said:
I successfully updated to 4.2.2 after flashing your zip file. :good:
Thanks so much man!

PS: And as expected, AppsOrb stopped working after this update. Well, Google I hope you will bring it back in later updates.

There's a great Xposed module that re-enables native App Ops.

RusherDude · Dec 15, 2013

oldblue910 said:
Yep, but grouper and tilapia didn't. It's happened before. The only device that ever saw 4.3.1 was the 2013 N7 LTE. There's plenty of historical precedent for it.

Sent from my Galaxy S4 Google Play Edition using Tapatalk

Yeah but.. 4.3.1 was only for N7 (flo/deb) and 4.4.1 was for EVERYONE but N7 (grouper/tilapia), is a completely different situation

keneth_c said:
No 4.4.1 for tilapia. 4.4.1 was skipped. We straight on 4.4.2 from 4.4

--
Sent from my Samsung S3 (GT-i9300) using Tapatalk

Ok. Thank you both!

osm0sis · Dec 20, 2013

Just another note about the factory images:

I was recently wondering why it seemed like my 16gb grouper was low on space, and of course assumed that it was because I had two user accounts on it. Recently I removed the second and still noticed it reported storage at 6gb total. Pretty much half of what it should be.

I did some tests and if you ever flashed the factory image userdata.img, even after erasing, it may reduce your usable data to that of the 8gb grouper device. JBQ basically confirms this in an unrelated topic here: https://groups.google.com/d/topic/android-building/Z6aUmEH9P4U/discussion

So the answer was to fastboot format userdata and let Android set it up again itself on boot, now I'm back to 13gb reported total storage and restoring my nandroid to see if it holds. :good:

@oldblue910 could you make notes about these issues on your factory images pages? I think the one about the incorrect bootloader being included is especially note-worthy to avoid people bricking.

bftb0 · Dec 23, 2013

@osm0sis

thanks for that link. I always wondered what the point of that userdata.img file was, given that:

- a factory flash should create a "blank" (empty) /data filesystem
- there are N7 devices of 3 different capacities, so what is the point of a given sparse file size?
- it is obvious from the speed (of that specific fastboot operation) that a file of that size is NOT being transferred.

etxeide · Dec 26, 2013

Thanks

aknorts · Jan 17, 2014

Awesome, thanks.

[REF] Nexus 7 Stock OTA URLs

Senior Recognized Developer / Contributor

Senior Member

Senior Member

Wiki Admin / Inactive RC

Member

Member

Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Senior Member

Senior Member

Member

Senior Recognized Developer / Contributor

Senior Member

Senior Recognized Developer / Contributor

Senior Member

Member

Member

Similar threads

Top Liked Posts