sargentmajord
Silver Member
Next stop 4000 ^_^
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
By the way Sam, can you explain what "random offset 0x017d" means during the OTA install script? It seems like it's ALWAYS 0x017d, which hardly seems random to me. And WOOT, 2900th post!
Hey samuri i got a tip where to find the official ota build that will be pushed so u can cross reference the hash with the 246 update
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
It would seem that if they changed anything then it would then be .247, two different things with the same version number would be a tech support nightmare.
I want to see PROOF that it happened with .905 - because I am the one who originated the .905 leak, and the file I downloaded matched up with the one I downloaded that was supposedly the official OTA pulled from someone's cache.It happened with 905 it could happen again
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
It happened with 905 it could happen again
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
SamuriHL said:No, it actually didn't. People claimed it did but were refuted when the hash was IDENTICAL. Then they claimed it was STILL different "somehow". They'd be wrong. Nonetheless, I like being thorough.
I want to see PROOF that it happened with .905 - because I am the one who originated the .905 leak, and the file I downloaded matched up with the one I downloaded that was supposedly the official OTA pulled from someone's cache.
I do remember a rumor that the OTA was different, but it turned out that the person with the MD5 mismatch had gotten the file corrupted somehow in the process of copying between the cache folder, the sdcard, and their PC.Could have sworn there was one update that did that
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
Could have sworn there was one update that did that
Sent from my 1.404 ghz 3605 quadrant score ICS .246 DROID BIONIC
I do remember a rumor that the OTA was different, but it turned out that the person with the MD5 mismatch had gotten the file corrupted somehow in the process of copying between the cache folder, the sdcard, and their PC.
I'm pretty sure that cache wipe is triggered by the on-device OTA installation app and only happens if the update is installed via the automatic reboot into recovery. Not being one to leave things to chance, I always catch the reboot and do a manual cache wipe anyways *LOL*The only difference I came up with was the install itself. I've been told that the official update install script wipes the cache and that those who installed it manually may not have done so. See now why I insist people do it with the HoB? As I said, I'm thorough and I leave nothing to chance.
I'm pretty sure that cache wipe is triggered by the on-device OTA installation app and only happens if the update is installed via the automatic reboot into recovery. Not being one to leave things to chance, I always catch the reboot and do a manual cache wipe anyways *LOL*
That was funny when they had the accidental push. Can't help but wonder if that's what happened to that guy over at xda that swears he got .246 OTA as a "developer" seed.Nope. 901 was accidentally pushed by mistake to people but was later replaced by 902. A small patch to update 901 to 902 was pushed to those who had 901. There has never been a leak that was proven to be different than the OTA. Ever.