yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] santod040:
As far as I know, that's all they need to know you are rooted.

I was told it was so they could better troubleshoot tech calls, to know what state your phone is in.

While I agree that could be useful info, I do not agree with their prying to get that information.

Granting access, probably just gives them quite a bit more info about the device's software state.
[HTC Droid DNA] mobitote:
With regard to tethering .. In earlier stock ROMs (dunno bout this current version haven't tried it yet) I normally disabled tethering guard using tb and installed tethering app of choice and all worked fine for those interested in tethering.
[HTC Droid DNA] takota6:
Little help.. In having problems with adb on winXp. adb devices shows my device but upon fastboot cmds it will reply waiting..different usb with no diffrence,I ask because I'm doing something wrong.On that note I did today restore to stock a phone that is being sent back without isuues ,but this new replacement is kicking my butt same hboot recovery
[HTC Droid DNA] badogg:
Hey Santod, I went back to this stock Rom but I'd like to get the messaging app from the GPE Rom of yours. Is it as simple as find the .apk that is in that zip and installing it to this one? I just love the colors and bubbles and whatnot from that Rom compared to the HTC messages app which I've never cared for.

Thanks a ton for everything!!
[HTC Droid DNA] finanandroid:
http://xdaforums.com/showthread.php?t=2721480
[HTC Droid DNA] badogg:
I tried what was suggested, but I get permission denied when trying to write to anything in /system. I guess it is due to some security in the stock kernel? So does that mean I'd have to load something like iHate's kernel or NuK3r3L or something to do this?

Appreciate the help... :highfive:

Edit: I got it installed there. Now to mess with it and figure out how to get it to install/work. Thanks again!!
[HTC Droid DNA] toolsoldier:
true, app doesnt show in app drawer, but it does appear as a widget..weird, any fix for this?..
[HTC Droid DNA] ancola66:
I confirm after flashing SU 1.94 >>> root that works good.
[HTC Droid DNA] Protonus:
Thank you [MENTION=1331268]santod040[/MENTION] for providing the easily flashed, stripped firmware+radio file, flashed it over top Viper 3.5.0 - no issues! And thanks for already answering every question I had previously in this thread!
[HTC Droid DNA] collegencmc:
Really dumb question here, I'm on GPE Rom, I flashed the radio and everything seems to be working just fine, everything I checked it looks like it took the update. But do I still need to flash a boot.img? It doesn't look like I need to, but I just thought I would ask.

Sorry if this has already been asked.
[HTC Droid DNA] Imacellist:
Are you saying you are currently on a gpe ROM and are going to move to this ROM? Then yes you should flash the new firmware. It will work without but you will have some issues. If you are staying on the gpe ROM then I think you are fine.
[HTC Droid DNA] collegencmc:
No I'm staying on the GPE ROM, just wasn't sure if I still needed to flash it or not. I saw [MENTION=4975132]sabres032[/MENTION] question on page 14 and [MENTION=1331268]santod040[/MENTION] response. So it sounds like the firmware can be flashed, I just didn't know if really needed it since I'm not on stock anymore.
[HTC Droid DNA] micahl88:
Has anyone had any luck with any form of wifi tethering from this or any other kitkat rom?

Thanks!
[HTC Droid DNA] takota6:
For sure,,gpe works sense6 and viper work,,and so do all the cyanogen alternative works..I use them all the time

Æaa\../
[HTC Droid DNA] santod040:
I think most all custom roms have some sort of tethering enabled or bypassed.

I know all of mine do.

As I said before, Verizon has blocks in place on unmodified stock roms.

Since this is intended to be pure stock, I did not implement any bypasses or mods.
[HTC Droid DNA] Imacellist:
No luck with wifi tethering on this rom, although I have been successful with usb tethering using pdanet. I paid for it awhile ago but that works well if you are willing to spend a little money on it.
[HTC Droid DNA] daydave100:
Completely upgraded, still getting update messages

I followed the instructions completely and I am successfully upgraded. However, I am still getting the "Software update ready to install" prompt constantly, and I keep pressing "Install later". Does anyone know a fix to this?
[HTC Droid DNA] Imacellist:
You flashed this ROM or did you take the update from Verizon? You shouldn't have an update via this ROM because it is on the most current version.
[HTC Droid DNA] santod040:
The only reason I could see this happening, is if the firmware was not updated as well.

If you did not update the firmware via post#2, then please do so.

This will not only make you fully current and prevent issues, but should also stop any prompts to update.
[HTC Droid DNA] daydave100:
[/COLOR]

I actually did flash the firmware. When I go to About>Software Information everything is as it should be. I'm gonna try to flash the firmware in the second post again to see if that would help.
[HTC Droid DNA] santod040:
Well, that's strange.

Becuase if everything is current, it should not be detecting any updates.

Did you get a prompt for the OTA prior to flashing this updated stock rom?

I could see where that may cause the notification to hang around still..not sure what else would be the reason for getting a notification still.

Regardless, if it doesn't go away, you can flash this and it will stop any OTA's and/or notifications from occurring.
[HTC Droid DNA] daydave100:
Well something interesting just happened. Instead of pressing Install Later I hit install now, and a error message popped up saying "Android is up to date. No changes were made." I think you were right about the notification hanging around because I postponed it before I updated. Anyways, I'm pretty sure the issue is now solved.
[HTC Droid DNA] santod040:
Yup, that was it then.. :)
[HTC Droid DNA] inspired designs 33:
flashing from cwmr

