yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] Phaded:
Possibly a bad download, Download the HBOOT again and give it another go.

Also, with that error you are getting during the RUU process, did you lock the bootloader back up before running the RUU? That error sometimes shows up from not doing that.
[HTC Droid DNA] Deleted member 2427418:
I don't know if this will help anyone or not, or if this was known and I was just being stupid, but I was getting the ERROR [155] as well when running the RUU and I knew my hboot was correct as well as locked so that wasn't the problem, so I attempted to run the RUU again and saw that it was saying my current version was 1.28.xxxxxx which made me realize that that was the Sense 5 roms version number and not the actual version number of my phone causing it to fail. What I then did was i downloaded an AOSP based rom (but I would surmise that a sense 4 DNA rom would work as well) and flashed that then tried again. After doing that it showed the correct version number in the RUU and processed correctly!!

For a little more in site I was on the following setup:

Moonshine S-OFF

Joelz Stock Sense 5 <-- What caused the Error 155

Carbon ROM (Built by Pio) <--- What fixed the error (Would work with any AOSP or Sense 4 Rom ***Needs tested***)

**Edit**

Also incase anyone was wondering I was doing this to fix my phones radio, for some reason when flashing certain roms it gets stuck in Roaming no matter what you do. To fix it I just take my phone completely back to stock S-ON etc, then go into the bootloader and hit factory reset with the stock recovery and it seems to fix it, then S-Off and unlock again and go about my business. I couldn't actually find an answer besides "RMA the thing" to fix the radio roaming issue, so i figured i'd add that incase anyone else was/is in the same boat. :)
[HTC Droid DNA] Phaded:
Hmm... I'll do a bit of testing on that with random Sense 5 vs AOSP/Sense 4 ROMs. If that is the case, I'll edit the guide.
[HTC Droid DNA] Imacellist:
I successfully restored my droid dna to untouched stock with this method. I had to exchange my DNA for a new one due to problems I was having and I am trying to do everything I can to make sure that there is no evidence of my tampering. One thing someone mentioned was to take the OTA's to get the device up to current 2.06 since I have been rooted and such since the first day it was available and am on 1.15. I have tried manually checking for software updates and it doesn't seem to find anything. It hasn't prompted me yet and I am wondering if because I am so far behind if they update system isn't checking or something else it wrong. Any thoughts? Any ways to manually update to 2.06 like flashing a new RUU (if that exists)? Thanks.
[HTC Droid DNA] Phaded:
Just leave the phone on... I did it a few weeks back. It will eventually update.
[HTC Droid DNA] Imacellist:
Thanks. Verizon is only giving me 5 days to ship it back haha. So I just wanted to figure it out as quickly as possible.
[HTC Droid DNA] Phaded:
Confirmed that on Sense 5 ROMs it randomly errors out. Editing guide.
[HTC Droid DNA] gris1016:
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
[HTC Droid DNA] Phaded:
The RUU itself crashes on the computer or the phone crashes and reboots?

Also the hboot I have linked should give you version 1.31 I do believe.
[HTC Droid DNA] death4u:
Thanks for this, worked perfectly!
[HTC Droid DNA] chayos00:
I am having issues not getting the phone to return to "Locked" status. I have and am running the stock ROM. Just reset back to factory. I am following the commands to the T. Below is what my CMD prompt shows that I typed in, or copied and pasted for the echo command. I was trying to follow the note about the echo command but I could see nothing wrong with it... also in the end I had to type exit command twice for it exit and go back to the prompt for the next folder.
[HTC Droid DNA] fr4nk1yn:
Use the dna2.06firmware.zip in the moonshine thread then flash it in fastboot again.

No need to donate to me, but thanks.

Donate to a charity of your choosing or just pay it forward.
[HTC Droid DNA] scheirere:
What moonshine thread are you talking about?

I'm also having trouble getting back to stock. I'm moonshine s-off and on a rooted stock rom (2.06.605.1). When I tried the RUU file, it would go for a while then say that I needed to use a different RUU that was compatible with my ROM. I tried the proceedure a couple times and really made a point to follow the directions to a "T". But no luck. Any help is greatly appreciated!!
[HTC Droid DNA] Phaded:
SIM needs to be in I do believe. Only takes 10-15 mins before it catches the update

