DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
new ics leak again 6.7.239
- Thread starter sargentmajord
- Start date
sargentmajord
Silver Member
SamuriHL said:
Md5= 7c53449dff20c6c09639e9c461633981
And there you have it - the same file as found last week, only on a different server.
C'est la vie.
Same useless build we've had for a while now. Let me explain to you 2 things you need to know about that build...
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/targa_vzw/cdma_targa:2.3.4/5.5.1_84_DBN-74-Test/120802:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-16/22:user/release-keys");
assert(apply_patch("MTD:boot:8388608:d8c98f433c0023c7353e794414cf0ece1a84828d:8388608:68412e2f3c965fb3e0c81df33a945f562c13b6eb",
"-", 68412e2f3c965fb3e0c81df33a945f562c13b6eb, 8388608,
d8c98f433c0023c7353e794414cf0ece1a84828d, package_extract_file("patch/boot.img.p")));
That's from "239"....here's 238:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/targa_vzw/cdma_targa:2.3.4/5.5.1_84_DBN-74/12:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-15/21:user/release-keys");
assert(apply_patch("MTD:boot:8388608:1b2caac524ec83e9325391c89d8284c0b91eb588:8388608:7e403368493a2713777d80fb85816af8d474a2ca",
"-", 7e403368493a2713777d80fb85816af8d474a2ca, 8388608,
1b2caac524ec83e9325391c89d8284c0b91eb588, package_extract_file("patch/boot.img.p")));
The stuff I highlighted in the apply_path line is the sha1 of the boot.img that they're patching. 238 is the sha1 from 905 FXZ. The 239 one....um, chirp chirp....who the hell knows?
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/targa_vzw/cdma_targa:2.3.4/5.5.1_84_DBN-74-Test/120802:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-16/22:user/release-keys");
assert(apply_patch("MTD:boot:8388608:d8c98f433c0023c7353e794414cf0ece1a84828d:8388608:68412e2f3c965fb3e0c81df33a945f562c13b6eb",
"-", 68412e2f3c965fb3e0c81df33a945f562c13b6eb, 8388608,
d8c98f433c0023c7353e794414cf0ece1a84828d, package_extract_file("patch/boot.img.p")));
That's from "239"....here's 238:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/targa_vzw/cdma_targa:2.3.4/5.5.1_84_DBN-74/12:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-15/21:user/release-keys");
assert(apply_patch("MTD:boot:8388608:1b2caac524ec83e9325391c89d8284c0b91eb588:8388608:7e403368493a2713777d80fb85816af8d474a2ca",
"-", 7e403368493a2713777d80fb85816af8d474a2ca, 8388608,
1b2caac524ec83e9325391c89d8284c0b91eb588, package_extract_file("patch/boot.img.p")));
The stuff I highlighted in the apply_path line is the sha1 of the boot.img that they're patching. 238 is the sha1 from 905 FXZ. The 239 one....um, chirp chirp....who the hell knows?
sargentmajord
Silver Member
SamuriHL said:
Got the same error on .239 an as for the boot img they are updating it to make a dedicated fxz for it meaning GB is no longer an option until I can work my magic
HUH? I don't know what you're saying. 239 is a useless build not meant for release phones. 235+ have new security that disallow fxz'ing back to 905. That's it so far.
sargentmajord
Silver Member
SamuriHL said:
Correct it is a useless build but its kinda like how the .893-5.8.894 updates were all had the same security as the .886 but different boot img files so no one could roll back with out the .893 fxz with the proper boot img file
Ah, I get what you're saying now. That's not what I was pointing out though. The point about the sha1 one was to show that the update script is not looking for a release 905 install. The boot.img that they boot.img.p is written for in that 239 update is something COMPLETELY different. Some test version of 905 perhaps.
sargentmajord
Silver Member
SamuriHL said:
Gotcha I swear to god if they send out another GB update before ICS I am going to flip
If they do, a *LOT* of us will be screwed. BADLY.
sargentmajord
Silver Member
SamuriHL said:
Lmao I am still kicking it on 232 xD
sargentmajord
Silver Member
SamuriHL said:I wasn't planning on keeping the bionic anyway, so I didn't care. 238 is very stable for me so meh. Whatever.
RAZR HD here I come xD