Checksum proof that RUU OTA = 2.1 Leak v3

[tereg]

I have currently been testing the method of rooting leaked 2.1 phones. There was a little discussion running in that thread (and other threads, I've found) that poses the question whether or not the RUU is the same as 2.1 Leak v3.

The RUU I'm using is referenced here: [ROM] Official HTC Desire RUU ROMS and OTA Update URLs - xda-developers -- which can be found here: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe

Leak 2.1 v3 I'm using is referenced here: http://androidforums.com/htc-droid-eris/69688-htc-droid-eris-os-2-1v3-download.html -- which can be found here: PB00IMG.zip

So, the process that I've been using to root these phones involves flashing the RUU OTA onto the phone. With some help from user bftb0, I have taken the time to do the analysis.

How did I get system.img and boot.img off of the RUU OTA, you might ask? Well, after I flashed the RUU OTA onto the phone, I went through the Incredible/Slide root method to root the phone I'm working with (without changing any phone settings within Sense). After getting adb to recognize the device in recovery, I took the steps necessary to flash Amon_RA's recovery. I then took a Nandroid backup of my phone, and extracted the system.img and boot.img files off of the SD card where the Nandroid backup was stored.

Then, I used unyaffs to unpack system.img into 2 separate directories, and used split_bootimg.pl to unpack boot.img

so, for split_bootimg.pl I did this, starting at the directory where each respective boot.img file is

$ mkdir unpak
$ cd unpak
$ split_bootimg.pl ../boot.img 

... [output] ...

$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i

The test after it's unpacked

#!/bin/bash
mydir=`pwd`
for tree in leakv3 RUU ; do
  cd $tree
  touch ./md5sigs
  find . -type f -print | while read fnam ; do md5sum $fnam >> ./md5sigs ; done
  cd $mydir
done
cat leakv3/md5sigs RUU/md5sigs | sort | uniq -u

$ ./md5test.sh
6951ac78e8f9ae5e6c4c4cb50803fed9  ./bin/su
9512ebf90efee5ea996ec59456cf4b03  ./md5sigs
c6212fa45ab99c3a5d731bca06184023  ./md5sigs

This output should be expected; we should expect the su executable to be in one and not the other if I've rooted it, and the md5sigs that the script creates are not going to have the same md5sums

Pastebins for both the leak v3 list of md5sums, and RUU list of md5sums

Leak v3 md5sigs pastebin: 74fcbd4f10fd8fea9ff3b3fe103d07 - Anonymous - PGZDbC1r - Pastebin.com
RUU OTA md5sigs pastebin: 74fcbd4f10fd8fea9ff3b3fe103d07 - Anonymous - qz5z0Vdr - Pastebin.com

Conclusion: They are identical

 

[thenestor]

Fyi, you can also take the rom.zip out of the RUU (it's in your windows temp folder while the RUU is running), and compare its checksum to the leak v3 PB00IMG.zip, and they're identical.

 

[xx_bishop_xx]

Pretty neat stuff....I think.

 

[Jrocker23]

I have currently been testing the method of rooting leaked 2.1 phones. There was a little discussion running in that thread (and other threads, I've found) that poses the question whether or not the RUU is the same as 2.1 Leak v3.

The RUU I'm using is referenced here: [ROM] Official HTC Desire RUU ROMS and OTA Update URLs - xda-developers -- which can be found here: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe

Leak 2.1 v3 I'm using is referenced here: http://androidforums.com/htc-droid-eris/69688-htc-droid-eris-os-2-1v3-download.html -- which can be found here: PB00IMG.zip

So, the process that I've been using to root these phones involves flashing the RUU OTA onto the phone. With some help from user bftb0, I have taken the time to do the analysis.

How did I get system.img and boot.img off of the RUU OTA, you might ask? Well, after I flashed the RUU OTA onto the phone, I went through the Incredible/Slide root method to root the phone I'm working with (without changing any phone settings within Sense). After getting adb to recognize the device in recovery, I took the steps necessary to flash Amon_RA's recovery. I then took a Nandroid backup of my phone, and extracted the system.img and boot.img files off of the SD card where the Nandroid backup was stored.

Then, I used unyaffs to unpack system.img into 2 separate directories, and used split_bootimg.pl to unpack boot.img

so, for split_bootimg.pl I did this, starting at the directory where each respective boot.img file is

$ mkdir unpak
$ cd unpak
$ split_bootimg.pl ../boot.img 
 
... [output] ...
 
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i

The test after it's unpacked

#!/bin/bash
mydir=`pwd`
for tree in leakv3 RUU ; do
  cd $tree
  touch ./md5sigs
  find . -type f -print | while read fnam ; do md5sum $fnam >> ./md5sigs ; done
  cd $mydir
done
cat leakv3/md5sigs RUU/md5sigs | sort | uniq -u

$ ./md5test.sh
6951ac78e8f9ae5e6c4c4cb50803fed9  ./bin/su
9512ebf90efee5ea996ec59456cf4b03  ./md5sigs
c6212fa45ab99c3a5d731bca06184023  ./md5sigs

This output should be expected; we should expect the su executable to be in one and not the other if I've rooted it, and the md5sigs that the script creates are not going to have the same md5sums

Pastebins for both the leak v3 list of md5sums, and RUU list of md5sums

Leak v3 md5sigs pastebin: 74fcbd4f10fd8fea9ff3b3fe103d07 - Anonymous - PGZDbC1r - Pastebin.com
RUU OTA md5sigs pastebin: 74fcbd4f10fd8fea9ff3b3fe103d07 - Anonymous - qz5z0Vdr - Pastebin.com

Conclusion: They are identical

Since they are the same thing does it still matter to update to the RUU to root the leak phones as the instructions say. I have everything that the instructions ask for but cant see device when I loop with the memory card in and out timing trick.

If i just have the phone in normal mode & connected to pc, I can see it with command prompt and when I loop.

 

[bberryhill0]

Pretty neat stuff....I think.

+10 on that good buddy. Over and out.

 

[tereg]

Since they are the same thing does it still matter to update to the RUU to root the leak phones as the instructions say. I have everything that the instructions ask for but cant see device when I loop with the memory card in and out timing trick.

If i just have the phone in normal mode & connected to pc, I can see it with command prompt and when I loop.

That's actually a good and fair point actually. I think that if you have 2.1 Leak v3, then you probably won't need to flash the RUU in the tutorial.