And while I appreciate the gesture I don't accept donations. Just like helping out. :D
[HTC Droid DNA] Phaded:
Try flashing the stock hboot first. If you did that read a few pages back on a different option.
[HTC Droid DNA] Phaded:
You can also try flashing the very first stock build + hboot, then running ruu. Did it today with no issues.
[HTC Droid DNA] nicodemu5:
Having some trouble getting my hboot to flash back to 1.15, on 1.33, my CID is 11111111, and i am facepalm S-Off, i try flashing the hboot and it is successful but when i get back into the bootloader it says I am still 1.33...not really sure what to do, im using viperdna...any help would be great :)
[HTC Droid DNA] Phaded:
1.15 is related to the software build number.

I do believe it should be 1.31
[HTC Droid DNA] Phaded:
After flashing 1.15 hboot it should show 1.31 as version #

If this isn't happening I wonder if the hboot download is corrupting itself...
[HTC Droid DNA] scheirere:
Phased,

What did you mean by the very first stock build? Do you have a link to the file or thread containing it? Sorry to be so "slow".
[HTC Droid DNA] RBThompsonV:
I can confirm.. SIM NEEDS to be in to try the update...

As for the beers, if you guys are ever in the Reading or Lancaster PA area, or the Baltimore Maryland area... hit me up... your bar tabs (or all of a days worth of coffees/redbulls) are on me..

AS for the instructions.. not to know more than you guys.. but rather than having in post 4 to flash the stock boot splash... maybe recommend a stock rom or stock rooted rom to flash first and foremost (of course, thats what I did... which may have led to all of the horribleness that happened, but it think it was something else... like gremlins)

Additionally, maybe have a backup of the ruu zip and instructions (happy to write them if you want... and host them on dropbox til it's depleted)..

Just trying to pay it forward
[HTC Droid DNA] fr4nk1yn:
I think having the file across multiple sources is a good thing. Like I mentioned I had bad DL's which was quite confusing. I thought my phone was gone.
[HTC Droid DNA] Phaded:
Tomorrow or Monday I will add different mirrors
[HTC Droid DNA] Phaded:
Typo on my part..

Ignore...

Gotta make sure hboot is right, 1.31
[HTC Droid DNA] nicodemu5:
Thanks for the reply, I was able to get RUU working after i flashed a stock rom and then flashed the hboot, showed up as 1.31 and am now S-ON full stock, thanks for the help :)
[HTC Droid DNA] Phaded:
Yea, I'm starting to think that a stock rom should be flashed first.

Gonna edit the guide tomorrow

Which stock rom you flash? Can you link it?
[HTC Droid DNA] nicodemu5:
Yeah here you go, this is the rom i flashed http://xdaforums.com/showthread.php?t=2056756
[HTC Droid DNA] scheirere:
Well...I'm not having any luck with this, despite a bunch of attempts. Initially I tried the steps outlined in the moonshine s-off post with the RUU coming back and telling me I needed a different RUU for my current ROM (2.06.605.1 710RD). Next I tried to flash the ROM suggested in the previous post. No Luck with that. I kept getting an error that the android system has stopped. Then I tried to flash the H-boot file suggested in post #4. No luck. I can't get the phone to do anything after rebooting into the boot loader. The command window program just sits waiting for the device, which never happens. Any other suggestions? I gotta be missing something small, right?
[HTC Droid DNA] Phaded:
No luck on hboot? Meaning ruu still failed or hboot didn't work?

And you flashed above rom with custom recovery yes?
[HTC Droid DNA] scheirere:
I tried the ROM but I kept getting an error message that kept popping up so I couldn't do anything. I had to reboot into recovery and flash a backup. And I couldn't flash the hboot file either. The phone didn't respond to the command window after booting into the fastboot. It just sat at the fastboot screen. Adb devices worked fine but the line with fastboot command didn't do anything.
[HTC Droid DNA] armydog13:
I used to have that issue all the time. Now whenever I plug my phone in, I reinstall the HTC drivers before I do. Never had any more issues with fastboot after I started doing that.
[HTC Droid DNA] Phaded:
Sounds like a driver issue. Reinstall htc drivers
[HTC Droid DNA] n0xx187:
Im running [ROM]9.24.2013 NOS M7 v3.0.7 [Sense 5.0 JB 4.2.2]Optimized&Stable

and when i try to flash the stock splash1.img it says this

sending 'splash1' (4050 KB)..

OKAY [ 0.579s]

writing 'splash1'...

FAILED (remote: not allowed)

finished. total time: 0.627s

i read something about needing the ENG hboot but im not sure .

Thanks
[HTC Droid DNA] n0xx187:
ok so i got the the phone back to locked and now im getting the 155 error then i do the RUU I am on a sense 5 rom as you can see from the post above. what do i need to do to fix this.

My replacement phone will be here today.

Thanks again guys

---------- Post added at 07:38 PM ---------- Previous post was at 06:53 PM ----------