got everything running ok i think.

but trying to get my firmware all updated..

i noticed when flashing via cwmr that it says i may have lost root... fix. cancel... etc...

ideas on what that means.

if i flash my firmware using fastboot like in post 2 will i loose my stuff.... sorry ...to sound like a noob.... got to used to samsung stuff. HTC is different.

well help if yall can or have any ideas.

cheers
[HTC Droid DNA] santod040:
I would personally use twrp to flash this rom and most current kitkat based Sense roms for less issues.

I posted supersu to flash in recovery for root, in the OP right below the download.

You will not lose anything flashing the firmware or I would warn everyone to backup first.
[HTC Droid DNA] inspired designs 33:
twrp huh... ok well if i gotta. not very familiar with that recovery. ok will do the su file to flash last then...and great on not loosing my stuff...

thanks for the reply.

Hey how about a debloated version of this rom pre rooted and all... that would be sweet.? well if ya got time

thanks a million for the files and the help.

cheers
[HTC Droid DNA] Protonus:
Welcome to the future.
[HTC Droid DNA] inspired designs 33:
tether how so... i use my device as my internet for my pc. so i set it as a wifi hot spot.... works just fine.

---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------

yeah the future is nice.... so where is that twrp stuff at anyway. Getting so comfy using cmd functions instead. be nice to have just one way to do all things but guess I'm to hopeful.

---------- Post added at 12:16 AM ---------- Previous post was at 12:11 AM ----------

ok just to be sure.... how do i flash the superuser zip you included.? in cmd using adb or fastboot.... or using twrp or cwmr.... just to clarify, I just want to make sure i get it right.

all else is good. even flashed your no more red text fix... worked great. :)

cheers
[HTC Droid DNA] santod040:
It's just a recovery flashable zip.

Just flash it in Recovery like you would a rom or other flashable theme/mod.
[HTC Droid DNA] inspired designs 33:
ok sounds good thanks much

cheers
[HTC Droid DNA] anandandrade:
How To Install Using TWRP

My Droid DNA is rooted / s-off also current firmware version is 3.06***** . I have downloaded both the attached files. Now please tell me how to install using TWRP!!!
[HTC Droid DNA] daydave100:
Flash the big zip file using TWRP first, then follow the instructions in the second post with the small zip.
[HTC Droid DNA] rajkumard:
Sense 6 vs Send 5.5

Is there any specific advantage/fixes of using this rom over NuSenseSix rom, except for this being the official version for the DNA.
[HTC Droid DNA] wowbro:
Where is "Place the zip in your fastboot/adb directory on your computer."?

When I try the Commands in terminal mac I get "command not found"

I have never rooted before or did anything like this but I just want the new kitkat and I am not getting it via OTA. So any help would be nice I tried to find info on this site but had no luck. If you could link me to a tutorial I am sure I can follow thanks. Also no noob jokes that only u think are funny lol
[HTC Droid DNA] rajuabju:
Just flashed the firmware+radio from post#2

