Root [guide] unlock droid dna

[scotty85]

Read This:
the following is outdated,and no longer works on newer firmwares. there is an s off method wich will turn the radio secure flag off,and install a modified hboot,giving the equivalent of unlock.

what you will need to do is:
1)run the moonshine s off tool
2)jump to the second post,download the files,but skip step one since moonshine gives you a nice patched hboot.just follow steps 2 and 3 to install a recovery and flash superuser root files.

again,the following is outdated. left for now,for nostalgia
_________________________________________________________________
this is gonna be a quick and dirty guide,ill try and make it "noob friendly" later

the htc droid DNA for verizon is not officially supported by htcdev(thanks vzw ) so some trickery is needed to change the CID of the device,allowing htcdevs bootloader unlock to work


download these files
-install drivers from revolutionary: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (download and run as admisitrator)
-download miniadb_v1031.zip wich contains the newest availble adb(aka "modern" adb referenced by jcase in original guide. supports backup/restore)

*carefully follow directions to change the carrier identification(CID) of your phone:
http://forum.xda-developers.com/showthread.php?t=2109862

there are a couple different ways to install an app on your phone. easiest is to:
-make sure "unknown sources" is checked in settings/security
-transfer the apk file to your internal sd
-use any file manager(for example astro file manager) to find the app,and install it.

verify superCID and prepair to root
*this will verify that the CID app worked to change the CID of the phone,and also get files set up and ready to procede to htcdev unlock.
-extract miniadb_v1031 and transfer the unzipped to the root of your C drive. you might consider changing the name to "miniadb_dna"
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_dna directory. type the following at the prompt in your cmd window:

cd c:\miniadb_dna

your command promt should change to "c:miniadb_dna>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("miniadb_dna" in this case)

-now make sure usb debugging is checked in settings/developer options,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices
(if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.)

adb reboot bootloader
(will boot phone to fastboot)

fastboot devices
(will return serial number. again,if PC starts installing drivers,wait until its finished)

fastboot oem readcid
(should return 11111111)

fastboot reboot
(will reboot the phone back to the OS)

unlock with htcdev,install recovery,flash superuser root files in recovery with directions in second post

holler if you have questions

 

[scotty85]

the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files

before you start,go ahead and download these files:
-twrp recovery: TWRP 2.3.2.0 for HTC Droid DNA - Droid DNA Development - RootzWiki
-superuser files: latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account



1)unlock with htcdev

Spoiler

most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier

1)prepair ADB
-use miniadb_dna folder from above. (this was originally a rezound guide,sodirections from here forward will assume this folder to be named "mini-adb_vigor",as an example. substitute "miniadb_dna" in place of "miniadb_vigor" when you see that command)
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_vigor

your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)

-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your "other supported devices" from the "select your device bar" and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty

-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:

adb reboot bootloader

it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:

fastboot devices

again,this should return your phones serial number.

-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :

fastboot oem get_identifier_token

-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:

fastboot flash unlocktoken Unlock_code.bin

-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal

as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]


c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [  0.069s]
finished. total time: 0.070s

c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.011s]
finished. total time: 0.156s

c:mini-adb_vigor>

2)flash a recovery

Spoiler

if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.

once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:

1)temporary recovery:

Spoiler

-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. **

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

in your command window you will see(red are my inputs):

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
        downloading 'boot.img'... OKAY [  1.518s]
                       booting... OKAY [  0.005s]
finished. total time: 1.523s

2)permanently install your recovery

Spoiler

-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. **

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-permanently flash your recovery to phones recovery partition:

fastboot flash recovery <recoveryname>.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.

*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.

and the code(again,red my inputs):

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
  sending 'recovery' (7074 KB)... OKAY [  1.659s]
            writing 'recovery'... OKAY [  5.179s]
finished. total time: 6.840s

3)flash superuser root files*

Spoiler

there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot

*congratulations,youre rooted

if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

s-off is better,and worth whatever extra efforts to achieve if available.

*hope it helps,holler if you have questions

donate to my device fund

 

[scotty85]

