Root Most Recent Radio

mjb34500

Newbie
Feb 7, 2011
29
2
16
Hi, new to the forum with a Droid Eris. I just switched up to KaosFroyo v38. I notice all this talk about 'bricking' and radios and such....

I have baseband version 2.42.01.04.27

Is there a more recent version? What will and upgrade, if available, do for my phone? I live out in the sticks a bit, so coverage is minimal. Will an upgrade actually help my service out here?

Appreciate any help y'all can provide!
 
There is a newer baseband for the Hero that works with the Eris, but no guarantees that it will be better.

Here is a link to it on xda; the link is on the first page. You should be careful about flashing radios, but the one here is a .zip file that you flash from Amon's, which will check to see that the .zip is signed. Just be careful to follow those directions if you flash it.
 
Thanks a bunch.....not sure what you mean by 'signed' tho?

Also, the directions say to place it on the 'root' of the sd card.....not exactly sure what that means either lol!
 
it just means place it in the top level. do not put it inside any other folders. the roms you flashed were also placed inthe root of the sd card.

flash the radio in recovery,like you would a rom. except you wont do any wipes,just flash it overtop of the rom youre running.
 
  • Like
Reactions: mjb34500
Thanks a bunch.....not sure what you mean by 'signed' tho?

Also, the directions say to place it on the 'root' of the sd card.....not exactly sure what that means either lol!

mjb34500,

A signed .zip file contains a special directory called META-INF. This META-INF directory contains three files, the MANFIFEST.MF, the CERT.SF, and the CERT.RSA file. The MANIFEST.MF contains a list of the all of the other files in the .zip file along with an SHA1 digest (checksum) of that file. The digest/checksums of the actual files in the .zip file can be compared with the digests contained in the MANIFEST.MF file which will guarantee the file's validity / integrity.

You can (and should) verify that validity / integrity of the radio file by at least validating its published MD5 checksum (F15CF77B1C08CFB1F357E2574F386F5F from the thread linked to by Scott's post above) and/or by doing a jarsigner -verify (which checks the aforementioned SHA1 digests in the MANIFEST.MF file). It just so happens that my (free, in the Market) app, AFV (Android File Verifier) will do both of the above functions.

According to this thread I think I figured out how to get past the bootloader HEHE - Page 3 - xda-developers, the CERT.SF contains SHA1 digests for the contents of the entries in the MANIFEST.MF file (pretty cool...I did not know this and will probably be adding an explicit check in my AFV app to double-check these too). The CERT.RSA is an RSA-encoded certificate, probably for the entire file.

Anyway, back to your last question: the root of your SD card is the top-level directory of the /sdcard--which is to say, not in any subdirectory of the /sdcard folder. If you are copying/moving the file from your PC and you've mounted your phone as "USB Mass Storage" (or similar phrasing), and it shows-up as the "G:" drive for example, then just drag and drop the radio file to the G: drive in Windows Explorer. Be sure to do a "safe eject" after doing this transfer and then, verify the MD5 checksum and the "Verify Jar-type File" function if you are using the AFV app.

Cheers!
 
mjb34500,

A signed .zip file contains a special directory called META-INF. This META-INF directory contains three files, the MANFIFEST.MF, the CERT.SF, and the CERT.RSA file. The MANIFEST.MF contains a list of the all of the other files in the .zip file along with an SHA1 digest (checksum) of that file. The digest/checksums of the actual files in the .zip file can be compared with the digests contained in the MANIFEST.MF file which will guarantee the file's validity / integrity.

You can (and should) verify that validity / integrity of the radio file by at least validating its published MD5 checksum (F15CF77B1C08CFB1F357E2574F386F5F from the thread linked to by Scott's post above) and/or by doing a jarsigner -verify (which checks the aforementioned SHA1 digests in the MANIFEST.MF file). It just so happens that my (free, in the Market) app, AFV (Android File Verifier) will do both of the above functions.

According to this thread I think I figured out how to get past the bootloader HEHE - Page 3 - xda-developers, the CERT.SF contains SHA1 digests for the contents of the entries in the MANIFEST.MF file (pretty cool...I did not know this and will probably be adding an explicit check in my AFV app to double-check these too). The CERT.RSA is an RSA-encoded certificate, probably for the entire file.

Anyway, back to your last question: the root of your SD card is the top-level directory of the /sdcard--which is to say, not in any subdirectory of the /sdcard folder. If you are copying/moving the file from your PC and you've mounted your phone as "USB Mass Storage" (or similar phrasing), and it shows-up as the "G:" drive for example, then just drag and drop the radio file to the G: drive in Windows Explorer. Be sure to do a "safe eject" after doing this transfer and then, verify the MD5 checksum and the "Verify Jar-type File" function if you are using the AFV app.

Cheers!

I just DL'd your app, thanks for the heads up!