My baseband now shows correctly as 1.02.01.0207

But build number still shows as 1.54.401.5 .... I thought that would change to 4.09? or is it cause I'm running Viper?
[HTC Droid DNA] santod040:
Build number shows the build number of the rom you are on.

Only difference you will see from flashing firmware, is the hboot version and baseband version.

The rest of the changes are non-visible.

So yes, it's because you are running Viper, which is based on Sense 6 Release Keys: 1.54.401.5 just like my Sense 6 rom is, as is noted in the thread title of mine as well.
[HTC Droid DNA] nycqns983:
Hey Guys,

I am trying to flash the firmware and radios... when trying to flash it in adb, I get this error:

"<bootloader> [ERR] Command error !!!"

I get the error when entering this command: "fastboot oem rebootRUU"

Anyone else having this issue?

---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------

If it makes a difference, I am running the newest Viper rom with TWRP installed
[HTC Droid DNA] Imacellist:
First of all are you in fastboot mode? If not load into the bootloader (hold down power and vol down until a white screen with text in many different colors pops up), use volume keys to go up and down to select fastboot, then press power on fastboot.

Once in fastboot make sure your computer sees your device by typing fastboot devices. If your device doesn't show up with its' serial number then there is a driver issue.

Although it is always good to give all info, in this case the rom you are on should have no effect.
[HTC Droid DNA] nycqns983:
Thanks man but I was in fastboot and made sure to check that my device was being seen....

Yeah, I didnt think that the rom would matter but it never hurts to make sure haha

Has anyone else seen this error? I am at a loss right now
[HTC Droid DNA] santod040:
I think you need to paste your input and output here for further advice.

I am not sure if you are doing the process correctly or not, so it's hard to say why you are getting errors.
[HTC Droid DNA] Imacellist:
Try making sure you have the current fastboot version. I've had issues in the past where I had older adb and fastboot versions and nothing worked until I updated. If it has been awhile since you have done adb/fastboot try updating. I used this to update before I do adb and fastboot stuff. Give it a shot. http://xdaforums.com/showthread.php?t=2588979
[HTC Droid DNA] santod040:
If you are just stuck trying to get to fastboot, you can do that manually using power and volume down...
[HTC Droid DNA] nycqns983:
I wish that was my problem haha I get this issue while already IN fastboot

---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------

Here you go:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jim>fastboot devices

FA2BVS501382 fastboot

C:\Users\Jim>fastboot oem rebootRRU

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.011s]

finished. total time: 0.012s

C:\Users\Jim>

C:\Users\Jim>

EDIT: I also tried going straight to flashing the zip and this happened:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jim>fastboot devices

FA2BVS501382 fastboot

C:\Users\Jim>fastboot oem rebootRRU

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.011s]

finished. total time: 0.012s

C:\Users\Jim>

C:\Users\Jim>cd desktop

C:\Users\Jim\Desktop>fastboot flash zip firmware.zip

sending 'zip' (22562 KB)...

OKAY [ 1.963s]

writing 'zip'...

FAILED (remote: not allowed)

finished. total time: 1.997s

C:\Users\Jim\Desktop>

---------- Post added at 08:18 PM ---------- Previous post was at 08:17 PM ----------

[/COLOR]

Thanks man, that was my first thought too...unfortunately it didn't help :(
[HTC Droid DNA] santod040:
Try: C:\Users\Jim>fastboot oem rebootRUU

instead of: C:\Users\Jim>fastboot oem rebootRRU
[HTC Droid DNA] nycqns983:
Holy Crap....its like its the first time I have done this or something! ... I think my fiance is right...I need new glasses

---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------

Thanks for all of your help in overcoming my own stupidity everyone!
[HTC Droid DNA] santod040:
Haha, no worries man, glad you got it sorted out. :good:
[HTC Droid DNA] famouscollin:
so every time i try to fastboot flash the firmware radio zip my cmd prompt tells me it cannot open the file? its been a while using fastboot but i still remembeer how but i cant seem to find the solution to the problem im runnin in to.. why wouldnt fastboot be able to open the file?

