Related
[SIZE=-2][ I realize this post doesn't belong here - shout me down after you've read the post ][/SIZE]
[gratuitous-begging]
Hi folks,
If you are publishing ROMs or other installable .ZIPs please please please (yes, I'm begging now) publish MD5 checksums (or at least an exact byte count) of the files you upload for public consumption in the posts in which they are announced. Both would be even better.
The problem isn't one of authenticity of download files (although it is useful to have that); it's that a tremendous amount of "help me" board traffic gets generated (both here and at AF) by folks complaining that they have a problem installing a ROM, when the real trouble they are having is corrupted files. I would be willing to bet that more than 90% of this traffic is caused by people attempting to flash truncated or otherwise corrupted files.
Yes, I know - if they would just pay attention to the fact that "E:" means ERROR in Amon_RA output, we would all be better off. That's hoping for a lot from newbs, though.
But honestly, if you don't publish a byte count or a checksum, those folks can't really check their downloads, even when they do know better. ( Some of the download sites report the download size, but usually only to 3 or 4 significant figures, and with no clear indication of whether MB means 10^6 or 1024^2. )
Many of the devs don't spend much time in the XDA Q&A or General sub-forums, and possibly never on AF, so they don't see this going on; that is to be expected and OK, too, because they are busy building ROMs and other goodies.
But, you can help the folks that are helping other folks get rooted in order to enjoy your work product if we can encourage a culture where people routinely check their downloads - using their phone! - to make sure that your good stuff has arrived safely on their SD cards.
With the help of jcase and Eclips3, user "scary alien" from AF put together a free app for computing MD5 or SHA1 checksums on the phone. There are lots of other ways to skin that cat, too; but the place to start encouraging a culture of having people check their downloads is with the devs - at their announcement posts.
Thanks for your time and consideration.
[/gratuitous-begging]
bftb0
good idea. would help those who have corrupted downloads.
bftb0,
Wonderful thread / post. Thank you very much--this is much appreciated.
By the way, I am working on trying to make the MD5 sum app a little more user-friendly by making the file selectable instead of having to type in the filename (I'm still learning about Android app development......thanks again to jcase and eclips3 for getting me started). I'll try to re-post here when (if?) I ever get this enhancement made.
We all very much appreciate all of the hard work and fruits of labor that you developers produce. Thank you!
scary alien said:
bftb0,
Wonderful thread / post. Thank you very much--this is much appreciated.
By the way, I am working on trying to make the MD5 sum app a little more user-friendly by making the file selectable instead of having to type in the filename (I'm still learning about Android app development......thanks again to jcase and eclips3 for getting me started). I'll try to re-post here when (if?) I ever get this enhancement made.
We all very much appreciate all of the hard work and fruits of labor that you developers produce. Thank you!
Click to expand...
Click to collapse
You might consider putting the byte count in the result display along with the checksum; if you get those two mods put together, you should make an XDA-wide announcement as something this generic is useful to all XDA (Android) users. Take it one step further - and add a "ROM verify (only)" function, and everyone at XDA will know your (screen) name.
Jp50 -
Check out this tangentially related thread. I wonder if your problem the other day with Nonsensikal was due to a similar problem - corruption of the ROM not on the SD, but in system flash (NAND).
One more tidbit, I suppose I should come clean about, it seems about time.
bftb0 == erisuser1 (on AF)
That should explain my motivation for begging this way. Just a historical accident that it worked out that way - i tried not to let the two become cross-forum sockpuppets, but sometimes that was inevitable
bftb0/eu1
Sheer elegance... I should have known it was you eu1!
Great post.
bftb0 said:
You might consider putting the byte count in the result display along with the checksum; if you get those two mods put together, you should make an XDA-wide announcement as something this generic is useful to all XDA (Android) users. Take it one step further - and add a "ROM verify (only)" function, and everyone at XDA will know your (screen) name.
Click to expand...
Click to collapse
eu1/bftb0, lol! I am floored! But not too shocked...how do you find the time?
The byte-count (shown as "File Size:") is already present...I actually created this app in no small part of your exhortations for checking MD5s over at AF -- I knew better than to not include something so vital per your tutelage.
Also, for those that don't know, you can also check your MD5 checksums via Astro File Manager (long-press a filename and select Details). There is also a free app in the Market, ManD5 that will also compute MD5 sums (it did not work (at least for me) when I first wrote my little app, but it does now). And, of course, in some ROMs, the busybox/md5sum program is often available.
However, mine will also calculate SHA1 checksums (which do take much longer to calculate and are more compute-intensive).
Cheers everyone!
This should get stickied or something. We should also get in the habit of asking devs for MD5s if they don't provide them initially. I think you're right; a massive amount of traffic (and headaches!) could be spared if we would do this.
I will provide md5's for future releases I have no problem with posting them but I think the expectation that this will somehow reduce the number of newbie questions/issues is unrealistic. The fact of the matter is that people just don't take the time to read/understand what it is that they are doing. I appreciate the effort here but I just don't see it making a difference. You love my rants don't you? lol
We'll see
Sent from my nonsensikal froyo
listyb01 said:
I will provide md5's for future releases I have no problem with posting them but I think the expectation that this will somehow reduce the number of newbie questions/issues is unrealistic. The fact of the matter is that people just don't take the time to read/understand what it is that they are doing. I appreciate the effort here but I just don't see it making a difference. You love my rants don't you? lol
We'll see
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
yeah i agree here....even though grdlock site where i upload my roms automatically displays the md5sum i just doubt that people who won't even use the search function will bother to check the md5
listyb01 said:
The fact of the matter is that people just don't take the time to read/understand what it is that they are doing. I appreciate the effort here but I just don't see it making a difference.
Click to expand...
Click to collapse
That's probably correct, but you will be reducing the effort of the folks that are trying to help the newbs out, and know better.
Right now what they have to do - in addition to instructing the newb where to get an app that will report file size or md5sum for a ROM file is to: download the ROM themselves, run it through "jarsigner --verify" to see if their own download is OK (signing check), and then compute the MD5 and report that back to the newb. It would be a lot easier to just say:
"Use Astro to compare the MD5 signature of the file on your SD card to what the dev published".
In addition, it helps a little bit with the authenticity problem, too - if someone finds a file on a mirror someplace, they can go back and check the dev's post to gain some confidence what they found is actually "the real deal". Right now that's an impossibility with some dev ROMs.
cheers,
bftb0
bftb0 said:
That's probably correct, but you will be reducing the effort of the folks that are trying to help the newbs out, and know better.
Right now what they have to do - in addition to instructing the newb where to get an app that will report file size or md5sum for a ROM file is to: download the ROM themselves, run it through "jarsigner --verify" to see if their own download is OK (signing check), and then compute the MD5 and report that back to the newb. It would be a lot easier to just say:
"Use Astro to compare the MD5 signature of the file on your SD card to what the dev published".
In addition, it helps a little bit with the authenticity problem, too - if someone finds a file on a mirror someplace, they can go back and check the dev's post to gain some confidence what they found is actually "the real deal". Right now that's an impossibility with some dev ROMs.
cheers,
bftb0
Click to expand...
Click to collapse
I see the value here.
Man I need to get out more, didn't really realize that this was such a hot topic Now back to building v5.3 with md5
Sent from my nonsensikal froyo
listyb01 said:
I see the value here.
Man I need to get out more, didn't really realize that this was such a hot topic Now back to building v5.3 with md5
Click to expand...
Click to collapse
\m/
It's probably just a hot topic to me. You wouldn't believe how hard it is sometime to extract diagnostic information from a newb
:|
bftb0 said:
\m/
It's probably just a hot topic to me. You wouldn't believe how hard it is sometime to extract diagnostic information from a newb
:|
Click to expand...
Click to collapse
...but you're good at it.
As a semi-noob - perhaps the noobs would get more benefit if there were some instructions on what to do with the md5 on the rom page. The developer could use the instructions of his choice and the noob would follow them blindly as long as they're detailed enough. It could be a little tack on at the end of the disclaimer (or wherever they wana put it).
Sent from my Froyo Eris using XDA App
bftb0 said:
...Take it one step further - and add a "ROM verify (only)" function...
Click to expand...
Click to collapse
You mean something like recognizing when a ROM (.zip) name is entered or selected and calculating its MD5 sum and file size against a known, published value?
This would be pretty straightforward (I think...). I could initially just keep an internal table of the ROM names/size/MD5 sums and later, try to acquire this info dynamically from some public source...
Am I in the ballpark here?
Thanks!
edit: would the "jarsigner --verify" method be available to me in my app? (or is that what you had in mind all along?)
scary alien said:
edit: would the "jarsigner --verify" method be available to me in my app? (or is that what you had in mind all along?)
Click to expand...
Click to collapse
Exactly that functionality (but obviously not any Sun/Oracle code). What I don't know off the top of my head is whether or not the Google API provides sufficient functionality to implement it without resorting to a native method. That would make it more portable to other devices (if it is possible).
The native code for doing all the un-.zipping, and signing checks is in the AOSP sources (and elsewhere, e.g. CyanogenMod, Clockwork) available through github etc. From there it is only a "simple matter of programming"
bftb0
Okay, I think I'm fairly close...would you consider the verifying the SHA1 digests from the META-INF/MANIFEST.MF file against each file in the .jar/.zip as "verification"?
I'm a little shaky on the certificates and such, but I think I can do the validation of each file listed in the MANIFEST.MF file. There is the matter of the CERT.SF file whose checksums I can't (yet ) match-up with anything...
Thoughts?
scary alien said:
Okay, I think I'm fairly close...would you consider the verifying the SHA1 digests from the META-INF/MANIFEST.MF file against each file in the .jar/.zip as "verification"?
Click to expand...
Click to collapse
Okay, yeah, its probably silly to quote yourself p), but I've got Java code that works. It reads a .jar file, inspects the MANIFEST.MF file, and calculates the SHA1 digest for each file listed in the manifest. Still gotta incorporate it into my app, but should be pretty straight-forward to do...(oh, and convert the hex SHA1 sums into base64, but my app is already coded to do that).
Stay tuned...(hopefully by tomorrow night)
Here's a test run of my code against Zanfur's overclock patch jar file and the fciv-generated SHA1 digests for the extracted directory:
Code:
d:\temp >[COLOR="blue"][B]java JarVerify kernel-overclock-update-v3.zip[/B][/COLOR]
jar file = d:\temp\kernel-overclock-update-v3.zip
File: [B]boot.img [/B][SHA1 base64 checksum: t4mIp5wAG9kIwTVE+I07BUBFtDE=]
SHA1 (hex) checksum: [COLOR="Red"]b78988a79c001bd908c13544f88d3b054045b431[/COLOR]
SHA1 (base64) checksum: t4mIp5wAG9kIwTVE+I07BUBFtDE= (from MANIFEST.MF)
File: META-INF/com/google/android/[B]update-script [/B][SHA1 base64 checksum: nyfFfx8UMymvIfBVT/6M6stjyjs=]
SHA1 (hex) checksum: [COLOR="red"]9f27c57f1f143329af21f0554ffe8ceacb63ca3b[/COLOR]
SHA1 (base64) checksum: nyfFfx8UMymvIfBVT/6M6stjyjs= (from MANIFEST.MF)
File: system/lib/modules/[B]wlan.ko [/B][SHA1 base64 checksum: WwY9Y+I3ziLsQMDfr6S3wmGn2bs=]
SHA1 (hex) checksum: [COLOR="red"]5b063d63e237ce22ec40c0dfafa4b7c261a7d9bb[/COLOR]
SHA1 (base64) checksum: WwY9Y+I3ziLsQMDfr6S3wmGn2bs= (from MANIFEST.MF)
d:\temp>[COLOR="Blue"][B]fciv -r -sha1 "d:\temp\kernel-overclock-update-v3"[/B][/COLOR]//
// File Checksum Integrity Verifier version 2.05.
//
Start Time: 09/08/2010 at 23h54'34''
[COLOR="red"]b78988a79c001bd908c13544f88d3b054045b431 [/COLOR]d:\temp\kernel-overclock-update-v3\[B]boot.img[/B]
1a93b9f8dc0e3a7db4d62e1c28e34e377ab59a53 d:\temp\kernel-overclock-update-v3\META-INF\CERT.RSA
9d109bf59721f29b2e6ed90780e1e98e5aa6bf1a d:\temp\kernel-overclock-update-v3\META-INF\CERT.SF
[COLOR="red"]9f27c57f1f143329af21f0554ffe8ceacb63ca3b [/COLOR]d:\temp\kernel-overclock-update-v3\META-INF\com\google\android\[B]update-script[/B]
0e6fdf73ab53327c944a9430b090e388f76b60a1 d:\temp\kernel-overclock-update-v3\META-INF\MANIFEST.MF
[COLOR="red"]5b063d63e237ce22ec40c0dfafa4b7c261a7d9bb [/COLOR]d:\temp\kernel-overclock-update-v3\system\lib\modules\[B]wlan.ko[/B]
End Time..: 09/08/2010 at 23h54'34''
Processed 8 directories
Processed 6 files
Errors have been reported to fciv.err
d:\temp>
Its coming!!! (probably not tonight, though )....I've got my MD5sum app coded with the ability to verify all of the SHA1 checksums in a jar file's MANIFEST.MF.
I've gotta cleanup some code and make the interface invoke the jar verification as a separate option from the ones currently available.
Interesting things I've found while testing and doing some research:
1. There are usually two phases to a "jarsigner.exe -verify". Certificate verification and MANIFEST file checksum verification. It appears that -verify does not cause/force certificate validation. The second phase is pretty much does what my app does/will do: scan through the manifest and validate the manifest's entry's SHA1 digests. My app will initially not check certificates--just the individual manifest's digest verification.
2. The Eris 2.1 leaks ROMs (base root and the three non-root leaks) are not jars per se: they do not contain a META-INF directory and therefore there is no MANIFEST.MF to scan. Only a filesize and checksum verification is apparently needed or used on these PB00IMG.zip files.
3. I successfully verified Ivan's 1.0 ROM (100MB) on my Droid X...it took around 3 minutes (will obviously take longer on the Eris...).
Here's a ddms trace of my app scanning the same kernal-overclock-update-v3.zip (renamed to koc.zip to make typing it in easier/quicker):
Code:
09-09 23:31:35.302: INFO/MD5sum(5191): jar file = /sdcard/download/koc.zip
09-09 23:31:35.302: INFO/MD5sum(5191): File: system/lib/modules/wlan.ko [base64 SHA1: WwY9Y+I3ziLsQMDfr6S3wmGn2bs=]...verifying checksum...
09-09 23:31:36.029: INFO/MD5sum(5191): SHA1 (hex) checksum: 5b063d63e237ce22ec40c0dfafa4b7c261a7d9bb
09-09 23:31:36.029: INFO/MD5sum(5191): SHA1 (base64) checksum: WwY9Y+I3ziLsQMDfr6S3wmGn2bs= (from MANIFEST.MF)
09-09 23:31:36.029: INFO/MD5sum(5191): SHA1 (base64) checksum: WwY9Y+I3ziLsQMDfr6S3wmGn2bs= (calculated)
09-09 23:31:36.037: INFO/MD5sum(5191): SHA1 checksum matches MANIFEST.MF (w00t)
09-09 23:31:36.037: INFO/MD5sum(5191): File: boot.img [base64 SHA1: t4mIp5wAG9kIwTVE+I07BUBFtDE=]...verifying checksum...
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (hex) checksum: b78988a79c001bd908c13544f88d3b054045b431
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (base64) checksum: t4mIp5wAG9kIwTVE+I07BUBFtDE= (from MANIFEST.MF)
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (base64) checksum: t4mIp5wAG9kIwTVE+I07BUBFtDE= (calculated)
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 checksum matches MANIFEST.MF (w00t)
09-09 23:31:38.091: INFO/MD5sum(5191): File: META-INF/com/google/android/update-script [base64 SHA1: nyfFfx8UMymvIfBVT/6M6stjyjs=]...verifying checksum...
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (hex) checksum: 9f27c57f1f143329af21f0554ffe8ceacb63ca3b
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (base64) checksum: nyfFfx8UMymvIfBVT/6M6stjyjs= (from MANIFEST.MF)
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 (base64) checksum: nyfFfx8UMymvIfBVT/6M6stjyjs= (calculated)
09-09 23:31:38.091: INFO/MD5sum(5191): SHA1 checksum matches MANIFEST.MF (w00t)
Cheers!
Ill publish these and make a sticky about it with detailed instructions on how's to check an MD5. If someone could PM me the list that would be a big help.
Cheers!
Ck
Sent from my Droid using XDA App
Captainkrtek said:
Ill publish these and make a sticky about it with detailed instructions on how's to check an MD5. If someone could PM me the list that would be a big help.
Cheers!
Ck
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Captainkrtek,
bftb0 / eu1 included a link to a thread I created on AF (http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html) in the OP (http://forum.xda-developers.com/showpost.php?p=7919706&postcount=1) that details various ways to check a file's MD5s checksums. Version 1.0 of my app simply calculated MD5 or SHA1 checksums against a specified file. There are several easy ways to get MD5s on the phone itself, as I detailed in the thread on AF.
Via bftb0/eu1's idea/suggestion, I'm very close to releasing an update to the app (v2.0) I wrote that will essentially do a 'jarsigner -verify' function against a jar (custom ROM)--at least the verification of the SHA1 digests of the files listed in the jar's manifest. This should take the guesswork out of knowing whether or not a user has successfully downloaded a complete/uncorrupted custom ROM (or otherwise signed jar file).
Last weekend, I posted a thread (http://androidforums.com/eris-all-things-root/168942-phone-rom-checksum-verifier.html) re. v1.1 of my app that was basically a brute-force approach to ROM verification. I created a table that the app loaded and compared against the checksum of the specified file to check its validity.
Anyway, I'm hunkering-down this evening trying to finish what my last two posts have detailed re. the v2.0 version of my app. My biggest hurdle is my unfamiliarity with Android development ))...I want to make it more user-friendly by not requring that the filename be inputed by hand, but instead allowing a file to be selected. I got just a little bit more testing and verification to do.
I'll be soliciting feedback and folks to test the app out and let me know what they think.
Thanks and cheers!
Hey,
By hoping you'll find this thread useful, here you can find all the available HTC Desire HD Radios:
____________________________________________________________________________
Xeleth is now maintaining and updating the thread with the latest releases
Please refer to the second post to check out all the latest files
...or keep reading for the Radio archive
____________________________________________________________________________
DISCLAIMER
Flashing radio is A VERY RISKY OPERATION and may brick your device if something goes wrong; you may also not be able to flash a previous version if the newer one isn't performing well.
S-OFF bootloader is required to successfully flash any radio. The stock bootloader doesn't support fastboot commands.
Radio S-OFF is highly reccomended, expecially if you're willing to try the latest radio files (> 26.04.02.17). By being Radio S-OFF you'll have the chance to restore previous ROMs and Radio files.
HOW TO READ THE RADIO NAMING SCHEME
i.e. Radio_12.28b.60.140e_26.03.02.26_M
|_______|__PROTOCOL__|__RADIO V.__|
HOW TO FLASH - Quick Start Guide - The Google Way (for CM or AOSP ROMs)
- Make sure you have downloaded the Android SDK, your device is plugged in, fully charged and the ADB Drivers are correctly installed on your PC.
- Extract the radio.img file to the /tools folder of your Android SDK (or /platform-sdk if you have downloaded the Gingerbread SDK).
- Reboot your device into bootloader mode.
- Launch the command prompt and browse to the /tools folder of the Android SDK (or /platform-sdk if you have downloaded the Gingerbread SDK).
- Type (without quotes) "fastboot flash radio radio.img".
- Wait until the send and write operations are completed (this may take a few minutes).
- Reboot your device.
HOW TO FLASH - Quick Start Guide - The HTC Way (for Stock ROMs)
- Make sure you have downloaded the HTC Fastboot Package, your device is plugged in, fully charged and the HTC Sync USB Drivers are correctly installed on your PC.
- Extract the radio.img file to the folder containing the fastboot executable the file AdbWinApi.dll may be also required and placed in this folder.
- Reboot your device into bootloader mode.
- Open the command prompt and browse to the fastboot folder.
- Type (without quotes) "fastboot flash radio radio.img".
- Wait until the send and write operations are completed (this may take a few minutes).
- Reboot your device.
HOW TO FLASH - Quick Start Guide - Quick Flash Packages for Windows
- Please refer to the next post for further informations about Quick Flash Packages
HOW TO FLASH - Detailed infos
For more informations and troubleshooting, please check these threads:
How to flash a radio.IMG - tried and tested by leith51
Ivo's Introductory Guide to this forum by ivolol
[FILES]
Release
October 2010: Radio_12.28b.60.140e_26.03.02.26_M - HTC WWE 1.32.405.6
Radio.img MD5 Checksum: 989501d06389d212143b491c14724c05
17th December 2010: Radio_12.28e.60.140f_26.04.02.17_M2 - Orange ES 1.75.75.2 / HTC WWE 1.72.405.3
Radio.img MD5 Checksum: d3809958c8fad8211d20f97eeede2a1a
21st December 2010: Radio_12.35a.60.140f_26.04.03.30_M - HTC CHN 1.75.1400.4
Radio.img MD5 Checksum: ce2d2c8d4fefc082874c954646fa7363
4th January 2011: Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2
Note: Once flashed, this radio will show up as 12.28e.60.140fP_26.04.02.17_M2 or 12.28e.60.140fU_26.04.02.17_M2
Radio.img MD5 Checksum: aea59efafc7327000a44ee902046c355
17th January 2011: Radio_12.39.60.19_26.06.04.06_M - Cingular US 1.80.502.3
Radio.img MD5 Checksum: 99f4994c7b8b193336cad0dc5ffd19b4
28th January 2011: Radio_12.35d.60.140f_26.06.03.24_M2 - TELUS WWE 1.84.661.1
Radio.img MD5 Checksum: edc9b36f3e30b8a3aec0f8e5ebfe9484
25th February 2011: Radio_12.28g.60.140f_26.05.05.27_M3 - Orange UK 1.84.61.2 / CSL-HK CHT 1.84.832.2
Radio.img MD5 Checksum: 8c252e3ac1358e974863789c749ac4f9
[*] 28th April 2011: Radio_12.54.60.25_26.09.04.11_M2 - HTC Ace Gingerbread S 2.36.405.5
Radio.img MD5 Checksum: 2dc4cfc01516d71c8d68ac2c5e2feda0
23rd June 2011: Radio_12.56.60.25_26.10.04.03_M - Telus DHD 2.43.661.1
Radio.img MD5 Checksum: 774b9ddeef6ce76dd8191b6ca2397cda
21st July 2011: Radio_12.59.60.26_26.11.04.21_M - HTC Ace Gingerbread S KT-KR 2.52.1010.2
Radio.img MD5 Checksum: c39bcfcd8e2c46502bdd02cca6d914ff
6th September 2011: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1 WWE
Radio.img MD5 Checksum: 3ca0e9784c6fd610c0d95391f2bc9245
1st December 2011: 12.65.60.29_26.14.04.28_M - HTC 3.12.405.1 WWE
Radio.img MD5 Checksum: e186ba030925e836898b86d4369e77a3
June 2012:
12.68.60.29U_26.16.04.09 - Unknown source
Radio.img MD5 Checksum: 960f4cb8e849a7423ee656619579b4aa
Test
20th November 2010: Radio_12.32.60.140e_26.04.00.05_M - HTC CHS 1.60.1400.7
Radio.img MD5 Checksum: 25ae4bae9f011fa53d3d3fa73c80c24d
23rd December 2010: Radio_12.28g.60.140f_26.05.02.15_M_test - UK 1.75.771.2
Radio.img MD5 Checksum: 17d809807ff54ac99dc54640c139dafa
07th March 2011:Radio_12.41.60.19_26.06.04.14_M_Test - HTC Ace Gingerbread S Generic 2.16.0.0
Radio.img MD5 Checksum: 71ba0afe14b1caf5ba29da6f3e2ab755
17th March 2011:Radio_12.35d.60.140fU_26.08.03.07_M_Test - HTC Ace Gingerbread S Generic 2.25.0.0
Note: Once flashed, this radio will show up as 12.35d.60.140fP_26.08.03.07_M or 12.35d.60.140fU_26.08.03.07_M
Radio.img MD5 Checksum: b19c70e7d346c9f76ac31e1964fa4238
04th April 2011: Radio_12.48.60.23U_26.08.04.07_M3 - Unknown source
Warning: this radio has been reported to be working but we still don't know the source ROM. So be careful before flashing.
Radio.img MD5 Checksum: a7fc088a0d12f6b4f5eda5322882091e
[*]: Recommended download
[**]: Still untested, be careful before flashing
[MIRRORS]
- MIRROR 1 - Courtesy of burnout11
[CREDITS]
- Thanks to brolee83 for posting the 26.04.02.17_M2_SF Radio
- Thanks to Rey-619 for posting an alternate link for the 26.06.04.06 Radio
- Thanks to limestar for posting the 26.05.02.15 Test Radio
- Thanks to kumar.anirudha for posting the HTC Ace Gingerbread S Generic 2.25.0.0 Test Radio
- Thanks to rock_shen for posting the 26.08.04.07 Radio
- Thanks to n9ntje for posting the 26.09.04.11 Test Radio on this thread, credits also to 911sniper and to Fightspit
- Thanks to shaboobla and Bla1ze for posting the 23.10.04.03 Radio
- Thanks to mike1986. for posting the 26.13.04.19 Radio
- Thanks to mike1986. for posting the 26.14.04.28 radio and to soleil10 and sigurd_LU for providing infos about this new release
- Thanks to preacher65 for sending me the 26.08.04.07 Radio which was missing from my HDD and was unavailable since MultiUpload was shut down
- Thanks to devil-kin for pointing me the links to the 26.16.04.09 radio
RIL - RADIO INTERFACE LIBRARIES
What is a RIL? Quoted from jkoljo's [RIL] Radio Interface Libraries thread: RIL is a library that acts as a bridge between your device's phone functions and the radio firmware in your device's communications chip (radio). Matching radio and RIL is always a good combination when you think of signal stability and battery consumption. That is why you should flash a matching RIL when you flash a new radio.
Flashing RILs only work for Sense based ROMs and CM7 ROMs > nightly built 57. ATM MIUI doesn't support HTC RILs.
Please refer to the [RIL] Radio Interface Libraries Thread for a comprehensive list of all the RILs released for the Desire HD
QUICK FLASH PACKAGES FOR WINDOWS
Quick Flash Packages are zip packages which will flash the desired radio in a simple and easy way.
QFP are intended for users who have already flashed a radio before and know how to handle the whole procedure and the risks involved.
During the flashing procedure, all the steps are being explained and the user will need to confirm each action.
If you should experience any weird behaviour or should get any error response by your command shell, please close the window and report it to me.
[REQUIREMENTS]
- Your device is turned on and is not in bootloader or recovery mode
- Battery is at least at 50%
- HTC drivers or Google Drivers installed and working
- Your device is recognized under Device Manager;
- USB Debugging Mode is enabled;
- Radio S-OFF has been performed;
- ENG Hboot is installed.
If you're not sure or you do not meet them, please follow the "How to flash a radio.IMG - tried and tested" guide by leith51 and flash the radio by following the steps suggested by that guide.
[HOW TO INSTALL]
Unpack the zip folder to your desktop folder and run the QuickRadioInstall.cmd script which will start the flashing procedure.
Follow the steps shown on screen.
[FIRST RUN]
- QFP will first check if your device is recognized by ADB. This will make sure the drivers are installed and working.
- QFP will then reboot your device into Fastboot/bootloader mode
- QFP will then flash the radio, showing the results
- Once done, QFP will reboot your device
[SOME SCREENSHOTS]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[DOWNLOADS]
- Quick Flash Package: Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2
ZIP FILE MD5 Checksum: 1c9b2d02021995e9269f1e19978e22fd
- Quick Flash Package: Radio_12.39.60.19_26.06.04.06_M - Cingular US 1.80.502.3
ZIP FILE MD5 Checksum: 0ff08e2db8b4c91d68dd8449bbbf148b
- Quick Flash Package: Radio_12.35d.60.140f_26.06.03.24_M2 - TELUS WWE 1.84.661.1
ZIP FILE MD5 Checksum: 9d1cac04bcb4abbc7a8aa6a5b5b9f557
- Quick Flash Package: Radio_12.28g.60.140f_26.05.05.27_M3 - Orange UK 1.84.61.2 / CSL-HK CHT 1.84.832.2
ZIP FILE MD5 Checksum: 27d02c880d41d48083acbd1eddb242e5
- Quick Flash Package: Radio_12.54.60.25_26.09.04.11_M2 - HTC Ace Gingerbread S 2.36.405.5
ZIP FILE MD5 Checksum: b341bcc7f24be533523b337ddd4f6c17
- Quick Flash Package: Radio_12.56.60.25_26.10.04.03_M - Telus DHD 2.43.661.1
ZIP FILE MD5 Checksum: c50d9274cd58778312122ad6ae71ab4a
- Quick Flash Package: Radio_12.59.60.26_26.11.04.21_M - HTC Ace Gingerbread S KT-KR 2.52.1010.2
ZIP FILE MD5 Checksum: 07f5973a99fb9f9f922a09be1535ce5d
- Quick Flash Package: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1 WWE
ZIP FILE MD5 Checksum: 4ce58ebaee18e9b695d733b47c5b5b02
- Quick Flash Package: Radio_12.65.60.29_26.14.04.28_M - HTC 3.12.405.1 WWE
ZIP FILE MD5 Checksum: d6a14d53753224077e3cf5e8b3feaa07
http://xdafil.es/DesireHD/Radios/
what is a radio, whats the difference between this and a ROM for example?
Rittzy said:
what is a radio, whats the difference between this and a ROM for example?
Click to expand...
Click to collapse
Correct me if im wrong anyone...
ROM is the operating system(Android) , its the image that you place on the flash memory that contains the various parts of the OS including the kernel.
RADIO in your phone is another computer in its own right and has its own CPU and RAM controls the phone. Controls Main phone functions a radio is a number of "radios" really GSM- Phone, GPS, Bluetooth, WIFI, its seperate because you cant have a rogue application effecting the performance of the phone. you cant have some live wallpaper causeing the phone to drop out because it is hogging CPU cycles!
& then the Kernel is the core piece of code that boots on the hardware and then loads everything else, the kernel boots then runs init, which can do several things.
Great thread!
Hello
Its is possible to flash Radio via recovery instaead of ADB? (Like the classic Desire)
What is the best Radio now?
Thanks
Hello... i'd like to know if with this radio there is an increase of signal strenght,because since i bought this phone with h3g operator here in italy signal is a complete disaster,even if i live in a well covered zone.reply soon
madmatteo93 said:
Hello... i'd like to know if with this radio there is an increase of signal strenght,because since i bought this phone with h3g operator here in italy signal is a complete disaster,even if i live in a well covered zone.reply soon
Click to expand...
Click to collapse
I prefer this one: http://xdafil.es/DesireHD/Radios/12.32.60.140e_ 26.04.00.05_M.zip
Dj!pOner said:
Hello
Its is possible to flash Radio via recovery instaead of ADB? (Like the classic Desire)
What is the best Radio now?
Thanks
Click to expand...
Click to collapse
It is posible, I did flashing radio trough recovery on the Normal Desire.
But dunno how to repack to zip to make it flashable for recovery tho!
Thanks for your reply
Waiting for flashable Radio ...
thanks...thank you so much xmoo just some minutes ago i flashed the radio with that version and situation seems a bit improved,but still a disaster
really really thanks
xmoo said:
http://xdafil.es/DesireHD/Radios/
Click to expand...
Click to collapse
are these radios flashable via recovery?
Nope, the .img is in them.
golf60 said:
are these radios flashable via recovery?
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
when i look in the zip of the newest radio it looks like a flashable zip file with meta-inf and system folder... after downloading with opera mini...
looks like the flashable radios for my desire...
golf60 said:
when i look in the zip of the newest radio it looks like a flashable zip file with meta-inf and system folder... after downloading with opera mini...
looks like the flashable radios for my desire...
Click to expand...
Click to collapse
Uhm.. I had to grab them all just to make sure if you where mistaking another one for being the "newest" but no, I couldn't find anything except for the image in any of them.
how can i make the .img file flashable via CWM ? the flashable desire files only named radio.img ? How can i make these .img files flashable via CWM ?
these are the flashable radios for the normal Desire... what is different?
http://forum.xda-developers.com/showthread.php?t=687464
I tried building some flashable zips the same way as the desire ones, they flash in recovery but they do nothing. I have to say though that it takes more work to create a flashable zip file than it takes to safely flash through fastboot.
Sent from my HTC Desire HD using XDA App
xmoo said:
http://xdafil.es/DesireHD/Radios/
Click to expand...
Click to collapse
Hey, thanks for pointing that out. I noticed the "HTC Desire HD Files" thread but I didn't find any mention of Radio files so I thought they were not on the server. But maybe this thread could still be useful as we can have a centralized place where to discuss how different radios work
madmatteo93 said:
Hello... i'd like to know if with this radio there is an increase of signal strenght,because since i bought this phone with h3g operator here in italy signal is a complete disaster,even if i live in a well covered zone.reply soon
Click to expand...
Click to collapse
I'm using 3 IT and I noticed a small improvement in my signal strenght. Don't expect anything huge, tho
golf60 said:
when i look in the zip of the newest radio it looks like a flashable zip file with meta-inf and system folder... after downloading with opera mini...
looks like the flashable radios for my desire...
Click to expand...
Click to collapse
I'm afraid none of the available radios are flashable via Recovery atm
hi,
I'm italian too .... use TIM and now have radio coming with rom Revolution 1.92
maybe your latest test-radio do you think it's better than the one that I used now ?
....
and, if you know, how to find the radio image that I have, if somethings is wrong ?
tks for reply
Alright guys, this script was made by Indirect. It contains a much simpler/less crappy batch script to root your phone without pausing (contains 3 confirmation though just in case) If this file messes up, it isn't my fault as the usual android modification warning applies.
This is the same method as the usual one but just has less than 70 lines of code instead of 138 which is the best way to make it while still having it be noob friendly or just ripping away at the commands where a glitch can happen. Enjoy this guys, just know the person who wrote it worked hard.
Remember, you still need to flash an RUU after this but atleast you can backup with TB before hand!
I MADE THIS THREAD BECAUSE THE FORMER THREAD WAS CLOSED BECAUSE THE MEMBER WAS NO LONGER A PART OF XDA.....WELL I AM so this shouldnt be closed
THIS WAS MADE BY INDIRECT
*
MD5 SUM: 5D93EE36EF9D040A4655D135FD9421D2
Changelog:
v 1.0 Added confirmation question as to whether MD5 hash matches.
v .99 Added MD5 Checker
v.9 Initial release
Code:
CREDITS: Agrabren for the fre3vo exploit
people in the #htc_evo_shift channel for providing entertainment
otaking71 for RUU'ing his phone back to stock to test this.
teamwin for being awesome.
IF YOU NEED HELP USING THE SCRIPT USE THE IRC CHANNEL FOR HELP. Indirect is usually there and other people can help too.
Bump....
I keep getting the adb server is out of date
Power_ said:
I keep getting the adb server is out of date
Click to expand...
Click to collapse
Go to the IRC channel for help
Sent from my Supreme Shift on Wires!
IRC channel?
bump
Sent from my Supreme Shift on Wires!
Thread Closed for this reason:
Found it on your .bat
Code:
echo * signature has been changed sucessfully!
Echo congrats on gaining root access.
echo Be sure to say thanks to OTAking and Scary for finding this out.
[B]echo Screw Evil_devnull, he's an attention whore[/B].
PING 1.1.1.1 -n 1 -w 5000 >NUL
adb shell su
echo if it doesnt say "su not found" then your rooted and this worked
:N1
:N2
Kindle Fire Utility v0.9.5 (3/30/12) pulls in a file called files.log containing
updatemd5|FCF807C71EAB888106DD9C407C2E2DAB
I attempted several times using KFU v0.9.5 (and KFU v0.9.4) to get the update.zip file and failed the md5check test repeatedly.
Since the run.bat routine deletes the update.zip file when md5check fails,
I went outside of KFU to get the update-kindle-6.3_D01E_4019920.bin to see what went wrong.
I got:
E87836AF028338B5BABB468D443A586D update.zip
I deleted the file and did wget again.
I still get this md5 result which does not match the current md5 code from random.kennocha.com/kindle/utility/sync/files.log
Would you please confirm the md5 check code for update-kindle-6.3_D01E_4019920.bin listed in the current files.log?
Thank you very much for your help.
watersnake said:
Kindle Fire Utility v0.9.5 (3/30/12) pulls in a file called files.log containing
updatemd5|FCF807C71EAB888106DD9C407C2E2DAB
I attempted several times using KFU v0.9.5 (and KFU v0.9.4) to get the update.zip file and failed the md5check test repeatedly.
Since the run.bat routine deletes the update.zip file when md5check fails,
I went outside of KFU to get the update-kindle-6.3_D01E_4019920.bin to see what went wrong.
I got:
E87836AF028338B5BABB468D443A586D update.zip
I deleted the file and did wget again.
I still get this md5 result which does not match the current md5 code from random.kennocha.com/kindle/utility/sync/files.log
Would you please confirm the md5 check code for update-kindle-6.3_D01E_4019920.bin listed in the current files.log?
Thank you very much for your help.
Click to expand...
Click to collapse
I don't think kfu has the md5 for 6.3. I think its for 6.2.2
Sent from my myTouch_4G_Slide using XDA
I just rooted my brand new nook color 1.4.1 today and used the latest MiRaGe - KANG build of CyanogenMod Rom. Here are the links to the instructions I followed:
http://forum.xda-developers.com/showthread.php?t=1030227
http://forum.xda-developers.com/showthread.php?t=1344873
As part of the KANG build I decided to try and initialize V6 Supercharge utilizing V6_SuperCharger_for_Android-update8.sh.txt that was provided on this page:
http://forum.xda-developers.com/showthread.php?t=991276
I followed the directions given (used busyboxinstaller 1.18.2) and took the following steps:
- Start Terminal Emulator and do the followings
- su
- cd /sdcard
- sh V6*
However, after I enter sh V6* I see
REMINDER: ONLY USE BUSYBOX v1.18.2 OR LOWER!!
and the cursor moves down to the blank next line. Nothing else happens. I have no idea why this isn't working. At first I was getting an error about the file being read-only, so I downloaded ES File Explorer and made sdcard writeable, but now I have this. Any help would be awesome!!!
Sorry...ignore this post please
rampart51 said:
Sorry...ignore this post please
Click to expand...
Click to collapse
He means ignore his "reply", not my post! Still need any help I can get, thank you!