Ok got it to go by maunally booting into the bootloader not sure why that worked but would be nice to put in the guild..

Thanks guys

---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------

Ok got it to go by maunally booting into the bootloader not sure why that worked but would be nice to put in the guild..

Thanks guys
[HTC Droid DNA] mcsplatt:
Ok I can not get adb or fastboot to see my phone. Wtf? Yes, debugging is checked. Updated sdk, tried the pdanet thing, no dice. Also my desktop is ancient and only has usb2 and I have used adb previously on this phone using the same port. Any ideas why I would have lost it? I need to get to stock to warranty it.

Would a stock rom make any difference? It won't even see it in recovery or bootloader tho so probably not
[HTC Droid DNA] rsims26:
I've had this happen once and I reinstalled the drivers with HTC Sync on my computer and then it worked fine. Then after I got it back to stock I made sure to delete the HTC sync off my computer since it doesn't play nice with Moonshine.
[HTC Droid DNA] OverrideJones:
My phone is root with clockwork mod and I need to have it sent in for repair also... which one of those methods works for me?
[HTC Droid DNA] bksyfer:
Ok... I have read the whole 21pg forum but couldn't find a user with the same issue that replicates mine.

I am running Moonshine S-off, used Windows 8 system and than a Windows 7 system to RUU. While

experiencing the same issue same issue.

Let me give you a run down of what I did and present my problem.

-I went through hell getting advanced and fastboot to recognize

My solution:

uninstall all device manager drivers correlating with the phone driver

Install pdanet HTC Driver through twice hell your computer might install the driver themselves

Using only SENSE 5 ROM or AOSP ROM while

+on android screen: ADB and

+on fastboot screen: Fastbooot

Success

-I locked through

Code:

adb devices (verify device ID is listed)

adb shell

su

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796

exit

&

Fastboot OEM lock

Success

PROBLEM

-Rebooted to fastboot

Started RUU with 158 error

went to flash HBOOT with no success

displaying

FAILED <remote: not allowed>

Any solutions?
[HTC Droid DNA] Uzephi:
Check instructions for moonshine again. "If you get 158 error flash stock hboot, follow instructions on post 4."

Did you try that yet?

Sent from my Rezound
[HTC Droid DNA] bksyfer:
Yes after 158 error

I went to flash HBOOT STOCK:

FAILED <remote: not allowed>

displayed in cmd.

Prior to the error 158 message I was using a different USB cable. The RUU prossess will seem like it is going through until it reaches the sending process. The ...... (decimals) after sending still moves so I know the process is not frozan however it is just stuck at the sending...process and goes nowhere fore hours while on the black HTC screen. Triedflash PL38IMG with same cable it would get stuck at fastboot screen.

After I used another cable is when 158 error messagefor RUU started and FAILED <remote not allowed>forPL38IMG appeared.
[HTC Droid DNA] Phaded:
Are file extensions hidden? If so, make sure you didn't rename it .zip.zip
[HTC Droid DNA] bksyfer:
Problem solved. Man, it is amazing what reading carefully can do for you.

I left out

fastboot oem rebootRUU

on the command prompt when trying to flash 1.15 hboot.

Mad at myself right now, but happy I'm yet again back rooted and no more roaming or no service signal.

Thank ya'll for helping me diagnose my problem.
[HTC Droid DNA] -Abuse-:
help please!!

Help please .. I read this entire thread and saw someone with the same issue but didn't seem to figure out the solution. I flashed the stock HBOOT first, then am trying to do the splash1 and am getting the following error:

fastboot flash splash1 splash1.img

sending 'splash1' (4050 KB)...

OKAY [ 0.576s]

writing 'splash1'...

FAILED (remote: not allowed)

finished. total time: 0.611s

When I'm in fastboot after doing fastboot flash zip PL83IMG.zip it shows:

*** TAMPERED ***

*** UNLOCKED ***

MONARUDO PVT SHIP S-OFF

CID-VZQ__001

HBOOT-1.33.0001

RADIO-1.01.04.0308

OpenDSP-v6.120.274.0114

eMMC-boot

I don't want to run the RUU executible before i get the stock splash screen restored. I need to send in the device for warranty replacement so need it returned to pure stock. any idea how to get the splash1 to flash successfully? Do i need to moonshine again or something and start over? I'm thinking that i did fastboot flash zip PL83IMG.zip first instead of the splash1 and that's my problem? How to remedy?

Thanks for the help!!!!