EDIT: updating android sdk seeing if that helps
[HTC Droid DNA] inspired designs 33:
I found that if it sees your zip as a non OEM zip it cant or wont open the file... I had to flash mine in recovery ( CWMR or TWRP ( TWRP is recommended )) and doing it that way fixed my issue.

have you tried to flash the file in recovery at all.?

hope that helps.... worked for me as i was having the same problem.

cheers
[HTC Droid DNA] famouscollin:
It was a silly problem, I forgot on win8 you don't need to rename to ******.zip. cuz it is a zip file it's as if it's implied.. so as pur the instructions in post 2 if your on win7/8 it would be fastboot flash zip firmware.zip.zip (assuming you renamed to firmware.zip)
[HTC Droid DNA] Imacellist:
No the instructions are correct. It depends on your settings in windows though. You can have windows show the extensions and therefore let you edit them.
[HTC Droid DNA] goinflyn:
Any chance of adding a WiFi tether mod to the stock Rom? That's all most of us would be looking for. Then it's the complete package. Thanks again for all your work.
[HTC Droid DNA] terrorist96:
Can anyone help me with installing this rom? I've tried reaching out for help previously with no luck.

http://xdaforums.com/showthread.php?p=52422229
[HTC Droid DNA] Imacellist:
You can install the rom without flashing the firmware. Have you flashed it and are just trying to flash the firmware?
[HTC Droid DNA] terrorist96:
No, I haven't tried just installing it from the internal memory via twrp. I figured ADB was a requirement for this.

I'll try though.
[HTC Droid DNA] Imacellist:
It is 2 separate things. The ROM you flash with twrp, the firmware you flash with fastboot. Make sure you use a good cable and not a cheap one. I've had issues with bad cables and using adb.

---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------

The next thing is to make sure you have the latest adb and fastboot. I posted a link a bit ago for an updater. Put your phone is fastboot mode and then use the fastboot commands.
[HTC Droid DNA] terrorist96:
I have tried multiple cables and computers. BRB, flashing
[HTC Droid DNA] terrorist96:
I successfully flashed the kitkat rom but I did lose root. I tried flashing the zip and fixed it. Now I'm in fastboot and "adb devices" doesn't show any devices connected.
[HTC Droid DNA] santod040:
In fastboot, you would do fastboot devices, not adb
[HTC Droid DNA] terrorist96:
Nothing happens. I don't wanna clog this thread with troubleshooting. Can we discuss further elsewhere?
[HTC Droid DNA] santod040:
Yeah just pick a related thread in the Q&A or make a new one if you feel you need to, and I'm sure myself and others will try and help assist.
[HTC Droid DNA] terrorist96:
Already have. Linked to it in my post above.
[HTC Droid DNA] d08speed3:
I am having some trouble with my phone sticking at the white HTC screen and it bootloops on it. Is this a kitkat firmware issue? Can I flash the JellyBean firmware back? This firmware has a boot.img? What would that do? I've never have this happen so much since flashing the kitkat firmware zip. I just reflashed it and after a few reboots it does it again. I have to tap the power button when powering on and that sometimes work.
[HTC Droid DNA] santod040:
Maybe you need to reflash it?

Did it prompt you to reflush the firmware a second time when you did it, like I have in the guide?

Did you do that and apply the flash command a second time?

I haven't had any issues, so I can't really say what's going on with yours or why you would be having issues.

Could be an issue with the rom/kernel you are using...

You can always revert the firmware if you want, but I can't promise that kitkat is gonna work fully, especially audio stuff using JB firmware with the newer libs and kernels.

The firmware that contains a boot.img, well it has a boot.img(ramdisk and kernel)

So if you flash that, you'll wanna reflash a rom after, so that the rom you want to run, loads its kernel.

In other words, if you try and use a JB kernel on Kitak it will bootloop.

So if you are on kitkat now and flash JB firmware with a JB stock secure kernel, you aren't going to boot until you reflash your rom.
[HTC Droid DNA] d08speed3:
Yea I followed your guide. Just flashed Jamie's prior kernel and testing now.

Seems kernel related.... thanks

