Firmware v1.02 Available

[roguelj]

My post criticising this has had the desired effect, and indeed I did know that I was in for a load of flak when posting it. But it has resulted in a simple update that reverts the scroll back allowing the official update for those users that wanted to try it, which I beleive was being overlooked in favour of developing the much appreciated custom rom. Users asking for help not in the modding section, but in the offical firmware update thread have now got a fix instead of being brushed aside.

Wow, so that was your idea all along, eh? Instead of suggesting, or asking for this, you thought that writing a post that you knew would generate you a lot of flak was the right way to go about it? You use your command of the English language to piss people off? That's how you get things done?

Wow.

[Pete_S]

I think most jumping on the bashing bandwagon here do not understand what my criticism was, it was in no way anti modding as I have supported the open source community for many years and have been an active contributor in the past, but failing eyesight now prevents me enjoying it so much, and like most on here have in some way opened and modded most of the tech I own. I wasnt cricising developers and the tools they use as that would be like bashing myself, so forgive me but I think those posts suggesting I am knocking this, and imparticular the clockworkmod tool or development in general are just displaying the ignorance of the posters.

What I did criticise was not development, but an attitude displayed by warped flash on this occasion in that when it was established that his edited build prop would prevent the official update from working. There was no help offered to users such as, 'yea my edited build.prop will prevent the official update, but no probs, no one could forsee the pre-requisites of these updates so I am posting a fix that will undo my edits for those that wish to install the new firmware', instead it was incorrectly implied that the new firmware was at fault. Warpedflash will tell you that assert true statements in the update scripts failed because of the edited build.prop. It was never in question (by me) that the official update would not work with clockworkmod installed or on a rooted scroll, as I had examined the update scripts.

My post criticising this has had the desired effect, and indeed I did know that I was in for a load of flak when posting it. But it has resulted in a simple update that reverts the scroll back allowing the official update for those users that wanted to try it, which I beleive was being overlooked in favour of developing the much appreciated custom rom. Users asking for help not in the modding section, but in the offical firmware update thread have now got a fix instead of being brushed aside.

I dont really want this thread turning into a bashing war... thanks fo rsupporting me peoples but it shoul really actually be about the 1.02 update lol...

So yea I updated the how-to files saying not to do them if you want to flash 1.02. Im not going to take them down because I am of the opinion most people are not so retarded as to not ask for help if it goes wrong.

The root should still work on 1.02 and should the new build.prop files I will however revert the device ID changes if its requested so the new update will flash over the top - downside the thing will be name badly in tapatalk again.

Thanks warpedflash, you got there in the end

Sorry to everyone for carrying this on... but, smacks of a politician backsliding after all party criticism.

There are ways of engaging with other people which don't involve getting personal and which usually get the job done far better and to everyones satisfaction.

It's called tact, Sybil. You wouldn't understand

[mojo]

VOTE- for thread to be cleaned up and back on topic...

[Kommander]

Seconded.

[paulieb]

I thought I would have a go at 1.02 anyway as the battery thing is driving me mad. I have the scroll rooted, build prop v3, clockword mod etc etc.

Factory reset went ok, but installing the update gave an assertion failure

"ro.product.device" = "tcc8900" or "ro.build.product" = "tcc8900"

The new build prop did change these so I've put the original build prop back with these original settings in it, but I'm still getting the same error while attempting to apply the update.

Any suggesstions welcome

[Warpedflash]

paulieb restore the stock recovery image as well.
or if you fell up to it you a can remove a couple of line (those 2) from the update-script itself

[Fonefixer]

In my case I diddnt have a copy of the stock recovery image. I think (bear in mind im only a "learner" at android!) that the clockwork mod overwrites the original recovery partition and doesnt save it anywhere. DJ_Steve and Warpedflash helped me out when I had this. I also had to remove the "update-script (note not updater-script) and remove the two lines the above post refers to.

I still have CWM on my device and im happy for it to be there because i can back everything up.

One final note, I saw that if I opened these files in notepad they diddnt display correctly, but in wordpad they did.

HTH

[Detection]

I still can not apply the 1.02 update after removing the 2 lines and script from the update.zip

[Warpedflash]

there is also a date check line if i remember correctly. remove that as well

[Fonefixer]

The lines that I removed are:

assert(!less_than_int(1294299609, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "tcc8900" ||
getprop("ro.build.product") == "tcc8900");

The first line is the date check...