this is a replication of my post in the rezound forum. now that the dna has htcdev unlock,this info will apply. keep in mind we may not be able to take full advantage of it if roms may not scripted for the recovery to flash the boot image. we didnt really get to reap the full benefits until s-off was achieved,and rom devs again started scripting the roms for recovery boot install.


if you have not rooted yet, consider using the guide here,as ive tried to eliminate some of the confusion from htcdev's page,and using it will give you some basic knowledge and tools that you will use in happily modding your s-on device. youll also potentially have an understanding of fastboot booting your recovery into phone memory,as it is the same thing as what the guide instructions are for a "temporary recovery".

most folks that have come from other devices are used to the following sequence of events:
1)root phone
2)install a custom recovery(generally clockwork mod,or Amon_Ra)
3)booting to that recovery to make and restore backups,flash roms,etc. since the root method generally gave access to all the phones different memory partitions,many of wich are modifiable via the custom recovery.

even worse,are folks who have come from different devices and used an app called "rom manager" to manipulate things from within the booted operating system. i am not a fan of rom manager period,even on phones that it works on.

unfortunately,the above is a recipe for disaster on any s-on,high end htc device.

to begin,
a few words about htcdev

Spoiler

htcdev is htc's answer to the publics cry for unlocked bootloaders,and the ability to modify and install custom operating systems on their htc devices.

basically,you send information to htc,and they provide an unlock token that is reusable,but unique to your device. this changes the locked lettering at the top of your hboot screen to unlocked,and gives you access to the /boot,/system,and /recovery partitions only of your phone. it is not s-off by any means,and there are still alot of checks being done by the phone,wich lead to disadvantages. most notably,you cannot change any other partitions. hboot,radios,and splash screens are protected and off limits. you also cannot roll backwards in software build numbers and firmware if you flash a leaked rom and dont like it.

there are a couple of advantages.

1)unlike the underground exploits used in the past,htcdev will always work. you dont need to worry about unrooting and not being able to root again. if you need to relock your bootloader and flash factory firmware,you will always be able to re-unlock with your original unlock token.

this makes it convenient for users that only want root access so that they can run a few root apps(titanium backup,wifi tether) and delete some bloatware. the folks that like to run stock,and recieve OTA updates can easily do so by keeping the STOCK recovery on the phone.

as long as the stock recovery is in place,you are not in danger of an OTA messing up your phone.

rezound user: but,wait! wont accepting an OTA break my root?!
scotty: yes,but thats not a big deal. after the OTA has finished,you can quite easily relaunch your temporary recovery,and re-flash your root files,just as you did when you first rooted. re-rooting is easily accomplished,and therefore nothing to be concerned with.

2)the other big advantage of an htcdev unlocked s-on bootloader,is that since the bootloader is protecting itself,and the radios,it is nearly impossible to hard-brick(i.e.,unrecoverable) device with software flashes. any damaged to the phones filesystem are almost always fixed by RELOCKING the bootloader,and running an RUU(factory signed software package)

modding your s-on,unlocked device
first and foremost,remember this:
**an htcdev unlocked phone CANNOT write to the /boot partition FROM its /recovery partition.**

Spoiler

what this means is that,unlike your s-off evo 4g,thunderbolt,inc 1,or just about any other htc device you may have messed with,the rom that you flash from a recovery that is permantly installed on your phone cannot install the boot image. since the boot image houses the kernel, the roms kernel is not being installed along with the rest of the rom.

this means that if your rom requires a different kernel than what is on your phone,it will not boot. it will hang indefinately at the splash screen.

there are a couple options to work around this handicap with s-on phones:

1)flash the kernel manually. it can be done with the command fastboot flash boot or it can be done by placing the boot image inside a PH98IMG file and flashing it in hboot.

PH98IMG flashing is a PITA on an s-on phone,in my honest opinion. the information on the "android info" text document inside the file must contain the correct info or the phone will not let the file flash. this leads to much aggravation,confusion,and an overall very bad rom flashing experience

therefore,the better way to flash kernels,IF you want to do it manually,is to use the fastboot flash boot command. more info on that here: http://androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html#post3933400

and now the best for last:
2) fastboot boot your recovery into phone memory