HTC DNA
[HTC Droid DNA] theseabass:
Jamie's kernel won't work, its an AOSP kernel. You'll need a sense kernel.
[HTC Droid DNA] d08speed3:
I know that. I posted about firmware issues. It was kernel problems in the end. Sorry

HTC DNA
[HTC Droid DNA] pyroguysf:
For anyone experiencing the touchscreen and/or back button issues, I returned to full stock S-On and took the OTA, where I no longer experienced the sensitivity issues with the official update. I easily re-unlocked with weaksuace + firewater, clean flashed this ROM just as before, however, everything was still working properly with no sensitivity issues seen previously.

[MENTION=1331268]santod040[/MENTION] Previously, the touchscreen issues were only present after upgrading with your firmware while running the new 4.4 kernel (I didn't try the new kernel with previous firmware), so could there be a conflict with the firmware? Since the update came in 2 parts, and the first was ~18MB (close to the size of the firmware), might there be different versions of the firmware for different internals or something of the sort? That's just my hypothesis, and I didn't save either of the OTA zips, but I could pull the firmware off my device for comparison, if that's possible.
[HTC Droid DNA] santod040:
There is not different versions of the firmware.

Yes there were two updates.

The pre-update and the actual update.

Flashing the firmware I posted as well as the Rom, is essentially the same as what you did.

I can't say why you or anyone else had issues or is having issues.

What I can say, is I've only posted what firmware Vzw and HTC gave us, it's not something I've created myself and has worked just fine for me and many others.

If relocking made things better for you, then that's great.

But I personally don't see any benefit in doing so.

I've never relocked a device or gone back to S-on for any update purposes and have never had any issues either.

You also didn't say if you were on this stock Rom with touch issues or another Rom.

It does make a difference...But I'm not really trying to fish for more info, as I think this is all somewhat irrelevant.
[HTC Droid DNA] waxta:
I am experiencing the touch screen and button issues with the new kitkat kernel as well. Will I be able to take the OTA when I go back to stock and s-on if I am running on AT&T/GSM?

Edit: I have flashed new firmware/radio in various combinations. Everything but go back to stock.
[HTC Droid DNA] santod040:
Running the kitkat firmware with what? Why various combinations of flashing it?

If you aren't running the firmware with the stock rom, then this is posted in the wrong thread.

If the firmware is incompatible with a custom rom, then the dev of that rom should be made aware of it.

If you are running this stock rom and the firmware that is meant for it, then I don't know what to tell you.

It works fine for me on this and the rest of my roms, no touch issues whatsoever.

Almost forgot to answer your other question, no you won't be able to take a Vzw OTA on another network...

There is no need to go back to s-on to take an OTA anyways, not sure who started that theory...but it's a waste of time.

You can take an OTA while s-off and unlocked.

You can also flash a stock rom and stock recovery and flash the OTApkg's I posted in General which is the same effect the OTA would have, as well as simply flashing the firmware and stock rooted rom I posted.

It's all the same.....
[HTC Droid DNA] pyroguysf:
Not trying to get into an argument, but when the touchscreen doesn't properly work on a smartphone after an official software update, I don't think that discussion to try and solve the problem is irrelevant, as I think it can only help others solve the problem, even if it's just a small subset of people. It happened on any 4.4 Sense ROM, regardless of the Sense version, as long as the new official unmodified (or modified) kernel was used. I do agree that completely reverting to stock just to re-exploit a device is pointless 99% of the time, but it can solve an odd issue occasionally. I believe you 100% when you say you posted the unmodified firmware you got from official sources. I don't try to pretend I'm a dev, but seeing as running the same stock kernel and ROM combo previously caused an issue, whereas the issue is now no longer present, isn't the firmware the only other source (or at least most likely source) of the problem? Hypothetically, based on different internals identified by serial number, they could've pushed more than one version of the firmware, and I was just wondering if there's a way to check if mine was different.

Either way, I'm just saying that despite flashing as much of the unmodified stock update files as are available in these forums, more than just a couple people have had sensitivity issues with the new software. On the other hand, taking the update direct from official sources was for whatever unknown reason different and didn't give me the sensitivity issue running the same kernel and ROM. I was just offering to help look in to the cause of problem, but failing that, I'm just conveying a solution to the others with the same issue.