[RUU]*** THREAD CLOSED*** PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1

[santod040]

PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_Hboot_2_4

PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_2_4

These are the two signed encrypted Official RUU packages for Kitkat, for the Droid DNA.
They are complete and untouched and should be able to be used to update and/or return any DNA to stock kitkat.
I have seen users who are stuck in s-on states, with no OS, and other troublesome scenarios.
I thought posting this up, might help those folks and possibly others as well.

The smaller package, would be the pre-update and the larger one, being the final Kitkat RUU.
I have not used these, as I have no need.
So you are attempting to use these at your own risk.
They are directly from HTC Corporate though, and should be just fine.

First Package: Links removed for now, users seem to be having bad results
Second Package: Links removed for now, users seem to be having bad results

Disclaimer:
This will wipe your entire device!


XDA:DevDB Information
4.09.605.1 RUU, ROM for the HTC Droid DNA

Contributors
santod040
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest hboot, radios and firmware
Based On: Sense 5.5

Version Information
Status: Stable
Stable Release Date: 2014-05-26

Created 2014-05-27
Last Updated 2014-07-05

 

[santod040]

Reserved

--Boot into Bootloader/Fastboot USB Mode

Step 1.)

 fastboot oem rebootRUU

-- Wait for the device to reboot to a black screen with a silver HTC logo

Step 2.)

 fastboot flash zip filename.zip

Repeat

Step 3.)

 fastboot flash zip filename.zip

-- When it says it is done in the terminal/cmdprompt execute the following
[The green bar only fills up about 75% of the way]

Step 4.)

 fastboot reboot

 

[santod040]

Reserved

 

[jamiethemorris]

This is something that should go without saying, but maybe some people don't know, perhaps you should just put a note in the op saying it will wipe the entire sdcard.

Sent from my Droid DNA using Tapatalk

 

[ryryrocco]

If I run these how will it effect my s off/unlocked status. Do I need to relock to run if I am s off unlocked/rooted.

Sent from my Nexus 7 using XDA Free mobile app

 

[billa]

The smaller pre-update goes through fine, but then the larger one fails with a signature error.

This is what I've done so far...

fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip small.zip
fastboot flash zip small.zip
*** went though fine ***

fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip large.zip
*** uploaded fine, then checking signatures and finally failed with this message ***
C:\Cell\Android\ADB>fastboot flash zip large.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1111519 KB)...
OKAY [ 41.739s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 186.424s


Bootloader is v 1.57.0000 locked, S-ON
Now obviously I can't S-Off it since it's getting stuck on the HTC bootlogo.
Any suggestions? thanks

 

[Epiel]

The smaller pre-update goes through fine, but then the larger one fails with a signature error.

This is what I've done so far...

fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip small.zip
fastboot flash zip small.zip
*** went though fine ***

fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip large.zip
*** uploaded fine, then checking signatures and finally failed with this message ***
C:\Cell\Android\ADB>fastboot flash zip large.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1111519 KB)...
OKAY [ 41.739s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 186.424s


Bootloader is v 1.57.0000 locked, S-ON
Now obviously I can't S-Off it since it's getting stuck on the HTC bootlogo.
Any suggestions? thanks

Same here!!

---------- Post added at 05:05 PM ---------- Previous post was at 04:28 PM ----------

PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_Hboot_2_4

PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_2_4

These are the two signed encrypted Official RUU packages for Kitkat, for the Droid DNA.
They are complete and untouched and should be able to be used to update and/or return any DNA to stock kitkat.
I have seen users who are stuck in s-on states, with no OS, and other troublesome scenarios.
I thought posting this up, might help those folks and possibly others as well.

The smaller package, would be the pre-update and the larger one, being the final Kitkat RUU.
I have not used these, as I have no need.
So you are attempting to use these at your own risk.
They are directly from HTC Corporate though, and should be just fine.

First Package: LINK
Second Package: LINK

Disclaimer:
This will wipe your entire device!


XDA:DevDB Information
4.09.605.1 RUU, ROM for the HTC Droid DNA

Contributors
santod040
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest hboot, radios and firmware
Based On: Sense 5.5

Version Information
Status: Stable
Stable Release Date: 2014-05-26

Created 2014-05-27
Last Updated 2014-05-27

he smaller pre-update goes through fine, but then the larger one fails with a signature error.

This is what I've done so far...

fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip small.zip
fastboot flash zip small.zip
*** went though fine ***

fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip large.zip
*** uploaded fine, then checking signatures and finally failed with this message ***
C:\Cell\Android\ADB>fastboot flash zip large.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1111519 KB)...
OKAY [ 41.739s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 186.424s

Help me bro!

 

[santod040]

As I said in the OP.
I have not used these, as I have no need.
Do so at your own risk.
I posted them hoping they would help people in already soft bricked situations, etc,..
But they seem to be doing more harm then good, so I have removed the links.
Sorry for any trouble they caused.
Only suggestion I have is, check your MD5's and I will double check my source files against what's uploaded again, later today.

 

[billa]

As I said in the OP.
I have not used these, as I have no need.
Do so at your own risk.
I posted them hoping they would help people in already soft bricked situations, etc,..
But they seem to be doing more harm then good, so I have removed the links.
Sorry for any trouble they caused.
Only suggestion I have is, check your MD5's and I will double check my source files against what's uploaded again, later today.

It didn't do any damage at all, the small pre-update went though fine just the larger OS failed.
No harm done, though I noticed that the contents of the larger file is missing some files in the archive. I've read on some other forum that the correct update file is around 600k instead of 1gig (your file seems to be padded with something).
I have downloaded it twice from two different mirrors, maybe check your local hard drive file size against the upload and see if there's any discrepancy.

 

[santod040]

It didn't do any damage at all, the small pre-update went though fine just the larger OS failed.
No harm done, though I noticed that the contents of the larger file is missing some files in the archive. I've read on some other forum that the correct update file is around 600k instead of 1gig (your file seems to be padded with something).
I have downloaded it twice from two different mirrors, maybe check your local hard drive file size against the upload and see if there's any discrepancy.

It's a factory RUU, not the OTA files.
I already posted the OTApkg.zips.
This is intended to be a full signed stock rom.
Meaning you should be able to apply it, no matter what was on the device prior.
It does not patch an existing install, it supposed to install the full OS/rom.
RUU's and OTA zips are two different things.

 

[billa]

It's a factory RUU, not the OTA files.
I already posted the OTApkg.zips.
This is intended to be a full signed stock rom.
Meaning you should be able to apply it, no matter what was on the device prior.
It does not patch an existing install, it supposed to install the full OS/rom.
RUU's and OTA zips are two different things.

Completely understand, but there must be something wrong with the larger file as it's failing on an identical version unit with the bootloader and s-on locked (and same is happening with other users).
By definition an RUU (and its rom.zip component) should restore an equal or lower version unit without failing.

 

[santod040]

Completely understand, but there must be something wrong with the larger file as it's failing on an identical version unit with the bootloader and s-on locked (and same is happening with other users).
By definition an RUU (and its rom.zip component) should restore and equal or lower version unit without failing.

I am aware it seems to have an issue, and aware of what it should be able to do, that's why I pulled the links for now.
I actually just got done downloading the file again and am about to check it against what I already had.
Will update with more info, when/if I have anything new to add.

MD5 is still exactly the same... :/

 

[billa]

I am aware it seems to have an issue, and aware of what it should be able to do, that's why I pulled the links for now.
I actually just got done downloading the file again and am about to check it against what I already had.
Will update with more info, when/if I have anything new to add.

MD5 is still exactly the same... :/

Looking inside large archive, the total sum of the file sizes adds up to less than 10 megs, far from about 1gig, unless there are some hidden files...

android-info.txt 104 .... 2014-03-13 7:18:32 pm
boot_signed.img 6,727,936 .... 2014-03-13 8:10:10 pm
dzdata_16g.hdr 13,872 .... 2014-03-13 7:57:06 pm
dzdata_16g.img 679,472 .... 2014-03-13 7:57:06 pm
dzdata_32g.hdr 20,272 .... 2014-03-13 7:57:24 pm
dzdata_32g.img 939,824 .... 2014-03-13 7:57:24 pm
dzdata_64g.hdr 24,064 .... 2014-03-13 7:58:00 pm
dzdata_64g.img 1,171,456 .... 2014-03-13 7:58:00 pm


If you had the full ruu.exe it would be easy to extract it all.

 

[Epiel]

I just have to wait!

 

[goodman_east]

Completely understand, but there must be something wrong with the larger file as it's failing on an identical version unit with the bootloader and s-on locked (and same is happening with other users).
By definition an RUU (and its rom.zip component) should restore an equal or lower version unit without failing.

just because the encryption key has changed compared to RUU3.06.605
so u cannot flash RUU4.09.605 directly.
but u can flash the fimeware.zip from the OTA4.09.605, then flash the RUU4.09.605

---------- Post added at 10:31 AM ---------- Previous post was at 10:17 AM ----------

I am aware it seems to have an issue, and aware of what it should be able to do, that's why I pulled the links for now.
I actually just got done downloading the file again and am about to check it against what I already had.
Will update with more info, when/if I have anything new to add.

MD5 is still exactly the same... :/

firstly, the ruu encryption keys changed several times.RUU1.15.605.* has the first key. RUU2.0*.605, including 2.04.605, 2.06.605, 2.08.605, has the second key. and RUU3.06.605.* has the third key. above all can be decrypted easily. but RUU4.09.605 has the second generation way of encryption and the key changed again.
secondly, ur ruu has been decryption, and some .imgs havelost.

 

[billa]

just because the encryption key has changed compared to RUU3.06.605
so u cannot flash RUU4.09.605 directly.
but u can flash the fimeware.zip from the OTA4.09.605, then flash the RUU4.09.605

Yes in the first step the smaller pre-load firrmware.zip file goes through fine, but then in the second step with or without rebooting and trying to flash the larger OS file it fails with a key error. Isn't the function of the pre-load to update the keys and prepare the device for the OS file?
Usually the larger OS file also contains a copy of the smaller pre-load files, but looks like it's missing in this one.

 

[Epiel]

I have around one month with my phone without OS, I hope you can fix it!!

 

[goodman_east]

Yes in the first step the smaller pre-load firrmware.zip file goes through fine, but then in the second step with or without rebooting and trying to flash the larger OS file it fails with a key error. Isn't the function of the pre-load to update the keys and prepare the device for the OS file?
Usually the larger OS file also contains a copy of the smaller pre-load files, but looks like it's missing in this one.

i'm trying to get the RUU4.09.605.* and can share it.

---------- Post added at 12:24 PM ---------- Previous post was at 12:21 PM ----------

Yes in the first step the smaller pre-load firrmware.zip file goes through fine, but then in the second step with or without rebooting and trying to flash the larger OS file it fails with a key error. Isn't the function of the pre-load to update the keys and prepare the device for the OS file?
Usually the larger OS file also contains a copy of the smaller pre-load files, but looks like it's missing in this one.

Isn't the function of the pre-load to update the keys and prepare the device for the OS file?

yes, the key is in hboot.img.
and the pre-update step is to update the hboot.img

 

[tat2me2]

I hope someone comes up with a solution for this problem, I need to restore my wifes DNA but i'm only able to flash the smaller zip as well - tried everything from factory reset to recovery in the hboot menu, nothing is working, just keep getting bootloop.

 

[mopartonyg]

just because the encryption key has changed compared to RUU3.06.605
so u cannot flash RUU4.09.605 directly.
but u can flash the fimeware.zip from the OTA4.09.605, then flash the RUU4.09.605

Have you tried this method or just guessing? would be important to know if this really works your way.