this involves,basically,placing your recovery image inside the folder that contains adb and fastboot,booting the phone to fastboot,and the launching recovery into phone memory by entering the command:
fastboot boot recoveryname.img

do not confuse this with the fastboot flash command.

fastboot boot is taking an image,and booting it right up on the phone.

fastboot flash is permantly installing an image into the phones filesystem.

*if you use fastboot boot to launch your recovery into phone memory,then recovery CAN write to the boot partition,making rom flashing on your s-on device just like rom flashing on an s-off device.

i.e.,launching recovery from fastboot lets the rom install the kernel,and requires no seperate kernel flashing. this means that when you are following a rom developers install instructions,you can follow the set for s-off devices.

why does this work?!

well,an oversimplified explanation is this:
-fastboot is part of the bootloader,wich can write to the /boot partition
-launching recovery from bootloader,makes the recoverys operations work thru the bootloader.
-hence,launched recovery can write boot image. hooray! :smokingsomb:

all the above applies to bakcups as well. you canot restore a backup from the permenent recovery if it contains a different kernel. just like flashing a rom. all the above info in this post applies to restoring a rom as well.

some more detailed instructions

Spoiler

if you rooted with my guide,then you have seen this before. its basically the directions to "temporarily flash recovery"

for those that have rooted via other means,you can modify these directions to fit whatever folder you have adb/fastboot in,or you just use these directions:

download these files:
-mini-adb.zip: mini-adb.zip
-the latest recovery image for whatever recovery you are using.

first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (i recomand revolutionary drivers)

1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C\ drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. rename it to "mini-adb_vigor" since youll be putting some vigor(rezound) specific files in here. you actually can call it whatver you want,but directions from here forward will assume this folder to be named "mini-adb_vigor"
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_vigor


2)launch a temporary recovery:
-move the image file you downloaded above for amon RA and place it into the mini-adb_vigor folder.

-type in your cmd window,or copy/paste the commands that are in bold

-check the md5 of your recovery image:

md5sums <recoveryname>.img

i.e.,if youre using an image named recovery-twrp,then your command will be:
md5sums recovery-twrp.img

**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **

-enable usb debugging on your phone and plug it in,charge only mode.

-check for connectivity:

adb devices

-it should reply with your serial number. if so,then:

adb reboot bootloader

-this will boot your phone into "fastboot" wich is a white screen with coloered letters.

-check for connectivity:

fastboot devices

-should return serial number

-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

example:
fastboot boot recovery-twrp.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

now that youre recovery is running,you have lots of options. you can mount usb storage to move things on and off the sd card if you need to.

note that once recovery is running,you can unplug from the PC if you want to flash your rom from the couch,ktichen table,or wherever

you can now restore a backup,or flash a rom.

last and not least,a couple notes:
-to paste into the cmd window,you must right click/paste. you cannot control/v
-to copy from the cmd window,right click. click mark. highlight everything to copy in white. now hit enter,or right click again.

holler if you have more questions

 

[scotty85]

this is just for folks that like adb and want a more complex method than installing an app and running it.

jcases original root/supercid guide

Spoiler

this is gonna be a quick and dirty guide,ill try and make it "noob friendly" later

the htc droid DNA for verizon is not officially supported by htcdev(thanks vzw ) so some trickery is needed to change the CID of the device,allowing htcdevs bootloader unlock to work

refer to this thread:
[Exclusive] How To: Unlock The Droid DNA's Bootloader

download these files
-backup.ab and DNA_TeamAndIRC.zip from the link above
-install drivers from revolutionary: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (download and run as admisitrator)
-download miniadb_v1031.zip wich contains the newest availble adb(aka "modern" adb referenced by jcase. supports backup/restore)

prepair to root
-extract miniadb_v1031 and transfer the unzipped to the root of your C drive. you might consider changing the name to "miniadb_dna"
-extract DNA_TeamAndIRC.zip. put runme.sh, CIDGen.apk, and backup.ab into miniadb_dna
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_dna directory. type the following at the prompt in your cmd window:

cd c:\miniadb_dna

your command promt should change to "c:miniadb_dna>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("miniadb_dna" in this case)

