Can someone post a copy of this file please. You can find it in the system folder.
It has to come from a T-Mo US Defy with 3.6.360 firmware...
Thanks!
It has to come from a T-Mo US Defy with 3.6.360 firmware...
Thanks!
if you want to use the official 34.4.9 update, then replacing the file won't do you any good at all.
Yes build.prop might get you through the first check and you can fake it, you can't possibly fake the other hundreds of md5 check bebore the actual update part, can you?
Well, I used a much much more complicated method, and succeeded.Yes, actually, that's the plan.
Have you tried it?
I'm on the leaked T-Mo US FroYo so I don't think there should be a lot of problems.
Besides, no one has posted a Nandroid, so I'm inclined to at least try this route...
Well, I used a much much more complicated method, and succeeded.
Unfortunately I forgot to do a nandroid backup before going back to uk release.
I can tell you how, but Iwon't jump through hoops to do it again.
1. download the original t-mo backup (6.19.0, it's here somewhere), the 6.36update(Blur_Version.3.6.190.MB525.T-Mobile.en.US.zip) and 3.4.2update
2. edit the updater-script inside both zip to remove any possible checking lines
3. do the updates via CWM, nandroid restore->6.36 update->3.4.2 update, in that order and in one session.
not all of them, just the ones withOkay, so you want me to restore a 3.6.190 nandroid, update to 3.6.360, and then update to 34.4.9 all in one go?
But before that, I have to remove all "assert" lines from the updater script?
Is that correct?
not all of them, just the ones with
ro.build&md5 check
and those lines applying xxxx.p to either kernel or recovery