New version of JB 4.1.1 from Lenovo?

[mcl630]

Ok making the changes on build.prop stops the update notice.

ro.build.display.id=JRO03R.A2109A_A411_03_13_121126
ro.build.version.incremental=A2109A_A411_03_13_121126

So if you want to use custom rom replace

ro.build.display.id=JRO03R.A2109A_03_13_121126_MCL0201
ro.build.version.incremental=MCL0201

with

ro.build.display.id=JRO03R.A2109A_A411_03_13_121126
ro.build.version.incremental=A2109A_A411_03_13_121126

then use adb

adb shell

rm -r /cache/*
rm -r /data/dalvik-cache/*
reboot

on reboot check for updates says system is currently up to date.

even though I am still running custom rom, so best if devs don't modify build.prop

I don't recommend doing that (unless you just want to check to see if there are updates). If Lenovo releases a patch-type update (as most of the ICS updates were), it won't apply over a custom ROM.

 

[vampirefo.]

I don't recommend doing that (unless you just want to check to see if there are updates). If Lenovo releases a patch-type update (as most of the ICS updates were), it won't apply over a custom ROM.

Yes this is so one will know if an update exists or not, no a patch can't be added to a custom rom via OTA, A full upgrade would though, this update would remove the custom rom and install the update as it is a full rom not a patch.

 

[FloRider]

Don't use the OTA updates when running my MCL roms, the version numbers confuse Lenovo's OTA server, and patch updates won't apply over MCL anyways.

I always flash.

 

[FloRider]

Where did you get 03_12_121107 ? I've never seen that before. The first (and only) JB version I've seen is 03_13_121126.

That's the ROM I got with wget, thanks to vampirefo. for the link. What I find confusing is the "F" they append.

 

[FloRider]

That's the ROM I got with wget, thanks to vampirefo. for the link. What I find confusing is the "F" they append.

Another confusing issue -- wouldn't the extra bits from the "_F" throw off the MD5 hash?

 

[vampirefo.]

what did the first update display?

 

[FloRider]

That's it. It's still 121126. Since the version is stored in the zip and not as a filename, I would think the MD5 would be different.

 

[FloRider]

That's it. It's still 121126. Since the version is stored in the zip and not as a filename, I would think the MD5 would be different.

Maybe they tweaked some settings and threw that "277" trash in to make the MD5 hashes match.

 

[goldenwing6]

Maybe they tweaked some settings and threw that "277" trash in to make the MD5 hashes match.

File's name and type does not affect MD5,you can rename it to "abcd.xyz" and rehash it again,always the same

 

[FloRider]

File's name and type does not affect MD5,you can rename it to "abcd.xyz" and rehash it again,always the same

I didn't think that was a filename. What do you get with an OTA update? Update.zip? I don't think it's that ID I mentioned.

 

[goldenwing6]

I didn't think that was a filename. What do you get with an OTA update? Update.zip? I don't think it's that ID I mentioned.

My last OTA update got a file named "A2109A_A411_03_13_121126_US.zip",I backup it from "\cache" almost month ago

 

[cordoba]

Were you having reboots or freezes?

Reboots. But the update seems to have done the trick. Haven't had any problems since.

 

[FloRider]

Reboots. But the update seems to have done the trick. Haven't had any problems since.

Well. Same problem I had, and the same result. Maybe we made an error the first time we upgraded to JB.

 

[cordoba]

Well. Same problem I had, and the same result. Maybe we made an error the first time we upgraded to JB.

The interesting thing is that I didn't upgrade to JB. My tablet came with that older version on it! Weird.

 

[Linsalata28]

Is this update newer then mcl's jb ROM? If so is it worth updating? I saw a zip posted, is that rooted or do I need to root and debloat the update? Thanks for any replies.

Sent from my HTC myTouch 4g using Tapatalk 2