yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] Swannyman17:
FYI, anyone getting the Error 155 from the moonshine method, reboot to bootloader. Make sure it says fastboot usb and then run the RUU. Doesn't say that in the instructions and kept getting the error. Tried bootloader and it went first try. Hope this helps!

EDIT: Well nevermind. It fails and at 44% and I get error 152. Now im stuck on a black HTC screen with 4 triangles with ! in the middle....

---------- Post added at 08:16 PM ---------- Previous post was at 08:04 PM ----------

How did you get it to take from the manual bootloader?

I get this when I do the manual bootloader (1.15.605.4 to 1.15.605.4) but I am still stuck on the black htc screen with the triangles.
[HTC Droid DNA] andrewlyle:
failure to execute binary in zip

i am getting this message while trying to flash the lock bootloader zip in twrp. WRONG OPERATION! Error executing updater binary in zip. error flashing zip
[HTC Droid DNA] xentheosx:
I just ran the program and it went through... I was on latest version of Viper... Windows 7... I flashed the stock file on the OP page...and installed the drivers about 10 times...
[HTC Droid DNA] majp89:
So I kind of had a big "oops." I ran the hboot and it worked, but I didn't realize that it said to do the stock image first no matter what the method is. So when I run the command to install the img, I get:

C:\Android>fastboot flash splash1 splash1.img

sending 'splash1' (4050 KB)...

OKAY [ 0.614s]

writing 'splash1'...

FAILED (remote: not allowed)

finished. total time: 0.655s

Can anyone help me?

EDIT#2:

