can someone who is on 246 please post the ro.build.fingerprint from your build.prop?
ro.build.fingerprint=motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-23/29:user/release-keys
Sent from my DROID BIONIC using Tapatalk 2
6.7.246 To 5.9.905 Downgrade *deprecated*
Started by
mhous33
, Oct 04 2012 05:09 PM
24 replies to this topic
#21
jp1044
-
- News Writer
-
- 1,104 posts
DEVELOPER
- Twitter:@jp1044
- Google+:jp1044@gmail.com
- LocationColorado
- Current Device(s):MOTO X Developer Edition, Droid RAZR HD (backup)
Posted 04 October 2012 - 10:04 PM
ro.build.fingerprint=motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-23/29:user/release-keys
Sent from my DROID BIONIC using Tapatalk 2
#22
mhous33
-
- Developer
-
- 480 posts
Droid Master
Posted 04 October 2012 - 10:18 PM
ro.build.fingerprint=motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-23/29:user/release-keys
Sent from my DROID BIONIC using Tapatalk 2
ok thanks. the fingerprint asserted in the updater script is:
motorola/XT875_verizon/cdma_targa:4.0.4/6.7.2-223_DBN_M4-23/3450134:user/release-keys
so close and yet so far...
#23
rlewis312010
-
- Members
-
- 111 posts
Member
Posted 05 October 2012 - 04:04 AM
I told waco that the install must be 100% stock. Like, rsd 905, or hob 246, and not even start it. Reboot, go into stock recovery and try install. Only way I could ever get those installs to work. It looked to go into process with pic waco posted and stop...but it was not happy at place where "not beingb100% stock" failed for me on any ics leak. Even deleting one bloated app, lmfao. Just saying, unless it is tried with method I mentioned here, it could be the 100% stock bs.
#24
johnlgalt
-
- Superuser
-
- 7,296 posts
Antidisestablishmentarianist
- Twitter:https://twitter.com/JohnLGalt
- Location3rd Rock
- Current Device(s):Pixel 4 XL 128 GB
Posted 05 October 2012 - 08:21 AM
It will not work because the starting SHA-1 hash for every file in the updater-script is an unknown (heretofore) value. It's looking for a very specific build that we do not have.
Also, since we have locked bootloaders, we cannot flash this if we tried. The MD5 and SHA-1 of the CDT.bin matches that in the 5.9.90x FXZ files. Once you are on 6.7.235+ the security in CDT.bin changes from 3 to 4. The one in this "downdate" also had security 3 (obviously, since it is the same identical file as in the FXZs), so we cannot flash this unless we have an unlocked bootloader. My trials with the 6.7.235 update proved that.
It will not matter what you do.
Sent from my rooted BIONIC running ICS 6.7.246 via Tapatalk 2
Also, since we have locked bootloaders, we cannot flash this if we tried. The MD5 and SHA-1 of the CDT.bin matches that in the 5.9.90x FXZ files. Once you are on 6.7.235+ the security in CDT.bin changes from 3 to 4. The one in this "downdate" also had security 3 (obviously, since it is the same identical file as in the FXZs), so we cannot flash this unless we have an unlocked bootloader. My trials with the 6.7.235 update proved that.
It will not matter what you do.
Sent from my rooted BIONIC running ICS 6.7.246 via Tapatalk 2
#25
rlewis312010
-
- Members
-
- 111 posts
Member
Posted 05 October 2012 - 10:29 AM
Thanks John.It will not work because the starting SHA-1 hash for every file in the updater-script is an unknown (heretofore) value. It's looking for a very specific build that we do not have.
Also, since we have locked bootloaders, we cannot flash this if we tried. The MD5 and SHA-1 of the CDT.bin matches that in the 5.9.90x FXZ files. Once you are on 6.7.235+ the security in CDT.bin changes from 3 to 4. The one in this "downdate" also had security 3 (obviously, since it is the same identical file as in the FXZs), so we cannot flash this unless we have an unlocked bootloader. My trials with the 6.7.235 update proved that.
It will not matter what you do.
Sent from my rooted BIONIC running ICS 6.7.246 via Tapatalk 2
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
