Just out of curiosity, is there ANY difference between the 4 or 5 different posts of the new .627 radio? Each author based them off the same file so the only difference could be what was done once they were pulled from the full OTA? I imagine there isn't but is there?
I downloaded a couple of them when they first came out and one later to see what the difference was because of the md5 concerns. All (of the ones I saw) have the same exact radio images that get flashed. One had an extra file added by the tool that was used to compress it. The others just used different compression tools to zip them.
If you are really concerned about mismatches, you can probably extract the actual .img's out and verify the md5's are all the same which they should be since they all came from the same OTA leak.
Not concerned - just curious
Related
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
api1996 said:
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Using fastboot from the PC, as in
Code:
fastboot flash hboot name-of-hboot-image.nb0
(The phone needs to be in FASTBOOT USB mode (coldstart with Send+End), and an acceptable USB driver needs to be installed on a Windows PC)
The S-OFF bootloader is happy to let you replace itself - it is running in memory when you interact with it, not directly from the NAND flash memory.
You can find the .nb0 files inside any of the HTC leak PB00IMG.ZIP ROMs, or the "rom.zip" files embedded within the RUUs. (Note that the built-in Windows "compressed folder" methods for extracting a zip file will not work with these HTC .zip files because of the way that HTC "signs" these zip files, but the 7zip Utiltity for Windows will work).
The 1.47.0000 S-ON bootloaders are only found in the MR1 and MR2 RUUs; all of the "Leak" PB00IMG.ZIP files from HTC (Leak-V1,-V2, and -V3) contain the 1.49.0000 S-ON bootloader.
[SIZE=+1]Please be aware that flashing the bootloader is the single most dangerous thing you can do to your phone, and that if you flash a corrupted file to the bootloader you will certainly hard-brick the device. You absolutely must VERIFY THE MD5 SIGNATURE of the bootloader .nb0 image file before using it with fastboot! Fastboot provides you absolutely no protection from errors! YOU HAVE BEEN WARNED! You can find checksums listed in this reference post[/SIZE]
For clarity, I will repeat them here:
Code:
RUU___MR1 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
RUU___MR2 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
Leak___V1 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Root_Leak 22d3c7082811170e70f308e3213b5d1f hboot_7501a_1.49.2000_100124.nb0
Leak___V2 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Leak___V3 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
bftb0
PS I could swear I wrote a post essentially identical to this one within the last week
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
api1996 said:
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
Click to expand...
Click to collapse
[ Edit ] Updated - check Consolidated HTC Eris RUU/OTA/ROM URLs for the MR1 or MR2 PB00IMG.ZIP files - if you haven't already done the steps below. cheers! bftb0
I don't have a download link right now. If you want to wait a couple days, maybe I'll have something more convenient. In the meantime, the way to get these files is to run the associated RUU utility - but not all the way through. More on that in a second.
You can get the MR2 (1.17.605.1) RUU utility from this folder at shipped-roms.com - the MR2 link is the RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed_with_driver.exe link.
OK, now how do you "get" the PB00IMG.zip file out of the RUU?
Simple. You run the RUU right up to the point where you would normally be starting the install to the phone - but you don't do that. Leave the RUU running, don't terminate it yet. The point of doing this is so that the RUU unpacks all the temporary files it is going to use - including the "rom.zip" file. It puts all this unpacked junk in two temporary folders underneath your Windows user area, perhaps at
C:\Documents and Settings\<your_windows_user_name_here>\Local Settings\Temp
use your windows search capability to look for a big "rom.zip" file underneath there. (The two top-level folders will have long names that look like Windows registry keys). Note that you may have to diddle with your Windows Explorer folder settings to "Display Hidden Files".
Now copy the "rom.zip" file to some other location on your hard drive, and when the copy is complete, exit the RUU utility. (You can't do this until you have copied the file someplace else first, because all the temporary files get wiped when you exit the RUU).
You can then rename the "rom.zip" file to PB00IMG.ZIP. If I am not mistaken, the MD5 checksum of that particular (1.17.605.1) "rom.zip" file will be 9e9ad31f01bbcb05157443287f4f38dd
bftb0
PS. Note the "_with_driver.exe" part of the RUU file name. All the RUUs attempt to install a USB driver for the Eris on to your PC. Since MR1 and MR2 came out one year ago - a couple months after the consumer release of Windows 7, the drivers might not be the same quality as whatever you have on your machine now (if it in fact installs the driver despite the presence of an existing driver). Just a heads up in case it tries to kang a crappy driver into your Windoze box. You might want to take a restore point just before running the RUU in case you find you need to un-kang the driver from your PC.
Thanks for the download links. I had just extracted the rom.zip and found the bootloader and figgured that I should check the tread one more time. That's when I saw the edit! I guess I just have bad timing . Anyway, I went ahead and extracted the bootloader, here's a download link for the 1.47 S-ON bootloader from the MR2 update for anyone who wants it: http://www.multiupload.com/9300LRSFZP
Thanks
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
bftb0 said:
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
Click to expand...
Click to collapse
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
api1996 said:
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
. I thought I had read that someplace recently! LOL
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
USSENTERNCC1701E said:
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
Click to expand...
Click to collapse
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
No kidding, my first one was amazing, ran stable and cool, no trackball issues. I got some dirt in the speaker, when it blew out completely I just got it replaced. If I'd have know all the issues I'd be having with these refurbs I'd have just bought a bluetooth and called it good.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
Not for a lack of trying, though.
I've been trying to locate some older versions of the PRI but haven't been able to find any. Judging from Haus' radio AND pri update file I'm looking for a rcdata.img file I think but I haven't been able to find any in the 1.13 stock rooteds or on the dev forum. Anyone know where I can find them?
Thanks.
blingeorkl said:
I've been trying to locate some older versions of the PRI but haven't been able to find any. Judging from Haus' radio AND pri update file I'm looking for a rcdata.img file I think but I haven't been able to find any in the 1.13 stock rooteds or on the dev forum. Anyone know where I can find them?
Thanks.
Click to expand...
Click to collapse
The only source we've had for PRI files on both the EVO and seemingly also for the EVO 3D are the RUU files released by a user named Football with a Russian flag in his profile (occasionally maybe one or two official OTA updates on the EVO contained rcdata.img files...).
The RUU files are posted in the development board by Football and also mirrored on http://goo-inside.me/shooter/ruu.
The RUU is released as a .exe file. There is a rom.zip file inside the .exe which contains all the .img files including (if released in that specific RUU) the rcdata.img or nv.img.
Goo-inside.me has already extracted these rom.zip files and posted them renamed as PG86IMG.zip files because the rom.zip has the first 256 bytes of the digital signature required by the bootloader to be loaded directly when renamed to PG86IMG.zip. If you grab these zip files off goo-inside.me and open them up there should be a firmware.zip file which would contain the rcdata.img/nv.img if it was released in that RUU. Otherwise we haven't really been given rcdata.img/nv.img files from any other source on the EVO or EVO 3D yet.
If you want to extract the rom.zip file from inside the .exe yourself from linux - very helpful guide I've used: Extract ROM Image from RUU Windows Exe On Linux
As for the EVO 3D, off the top of my head, I only recall seeing an rcdata.img file distributed with this latest RUU 2.08, but I could be wrong and it is def worth double checking. With the HTC EVO, we didn't receive rcdata.img files very often .. might be the same case with the EVO 3D, only time will tell.
I know that might not be the best news but hopefully the technical information is helpful for now and the future in advising where to look and diff options on how to obtain!
Im also looking for this because ever since i upgraded the PRI on my evo 3d, ive had horrible service no matter what rom or radio i flash. i have an airave in my house and the phone constantly roams, goes on 1x and never passes 1 bar on sprint signal. Missing calls... it really sucks. Its weird because on my evo 4G, i never had a problem no matter what radio/pri/prl combo/setup i had... Wish i could get ahold of that earlier PRI because i had perfect signal and 3G everywhere in my house before this. =\
Okay, so just getting straight to the point, here are my 2 questions:
1. Why dont ROM devs release the MD5 image (The nand image created when you back up your phone) rather than releasing the zip file? Is it because the MD5 is larger, or is it just a preference. My thought process was that if you release the MD5 rather than the ZIP, then you wouldn't have to worry about signing the zip and things like that. Just release and flash, I could be wrong though. Any thoughts?
2. Would it be possible to simply build MIUI or CM7 on top of a Sense build rom? Like have sense as the base of the roms, but (deodex) and add MIUI apps to the rom to give it the MIUI look and feel. Same with CM7. I ask because I know that a lot of roms that aren't sense do not have the 3D capabilities that Sense Roms have (HTC being stingy with the source for 3D, i guess!), and if you did it this way, it would be the best of both worlds. So is it possible?
I was just sitting at work and thinking about these questions, and figured why not come to XDA and get some insight I might have missed.
Thanks,
Ognimnella
ognimnella said:
Okay, so just getting straight to the point, here are my 2 questions:
1. Why dont ROM devs release the MD5 image (The nand image created when you back up your phone) rather than releasing the zip file? Is it because the MD5 is larger, or is it just a preference. My thought process was that if you release the MD5 rather than the ZIP, then you wouldn't have to worry about signing the zip and things like that. Just release and flash, I could be wrong though. Any thoughts?
2. Would it be possible to simply build MIUI or CM7 on top of a Sense build rom? Like have sense as the base of the roms, but (deodex) and add MIUI apps to the rom to give it the MIUI look and feel. Same with CM7. I ask because I know that a lot of roms that aren't sense do not have the 3D capabilities that Sense Roms have (HTC being stingy with the source for 3D, i guess!), and if you did it this way, it would be the best of both worlds. So is it possible?
I was just sitting at work and thinking about these questions, and figured why not come to XDA and get some insight I might have missed.
Thanks,
Ognimnella
Click to expand...
Click to collapse
1) There is no such thing as an "MD5" image. MD5 is a hash value generated by using an algorythm .. I'm sure there are better articles on google explaining md5 and the md5sum value.
We only use the md5sum value in the custom recovery as a way to verify when restoring the image from your /sdcard is still the same as it was when the custom recovery dumped it from the partition in the backup process.
We also use the md5sum value to verify the file downloads correctly. If you check out my stock ROM thread - [ROM] joeykrim-original-1.2.0 Odex *Stock Rooted 2.08.651.2* - you will see I provide the md5sum value under each download link. This allows the user, after they have downloaded the .zip file to make sure their md5sum hash matches mine. If it matches, it was downloaded correctly. If not, there was an error somewhere in the download.
2) Unfortunately it is a bit more complicated then simply overlaying AOSP/CM/MIUI apps on top of the stock Sense ROM. Since none of the HTC Sense ROM is open source, it is near impossible for any developer to compile them from scratch. All changes being made to the stock Sense ROM by Sense ROM developers are through reverse engineering, making changes to the smali code and compiling back.
AOSP/CM/MIUI all claim, and probably most do, compile all their apk and other files straight from the source code giving them full control over all features/functions.
The reverse engineering process is very difficult and sometimes the code can be incomplete making it near impossible or extremely time consuming to create from scratch.
I tried my best to articulate the definitions and major issues correctly. I'm sure if somebody can add more detail or a different aspect they will. Hope that helps!
I'm on stock gingerbread 2.3.4. I plan to use this, to get rid of my stock battery icon
http://forum.xda-developers.com/showthread.php?t=1159848
but i've hesitated because of the AT&T label. And framework-res.apk file sizes seem to be different.(edit: of course i compared mine with the untouched file given)
So as an international user, should I avoid it or is it OK for me to flash it?
And it seems to replace framework-res.apk and SystemUI.apk; what if i do it with root explorer?
Should I be worried about anything? (except file permissions)
I can't advise neither for nor against trying it out, but if you do some framework edits/mods, of course the sizes are going to be different. Framework files are not machine code where you need to deploy tricks such as byte padding in order to preserve the original file size.
ravilov said:
I can't advise neither for nor against trying it out, but if you do some framework edits/mods, of course the sizes are going to be different. Framework files are not machine code where you need to deploy tricks such as byte padding in order to preserve the original file size.
Click to expand...
Click to collapse
My comparison wast between my original files and the original (untouched) backup files given in the same thread; it seems that AT&T framework and european frameworks differ in size.
Oh I see. Well I can see that happening too. There is after all a reason they would release two separate variants of the firmware, right?
ravilov said:
Oh I see. Well I can see that happening too. There is after all a reason they would release two separate variants of the firmware, right?
Click to expand...
Click to collapse
So I think I'd better create my own backup zip
Oh yes, definitely. Always prefer your own backups over anyone else's.
Answer to my own question is: NO. At least the one i used is not internationally compatible. causes bootloop.
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.