SOLUTION ---- got it to work! Even though I had a custom boot IMG (Viper) I did not have to restore it. However, i was getting ERROR 155 trying to install the RUU. The solution that worked for me another user had was going into fastboot and running the RUU from there. It worked AND put on the stock boot image... following the rest of the instructions from there and it was smooth sailing..
[HTC Droid DNA] Nowak4G:
I originally used moonshine but I had to lock my bootloader so I could RUU back to stock. I'm still S-OFF but cant flash a recovery. I tried to re moonshine and failed after "moonshinig" 10 times. Is there a command I could use to simply unlock like used to lock the bootloader?

Like this one:

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796

Edit:Got a recovery flashed, guess I don't really need it unlocked if s-off.
[HTC Droid DNA] Gutsyslap1:
Having some issues and I'm not sure if I'm just an idiot or what. Computer is recognizing my device is connected through ADB Devices no problems there. After downloading the RUU and trying to run it as administrator on my PC nothing happens. I have restarted my computer and I'm still not sure why it wont start up. What am I missing here? Thanks in advance for the help.

Edit: I completed S-OFF via moonshine method and I am following that guide.

Edit #2: Just compared file sizes and my version has about 500MB less than the stated download size.
[HTC Droid DNA] thayl0:
So ur trying g to get ur device back to bone stock ?
[HTC Droid DNA] Gutsyslap1:
Yeah I'm having an issue with my radio. I had a bad flash I'm thinking and was advised this could fix it by a number of people. My phone is only in roam, no data either and shows my number as all zeros. Tried other roms and full wipes of course and no luck. Went to vzw and replaced the Sim card and that didn't fix it so I'm trying to go back to bone stock and then root and s off again because a few people I've seen is this thread have had this problem. I have now been able to get the ruu to run but I'm getting error 155 so I'm trying to update my hboot which I'm having problems pushing the zip to it via adb because this is the first I've had to use it in probly 3 years.
[HTC Droid DNA] RLGL:
CM 11 did that to mine. Took about 5 hours and many rom flashes and radio flashes and factory resets to get it to straighten out. The final steps were the RUU and OTA updates with a factory reset between each one. Tonight I will go back to VIPER. One thing I noticed about VIPER is an option to set radio band, that was a temporary fix that would not stick.
[HTC Droid DNA] Gutsyslap1:
Well that's a huge relief because that's the exact issue I was having. Tried to flash beans which is cm11 and didn't have the correct version of cwm and that's where everything went nuts. Just need to get more familiar with adb again to make this process easier. Did you flash the hboot from post 4?
[HTC Droid DNA] thayl0:
What is your radio version. And what ROM r u currently running.
[HTC Droid DNA] Gutsyslap1:
Not 100% on the radio version as I'm at work and don't have the device with me but the ROM was nos m7. I can check what baseband when I get home around 515 eastern.
[HTC Droid DNA] Gutsyslap1:
Here is my baseband version. Im running NOS 3.0.7.
[HTC Droid DNA] RLGL:
Yes ,I used that hboot 1.15. Back on Viper and all is well.

I think the CWM recovery I used might have been corrupt causing the issues.
[HTC Droid DNA] Gutsyslap1:
Did you have to flash back to a sense 4 ROM? I was able to flash hboot 1.15 last night finally and still couldn't get the ruu to not have errors. I flashed an old sense 4 ROM so we will see how it goes tonight.
[HTC Droid DNA] RLGL:
It was only after going back to the stock rom and updating it with many factory resets was I able to get out of roaming
[HTC Droid DNA] Gutsyslap1:
Ok cool, I flashed to a 2.06 rom so im wondering if ill have issues with it or not tonight when I try the RUU again.
[HTC Droid DNA] Gutsyslap1:
What should the bootloader list in order for this to work? Tampered, S-off, locked etc.....
[HTC Droid DNA] Phaded:
Unlocked and s-off...
[HTC Droid DNA] Gutsyslap1:
Sorry should have been more specific. I completed the locking process and then was getting error 155 during the RUU. Saw some people having luck with that error in the thread by flashing the HBOOT in post 4 so I did that and always went to an old sense 4 rom. After completing that it now shows as ***Tampered*** ***LOCKED*** but still s-off and that my hboot is 1.33.0001. Now I am also having (im assuming unrelated) ADB issues and its showing the device as offline and when running the RUU I get error 170 so im in the process of trying to fix that now as well by deleting the entire SDK and redownloading and setting back up. Any suggestions to make this work? I'm going through this process trying to relock and go back to stock because I have either no signal or roam and my device wont program. I know its not the sim as I had that replaced and im using a backup gnex. Sorry for the late response and ANY help is greatly appreciated.