I ran the RUU in fastboot and it worked and fixed everything. Everything is working again and I am on stock and happy, ready for the 4.2.2 Sense 5 Update that never will be released :( Thanks for the method!
[HTC Droid DNA] Phaded:
Fyi you only need to flash stock splash of your running a custom one
[HTC Droid DNA] Phaded:
Download again and try again
[HTC Droid DNA] tdizzle404:
hey guys is there a new rooting method with the new ota?
[HTC Droid DNA] zounduser:
Are u referring to the 2.06 ota? If so...then yes, moonshine s-off. Or revone. Revone i couldnt get though. I tried quite a few times, im pretty sure it was because of lack of root.
[HTC Droid DNA] tdizzle404:
If I use moonshiers s~off method is that all I need to do before flashing twrp and roms?

I just seen dome talk about needing to install the super cid app
[HTC Droid DNA] Phaded:
Just do moonshine
[HTC Droid DNA] tdizzle404:
Did it no problems :D loving this phone now lol

Thanks Buddy!
[HTC Droid DNA] Swannyman17:
I reinstalled the drivers and used the download from Mirror #2 (slow as hell) but I'm now stock, locked, and s-on!
[HTC Droid DNA] d08speed3:
This puts you on stock ROM as well correct?

His: HTC DNA

Hers: LG Optimus G
[HTC Droid DNA] Phaded:
stock everything
[HTC Droid DNA] d08speed3:
Thank you for this! My speakerphone blew so I needed to go back to stock. I used the moonshine get back to stock method on the first page and all went well. Just that when I went to RUU it wouldn't read my phone. Kept getting error 170. So I did it in usb fastboot from bootlader and finally read my phone!
[HTC Droid DNA] ricecake2000:
OK

So, I tried the moonshine method, still showed I had S-Off

Tried the commands in the post for it and it wouldnt work.

I am confused on where to put the hboot img file that I downloaded, since if i put it in the same folder as both fastboot and adb then adb appears to be broken.

I need some help with this since I dont know where to put this dang file haha and my phone is going to Verizon on Monday :(
[HTC Droid DNA] ricecake2000:
Ok, so I got it to work, but it is still showing S-off........any way to change that since I now do not have root?
[HTC Droid DNA] Phaded:
You don't need the hboot file unless you are getting errors with RUU. If your s-off still you did something wrong.
[HTC Droid DNA] Bartikus:
So I'm trying to RUU because after flashing 4.3, then deciding to go back to 4.2.2 due to bugs for now, my phone is stuck in roaming and won't activate. I know of at least a few other people that have had this same thing happen to them, who are also stuck.

I downloaded the stock ruu, I flashed the stock hboot (hboot still says 1.33.0001 in the bootloader, but it no longer says moonshine s-off. it says *** TAMPERED *** ***LOCKED*** so I assume it worked?). My problem is when I try to run the RUU as admin on my pc. It immediately stops working and crashes.

Anybody else experience this and have some insight?
[HTC Droid DNA] Phaded:
All you did was flash stock hboot? No commands issued?
[HTC Droid DNA] Phaded:
Remember, you don't HAVE to flash stock hboot. Only if you have RUU problems.

But if you ran the lock command first, then flashed stock boot you're fine. Just gotta get RUU to work.
[HTC Droid DNA] Bartikus:
RUU wasn't working. It was crashing immediately. Since then I've gotten a working RUU from .torrented and ran that. It's trying to activate now but still can't get a signal, though I'm pretty sure it worked because the bootloader no longer says tampered. I know the signal at my house is usually bad, but placing the phone on my window sill usually gets me two bars of 3G. Can't get anything and the phone's been trying to activate for 15 minutes now.
[HTC Droid DNA] Phaded:
A factory reset through the bootloader (not os) should fix your problem.
[HTC Droid DNA] Phaded:
Make sure you're stock everything before doing that tho
[HTC Droid DNA] Bartikus:
How can I make sure that I am stock everything?

UPDATE: Did the factory reset, it worked. Thanks man!
[HTC Droid DNA] Phaded:
Glad to hear
[HTC Droid DNA] dvigue:
can i just run the RUU? will that get me to stock but still unlocked and s-off?
[HTC Droid DNA] Phaded:
Need to be locked to run RUU
[HTC Droid DNA] jmc23200:
It took me 2 days to S-Off following these directions. I was doing it while at work and for whatever reason, I kept getting error messages. I finally decided to try it from my home computer and it worked without one issue.

If anyone is receiving errors consistantly while trying to S-Off, try a different computer. It may save you time and aggravation.
[HTC Droid DNA] beaups:
not true. s-off devices don't need to be locked to RUU.

PSA

The only reason to EVER follow this return to stock guide is if you are planning on selling or returning the device for repair or replacement. There is no other reason EVER to go s-on.

Due to this guide, we've had probably ~50 people in IRC wanting to get s-off again, and struggling due to a variety of issues, but all related to "returning to stock" from this guide. And I've spent countless hours getting them s-off again.

If you are s-off you do not need to relock to ruu, you do not need to s-on to ruu. If you are having some problems that are causing you to want to "return to stock", fine, but going s-on or locking the bootloader in the process isn't going to help.

I'm done supporting these situations in IRC. Any further "I followed the return to stock guide to fix my xxxxx problem, and now moonshine and revone won't work" I will just kick and point back to this thread.

OP - you might consider updating your post, outlining what scenarios would call for using this guide, and what the pitfalls might be.

/PSA

p.s. credit for this command to lock BL "echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796" should have been given.
[HTC Droid DNA] Phaded:
I've noticed them as well. I'll add a big header to OP.
[HTC Droid DNA] beaups:
Thanks, not trying to attack you. It's a fine guide as long as people know what they are getting into.
[HTC Droid DNA] Phaded:
All good lol.
[HTC Droid DNA] thatotherguy..:
need some help,I'm stuck in bootloader, I didn't flash ruu before I write Verizon cid now I can't do anything, anyone know how I can get os back on?
[HTC Droid DNA] Phaded:
Huh? Why did you write the cid? This was a facepalm or jtag device?

Explain exactly what you did
[HTC Droid DNA] ijustwantaname:
Thanks for this guide, I believe it's exactly what I'm looking for! That said, I'm running into an issue: I'm currently on a custom ROM based on 2.04.605.2, but have been S-OFF/unlocked since I bought the phone (1.15?). Prior to finding this guide I already re-locked the phone so that now I'm S-ON/relocked, but the RUU is failing for me (error 158). I tried to flash the stock hboot, but that tells me "FAILED (remote: 12 signature verify fail)." I can tell from the bootloader screen that my current HBOOT is 1.33.0001 & my radio is 1.01.01.0110 but other than that I'm stuck. A little help, good sirs/madams?
[HTC Droid DNA] Phaded:
You need to unlock / s-off again. Can't flash hboot while locked
[HTC Droid DNA] ijustwantaname:
I wondered if that might be the case.. OK, thanks. It seems like all the S-OFF guides I've seen are operating on 1.15 though - is there a specifically recommended way to do it from 2.0x or should I just try with Moonshine/Revone/whatever until something takes? S-OFF again thanks to Revone, proceededing with your guide, fingers crossed..
[HTC Droid DNA] Phaded:
Moonshine will work on 2.0.x
[HTC Droid DNA] ijustwantaname:
I'm good to go! I had to re-flash my recovery for some weird reason but whatever - I'm back to locked/S-ON/stock! Thanks a ton!
[HTC Droid DNA] leroybrute:
I happen to have a monarudo s-off which is a dev device I believe. I have someone interested in buying it and he wants it back to stock. I have searched but can't seem to find an answer. I have also asked in the q&a and nothing.

Any ideas on getting s-off and on stock?
[HTC Droid DNA] ijustwantaname:
I may have spoken slightly too soon. I'm back to S-ON/locked bootloader, patched hboot back to 1.15 and then used the RUU to go back to 1.15 but now I'm not getting the OTA updates. I don't have cell service on the device at the moment but I do have wifi. I saw a comment elsewhere in a thread that suggested factory resetting and then ensuring all the GPS/location services are on, which I've done, but still no updates. Is there some trick to getting it patched back up to 2.06?
[HTC Droid DNA] d08speed3:
http://xdaforums.com/showthread.php?p=42328491

Flash the update using this
[HTC Droid DNA] ijustwantaname:
So I flashed this update and now my wifi won't turn on. It tries, but eventually errors out and gives up. I know I saw a radio component in the firmware but I'm thinking I'm missing something (BL shows 1.01.04.0308)?
[HTC Droid DNA] Phaded:
A factory reset to get data was all you needed. OTA eventually would've downloaded (as long as active SIM card was in device)
[HTC Droid DNA] adrianh85:
i think i screwed something up.... bad my device was on a sence 5 rom and i flashed a stock pls rom and now my device is stuck at at og DNA driod boot animation and power button down for 10 seconds doesnt work. i cant find a way to get back to bootloader or recovery.
[HTC Droid DNA] ijustwantaname:
I'm not saying you're wrong, b/c clearly you know your stuff, but it sat on my wifi for ~1.5 days with me hammering the "Check updates" button and no results. The SIM card is valid although there is currently no service on it - could that be the problem?. Oddly enough, after flashing that 2.06 firmware the OS still reports that it's on 1.15 but my wifi is borked, I can't run the RUU b/c the hboot has been meddled with again, I can't flash the hboot because I'm back to Locked/S-ON, and I can't unlock/S-OFF it b/c RevOne is failing where last time it was successful. I'm having terrible luck getting this thing back to operational stock!
[HTC Droid DNA] Phaded:
OTA needs to come from "service"

Oh you are on 1.15? OS and firmware? Use face palm to s-off.
[HTC Droid DNA] StiM_AddiCt:
I am following the moonshine guide to the T. Keeps erroring out with error 155. Phone is currently:

Moonshine S-Off

TWRP 2.5

NOS GPE Edition Verizon 1.4

No other changes have been made. The commands listed to go "S-On" prior to running the RUU appear to do nothing. After a few failed attempts I booted into the bootloader and it still showed moonshine s-ff. Help please!
[HTC Droid DNA] ijustwantaname:
Well.... crap. I guess I can swap service back to it some weekend or something to get it updated.

I don't know what I'm on anymore. :( The OS reports 1.15 but I definitely flashed that 2.06 FW from a previous post (which is what broke my wifi). My bootloader shows "TAMPERED" but it's still locked/S-ON. SuperCID isn't working for me - it says it works but when I boot into fastboot I still have my VZW__001 CID - which I'm assuming is related to Facepalm won't work either ("remote: 43 main version check fail"). Moonshine fails - it passes the tests but then eventually fails with temp root while waiting for the device. LOL... wat do??
[HTC Droid DNA] Phaded:
You don't go s-on until AFTER RUU. The command before RUU merely lock the device. It won't say locked until after RUU. Try a different usb port for RUU.
[HTC Droid DNA] Phaded:
Worth a shot..

In fastboot, try

fastboot oem writecid 22222222

Reboot fastboot

fastboot oem readcid

What's it say?
[HTC Droid DNA] ijustwantaname:
Sorry that I'm not responding until now, it was one of those days at the office. So I tried it out and writecid responds:

...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (No such file or directory))
finished. total time: 0.005s

..and unsurprisingly, my CID is still the VZW__001 after a reboot. Of possible interest, trying to write the CID seemed to lock up my phone - I had to use the power/volume buttons to reboot it.

I'll gladly wipe this thing and set it back to square-one at this point, but the hell have I done to it?!
[HTC Droid DNA] Phaded:
You locked it before running the ruu, so unless you can s-off again you kinda screwed yourself. I would suggest one if the irc channels related to our device. Someone in their may be able to help.

I strictly offer advice for people using this guide (correctly)
[HTC Droid DNA] Phaded:
Not to be a ****, but I am done offering any help unless you follow this guide correctly. I'm getting tired of seeing people issuing s-on commands before running the RUU or flashing the hboot etc...

So if you can't read or follow steps and mess up your phone, well, that's on you.

The very first part of the guide says to follow the guide as written, in order, yet that seems to be a problem for people.

If you follow this guide as its written, you will have pretty much zero issues, and if you do have one, I'll gladly help.
[HTC Droid DNA] ijustwantaname:
Welp, not one of the times I'm happy to have stumped the expert. Thanks anyway.
[HTC Droid DNA] Burn Stains:
So after I'm at 100% stock, S-ON, with CID 100% stock I can't receive the OTA with no SIM card installed?

Can I do this: You MUST upgrade to 2.06 fw first. To do this, download 2.06 firmware here. https://dl.dropboxusercontent.com/u/...06firmware.zip Then:

adb reboot bootloader

fastboot oem rebootRUU

fastboot flash zip dna2.06firmware.zip

fastboot reboot-bootloader

IMPORTANT! Then, choose "power off" in fastboot menu

to get up to date an then factory reset to make it look good?
[HTC Droid DNA] Phaded:
No as that is not stock everything. You'd honestly be ok sending it as RUU stock. It's still s-on, locked, unrooted... Verizon will bump the software up.
[HTC Droid DNA] Burn Stains:
Yea and if they ask (which I doubt) I'll just say I forever rejected it. :angel:

Thanks.
[HTC Droid DNA] RBThompsonV:
Looks like the link for stock boot image is down? (Trying to go from a JTAG S-OFF to factory... seems as if my phone is eating SIM cards...)

following your guide... it says to jump to psot #4 and from there flash stock splash screen (got to get rid of "this is a developer build" screen... )
[HTC Droid DNA] Phaded:
That is a normal screen. No need to flash a splash screen.
[HTC Droid DNA] RBThompsonV:
Will that go away? It wasnt there when I got the phone...
[HTC Droid DNA] Phaded:
Yes it was, maybe just didn't notice it... That is there on a 100% stock phone
[HTC Droid DNA] armydog13:
The developer warning doesn't appear until you unlock the bootloader I believe
[HTC Droid DNA] StiM_AddiCt:
Still cannot get this to work. Following the guide step by step. Keeps giving me error 155 (unknown error). I have tried different usb ports.
[HTC Droid DNA] StiM_AddiCt:
Finally got this to work. Had to load my TWRP backup of the stock rom. Once I did this it stopped giving me error 155 and then gave me error 158. Flashed the stock HBoot per the guide and then continued on without a hiccup. Thanks for this! Helped immensely. Already using my Galaxy S4 replacement phone. So long DNA...
[HTC Droid DNA] RBThompsonV:
Seeing as how i just got the replacement phone, and the developer message is not on there, i think you may be a little bit incorrect on this factoid... I am happy to send a pic if you'd like
[HTC Droid DNA] Phaded:
Glad you got it sorted
[HTC Droid DNA] Phaded:
Wife has stock phone, has that on boot screen. Different build? Don't know. Never touched her phone tho, it's there. But w/e, it's not even important.
[HTC Droid DNA] fr4nk1yn:
The development warning appears after flashing the eng hboot.

RegawMOD can remove it as well as changing the shown lock status.

[MENTION=2479532]Phaded[/MENTION] Considering the amount of people bricking their phone perhaps put in the tutorial a step with supercid'ing and HTCDEV unlocking. I don't know how it affects warranty but that's gives a way out if they relock before flashing the correct hboot.
[HTC Droid DNA] Phaded:
That isn't just an eng boot message tho... I don't rock the eng hboot and I have it. Wife's stock phone has it.

And honestly I'm thinking of removing the guide altogether... Following it should result in zero issues/bricks. Only real issue should be an image error and that is easily fixed/maneuvered around.

And I don't know the steps for what you did... Write em out and I'll include it in one of the posts
[HTC Droid DNA] RBThompsonV:
Getting Error 152 (IMAGE UPDATE ERROR)

The ROM Update Utility cnnot update your android phone

Please get the correct ROM Update Utility and try again

(I followed the instructions to the letter... Went from CARBON nightly to the latest OTA rooted update to trying this to get back to stock. Used RegawMOD to change orginal boot flash image (got rid of developer warning), flashed locked bootloader, ran RUU, got error 155, flashed stock HBOOT, ran RUU again, got this error... twice now

and phone is on HTC black screen with progress bar at about 95% with an error icon (Triagle w/ exclamation point) (Error symbol popped up around 42% i believe)

Any suggestions?

---------- Post added at 03:07 PM ---------- Previous post was at 02:30 PM ----------

Sorry, should have stated: Coming from JTAG
[HTC Droid DNA] Phaded:
Try a different usb port. If that fails, franklyn can guide you through a different method.
[HTC Droid DNA] RBThompsonV:
Tried a different USB port.. Same result.

Pulled USB after fail, drops to what looks a little like the bootloader screen... But shows:

***TAMPERED***

***LOCKED***

MONARUDO PVT SHIP S-OFF

CID-22222222

HBOOT-1.33.0001

RADIO-1.00.00.1023_3

OpenDSP-v4.120.240.0920

eMMc-boot

Oct 23 2012,21:34:05

Parsing...[downloaded ZIP]

RUU

[1] BOOTLOADER - OK

[2] BOOT - OK

[3] RECOVERY - OK

[4] SYSTEM - FAIL-UZ

[5] SPLASH1 - OK

[6] USERDATA - OK

[7] SBL2 - OK

[8] SBL3 - OK

[9] TRUST_ZONE - OK

[10] RPM - OK

[11] ADSP - OK

[12] PG2FS_SPCUSTOM - OK

[13] TP - OK

[14] SBL1 - BYPASS-S

[15] SBL1 - OK

[16] RADIO_VZ - OK

[17] RADIO_CUST - OK

Image unzipping fail!

Update Fail!

About to try on a different machine with a different download and different cable.
[HTC Droid DNA] armydog13:
Are you trying to RUU from the bootloader screen? Or did you fastboot oem rebootRUU first?
[HTC Droid DNA] RBThompsonV:
Yes, I fastboot oem rebootRUU first...but that was for the hboot.

Why would I enter fastboot to run the RUU? moreso, I CANT enter fastboot or ADB now...
[HTC Droid DNA] RBThompsonV:
OK, I take that back... when I do the RECOVER from the RUU program, i DO have fastboot (just tried it).

And the error happens at 17% (Bar flashes red on phone and then back to green, screen shakes a little the progress on RUU goes 17, 18,17,18 then progresses further but the triangle is at the end of the progress bar on phone.

Any suggestions?
[HTC Droid DNA] detonation:
edit: disregard
[HTC Droid DNA] armydog13:
No suggestion here. Just trying to determine exactly what point you were at when the problem occurred.
[HTC Droid DNA] Phaded:
Usually these image errors are related to the hboot. That or the usb port.

[MENTION=1118153]fr4nk1yn[/MENTION] can guide you through a different method of flashing. Frank please write it out and I'll copy it to the OP.
[HTC Droid DNA] fr4nk1yn:
I would just suggest supercid in case they need up a step. Then writing the original cid before locking.
[HTC Droid DNA] Phaded:
The cid isn't the problem with the ruu tho... Meh, I'm so over this haha

When running the RUU is creates a temp file that can be used to flash in fastboot as opposed to running the RUU as an exe. Can you mirror it Frank? Thought you had a link...
[HTC Droid DNA] RBThompsonV:
Reflashed the stock hboot from post #4.

I got back the bootloader screen and reran the RUU... same thing happens, starts failing at 17-18% ends in error 152

---------- Post added at 06:44 PM ---------- Previous post was at 06:34 PM ----------

Is it safe to write the CID before the RUU is successful?

---------- Post added at 07:09 PM ---------- Previous post was at 06:44 PM ----------

Is this the file you were referencing?

http://d-h.st/J0o
[HTC Droid DNA] Phaded:
No that is not the file.

Run the RUU. When it starts running, check /user/appdata/local/temp on your computer. Should be a file it generates that can be flashed using fastboot. Again, [MENTION=1118153]fr4nk1yn[/MENTION] knows more about that than me
[HTC Droid DNA] RBThompsonV:
I think found it...838MB, called DATA1.zip

How do I want to flash it?

fastboot flash zip DATA1.zip?

---------- Post added at 07:52 PM ---------- Previous post was at 07:47 PM ----------

Nevermind... it's a CAB file...
[HTC Droid DNA] Phaded:
Are you still s-off? With a custom recovery?

If so, boot into recovery and flash a stock Rom. Then try RUU.
[HTC Droid DNA] fr4nk1yn:
That file size looks correct. I uploaded my own for "special occasions":

http://www.adrive.com/public/8kYyds/rom.zip md5: f5a0745a3dee9ac02e261dd42ac67291

My experience writing the CID is OK before. That should'nt effect the RUU process.
[HTC Droid DNA] Phaded:
CID isn't the problem. You can flash hboots locked as long as your s-off still. So as long as no one skips to that any errors can be fixed before hand. It's if they issue the secure flag command before ruu where cid would even be needed.

The issue is the image error. I remember someone suggesting the ruu errors out because of the Rom on the phone.

Want him to try flashing the stock rom then ruu...
[HTC Droid DNA] fr4nk1yn:
OK, I think I'm up to speed now. I'm not subscribed to the thread.

[MENTION=404007]RBThompsonV[/MENTION] download the file from my post above, check the MD5. I had a few corrupt DL's I'm still not sure if it was my PC or not.

Keep the SuperCID until you're done, it's invaluable.

The right hboot is probably the culprit. It has to be the early "1.15", the fastboot way according to a tester didn't work. although I'd be interested in other tries.

Boot into fastboot and the command will be 'fastboot flash zip rom.zip' it will shows errors in real time and the failure or success will be reported at the end.

---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------

But people don't follow directions.

My phone was corrupted for some reason. I did a wipe and nothing would boot afterward. The 152 error is possibly caused by that. If so flashing in fastboot may override that check.
[HTC Droid DNA] Phaded:
Haha true, people don't follow directions...
[HTC Droid DNA] RBThompsonV:
I have changed my CID from 22222222 to VZW__001 and it did improve, but not actually fix the issue.

I am downloading your rom now franklyn

I was coming from a rooted stock rom.

and yes, i am still S-OFF

did i screw up by changing my CID? (I only did it after the suggestion above that it might be my CID)