-now make sure usb debugging is checked in settings/developer options,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

*carefully follow directions
at [Exclusive] How To: Unlock The Droid DNA's Bootloader

unlock with htcdev,install recovery,flash superuser root files in recovery with directions in second post

holler if you have questions

again,this is out of date- most folks should use post 1

 

[Randino]

This scares me.... lol everything was much easier in the old incredible days... And then I got the Nexus, and got spoiled and lazy. I'll have to actually follow directions closely with the DNA.

 

[caneaddict]

with the bootloader unlocked, how likely is it that we will get stable AOSP within the next few months?

 

[scotty85]

it is likely,but all vzw LTE devices are slow for AOSP development becasue the radios are complex and RIL is to figure out. just to get it booting and working on the device isnt so bad,but working with working data,calls,bluetooth,gps,etc. is another story.

as an example,cm10 is well underway for most devices and the rezound still doesnt have 100% working cm9

 

[caneaddict]

it is likely,but all vzw LTE devices are slow for AOSP development becasue the radios are complex and RIL is to figure out. just to get it booting and working on the device isnt so bad,but working with working data,calls,bluetooth,gps,etc. is another story.

as an example,cm10 is well underway for most devices and the rezound still doesnt have 100% working cm9

Thank u, very helpful reply . looks like I'll be going nexus 4 on art and just change phones when the next nexus gets lte

 

[beyond_the_veil]

This scares me.... lol everything was much easier in the old incredible days... And then I got the Nexus, and got spoiled and lazy. I'll have to actually follow directions closely with the DNA.

Seriously...I went straight from the old Dinc to the DNA. I feel like I need to sign up for classes or something

 

[scotty85]

for those wishing the method was a little easier, OP updated. make sure to thanks beaups on xda,and consider donating to his recomendations

 

[jordie9]

thanks would like an update.

 

[scotty85]

thanks would like an update.

what would you like an update on?

 

[Cuoficr]

Moonshine installs SuperSU when it does its little bootleg... Not sure about the recovery.img. Only my second attempt at rooting (which works great, thanks for the info) First with an HTC One V, and now my Droid DNA, not sure if I'll run any custom ROMs ornot, but the bloatware aggrevates me to no end.

Any recomended to check out?

 

[Cuoficr]

Ok, so first off I'm idiot... that being said... I'm pretty sure I flashed the wrong recovery, phone works fine, loads etc etc, but when I went into recovery this mornng it just hangs on the loading recovery splash screen..... Do I just wait for the battery to die and flash the right recovery???
Secondly... I d/l from the twrp recovery link in guide, and unzip, but no .img file?

 

[Lykarsis]

Ok, so first off I'm idiot... that being said... I'm pretty sure I flashed the wrong recovery, phone works fine, loads etc etc, but when I went into recovery this mornng it just hangs on the loading recovery splash screen..... Do I just wait for the battery to die and flash the right recovery???
Secondly... I d/l from the twrp recovery link in guide, and unzip, but no .img file?

First of all, on the DNA, you can restart the device by holding the power button until the buttons on the bottom flash 15 or 16 times.

Second, if you want to install TWRP, easiest way by far is to download goo im from the play store and install it from there (it will ask if you want to install an openrecovery script. Hit yes and you're gold.

 

[Cuoficr]

First of all, on the DNA, you can restart the device by holding the power button until the buttons on the bottom flash 15 or 16 times.

Second, if you want to install TWRP, easiest way by far is to download goo im from the play store and install it from there (it will ask if you want to install an openrecovery script. Hit yes and you're gold.

Got it straightened out thanks.

 

[CoyotesFan4Evr]

So, I did the custom recovery method mentioned by downloading Goo and telling it to install one for me. I was nervous about doing it at first because I really just wanted to do the temporary version but I couldn't figure out where I needed to put the file and the like. Mostly that comes with my lack of coding knowledge.

I post this to assure any future issues someone might have with wanting to have custom recovery. I may not know everything but I want to help where I feel I can.

Now I just have to figure out what Rom to flash. I'm torn at the moment but I'm sure I'll figure it out in the end.