Edit-Tested ADB commands with my gnex running CM11 and it worked no problem so it showing offline is a DNA problem not ADB.
[HTC Droid DNA] mopartonyg:
What operating system are u running on your PC? if u are using windows 8.1 and sometimes 8, the htc drivers are outdated and will not allow u to use fastboot. I have a thread in question sec all about that issue. I can use adb but not fast boot on my windows 8.1. Finally dual booted Linux Mint in order to use fastboot commands. Hope this helps ya
[HTC Droid DNA] Gutsyslap1:
Wow that's an interesting problem. I have windows 7 so I don't think that's it but that's a good point. I have an older laptop I can give it a shot on but my only thought is that it was working fine earlier though.
[HTC Droid DNA] mopartonyg:
Maybe try and updating the drivers on your pc and when u reinstall sdk make sure u have the latest version. I will look around for more answers.
[HTC Droid DNA] Phaded:
Abd matters not. You need.to.flash hboot in fastboot, then ruu
[HTC Droid DNA] Gutsyslap1:
So you think if I flash the ph83 file in fastboot I should be good? I was able to push that via adb but it still says 1.33 not 1.15.
[HTC Droid DNA] Phaded:
Follow exact steps in post 4
[HTC Droid DNA] Gutsyslap1:
Knocked that out last night, same problems. New SDK, new RUU, new drivers, and still showing device offline. As Phaded suggested to just following the instructions in post 4 (which I did exactly) I'm still not having any luck.

---------- Post added at 08:16 AM ---------- Previous post was at 08:14 AM ----------

Followed that exactly originally, shows 1.33 and getting errors within the RUU.
[HTC Droid DNA] mopartonyg:
This sounds stupid but did u try all the easy stuff like turning debugging on and off while phone is plugged into pc. Also u can use a program called pda.net go help the pc see your phone
[HTC Droid DNA] Gutsyslap1:
Doesn't sound stupid at all, I have very little experience at all with ADB so ill give it a shot tonight and update later. Thanks for the suggestions.
[HTC Droid DNA] Phaded:
Hboot will read 1.31 (IIRC) when properly flashed. It doesn't seem like it's flashing correctly. Are you getting any errors during flash? Also, try to download the hboot again. Could be bad download.
[HTC Droid DNA] nsmal24:
If I'm moonshine s-off, what's the best way to take the new ota staying s-off? Run the lock command, flash stock h-boot, and ruu? If so, how do you re-unlock since moonshine does the unlocking for you?
[HTC Droid DNA] Phaded:
Wait for someone to release the ota
[HTC Droid DNA] outkast2012:
I have a unlocked s-off DNA running viper 2.1

I am sending in my DNA with a broken screen to Asurion insurance. I have the total equipment coverage w verizon

Will I have to return to stock?
[HTC Droid DNA] Uzephi:
Not for insurance claims. Only Warranty

Sent from my DNA using my mind.
[HTC Droid DNA] 2alive:
I'm new to DNA (gsm user, not verizon) and can´t get data working so I´m going stock to see if fresh install solves the issue, from what I read I understand that in moonshine case there's no need to flash stock hboot and splash is that right?

Just lock and ruu...
[HTC Droid DNA] outkast2012:
Thank you for a quick reply!
[HTC Droid DNA] Phaded:
I'm going to update this tomorrow with the new ruu... Should alleviate any hboot issues in the future
[HTC Droid DNA] Spider210:
So I don't remember which method I used to unlock my phone, I am sending it in to HTC directly, .for a swollen back which over the past week formed a blue dot on my screen, ( I think battery is shot) I am skipping the verizon warranty process because they'll just give me someone elses broken phone

I used the htc method right when the phone was released, whats the best way to get back to stock, receive the ota and relock. I don't want any issues with warranty because of it being unlocked.

Let me know the direct steps in doing this as I am rusty! any help is much appreciated!
[HTC Droid DNA] Phaded:
Facepalm

Skip s-on part off your only unlocked
[HTC Droid DNA] Spider210:
I'm also s-off I did it all at the same time

Sent from my DNA
[HTC Droid DNA] Phaded:
Facepalm then
[HTC Droid DNA] billy0679:
RUU problem

ok so i finally got a good download of the 1.15 RUU, ran that all was good, got s-on and all went well. reloaded bootloader to find that it says relocked. will taking the ota get rid of that? or is there something else i need to do? any help would be greatly appreciated, gotta ship this phone back to vz in the next day or so.
[HTC Droid DNA] tsruggles:
I can't get the RUU to run on my Win7x64. I click run as administrator and nothing happens. I've downloaded through ie and chrome to no avail,