• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root DNA stuck in ruu mode

C

CSMGHTCDNA

Newbie
I believe i have bricked my htc dna. Its stuck on a black htc screen with triangles in each corner. I cant access recovery are anything for that matter. This all started when i flashed a custom rom called "clockworkmod" which i flashed successfully. I noticed after i flashed it that there was 13gb of space being calculated in my "other" field when i went to see my storage info. I then researched and found out that the clockworkmod was some how duplicating the operating system and thats the reason why the "other" field was showing over 13gb. I then flashed another custom rom to attempt to fix this issue called "twrp" this flash also was successful but the issue wasnt fixed, so out of stupidity and lack of knowledge i then went into twrp and choose to wipe data not knowing that this would totally wipe my entire operating system. Now i was at a point were i couldnt do anything but load into bootloader( s-0ff and unlocked) and also recovery (twrp) so then i started digging in deeper and found out i could flash the factory rom via ruu (if i could find one for 4.4.2 kit kat) which i was unable to do for days. Then i finally found a factory rom for 4.4.2 kit kat but it didnt have the boot image. So when i flashed it i got the black htc screen and the status bar would fill all the way up and that was it....it would never move off of that screen. So i found out that there wasnt a full factory rom available for the 4.4.2 kit kat with the boot image. So once again out of stupidity and lack of knowledge i thought i was using common sense by taking one of my multiple boot image zip files and dragging it into the zip file of the rom that didnt have the boot image( i thought that was logical) which i guess it wasnt because now i cant even get into bootloader or recovery and my cpu wont detect my phone i cant do any command prompts are anything. What can i do? Is this considered a "bricked phone"? Can anyone help me?
 
CSMGHTCDNA said:
I believe i have bricked my htc dna. Its stuck on a black htc screen with triangles in each corner. I cant access recovery are anything for that matter. This all started when i flashed a custom rom called "clockworkmod" which i flashed successfully. I noticed after i flashed it that there was 13gb of space being calculated in my "other" field when i went to see my storage info. I then researched and found out that the clockworkmod was some how duplicating the operating system and thats the reason why the "other" field was showing over 13gb. I then flashed another custom rom to attempt to fix this issue called "twrp" this flash also was successful but the issue wasnt fixed, so out of stupidity and lack of knowledge i then went into twrp and choose to wipe data not knowing that this would totally wipe my entire operating system. Now i was at a point were i couldnt do anything but load into bootloader( s-0ff and unlocked) and also recovery (twrp) so then i started digging in deeper and found out i could flash the factory rom via ruu (if i could find one for 4.4.2 kit kat) which i was unable to do for days. Then i finally found a factory rom for 4.4.2 kit kat but it didnt have the boot image. So when i flashed it i got the black htc screen and the status bar would fill all the way up and that was it....it would never move off of that screen. So i found out that there wasnt a full factory rom available for the 4.4.2 kit kat with the boot image. So once again out of stupidity and lack of knowledge i thought i was using common sense by taking one of my multiple boot image zip files and dragging it into the zip file of the rom that didnt have the boot image( i thought that was logical) which i guess it wasnt because now i cant even get into bootloader or recovery and my cpu wont detect my phone i cant do any command prompts are anything. What can i do? Is this considered a "bricked phone"? Can anyone help me?
Click to expand...

your phone is stuck in "ruu mode". you can try fastboot reboot-bootloader to get back to normal fastboot.

is your phone s off or s on?

it may help if you could enter the folowing command and paste back the info(xxx out your esn,imie):
fastboot getvar all
(the phone can be in normal fastboot or ruu mode for that command)

some links to what you have tried to flash may help as well,as well as the process you tried to use to flash them.
 
before we go any further let me say HOW MUCH I APPRECIATE YOU RESPONDING!!!! A BIG THANK YOU IS NOT EVEN ENOUGH!!!! AS OF RIGHT NOW MY PHONE IS STUCK ON A BLACK HTC SCREEN AND EACH OF THE FOUR CORNERS OF THE PHONE HAS TRIANGLES/! IN THEM, BEFORE THIS HAPPENED I WAS UNLOCKED AND S-OFF. I RECEIVED MY TOKEN VIA HTC DEV AND WAS ABLE TO SWITCH FROM S-OFF TO S-ON WHENEVER I WANTED TOO. I ALSO HAD CHANGED MY CID TO 2222222 SO.... AS OF NOW I CANT GET ANY CPU TO DETECT MY PHONE SO WHEN I OPEN A COMMAND IT JUST SAYS "WAITING FOR DEVICE"....I BELIEVE THAT STUPID THOUGHT OF TAKING THE FACTORY ROM I HAD THAT DIDNT HAVE THE BOOT IMAGE AND THEN TAKING THE BOOT IMAGE FILES I HAD AND DRAGGING THEM INTO THE FACTORY ROM ZIP FILE IS WHAT GOT ME HERE AND NOW THAT I THINK ABOUT IT I WAS PUTTING BOOT IMAGES FILES INSIDE OF THAT FACTORY ROM FILE THAT DIDNT HAVE THE BOOT IMAGE AND WHEN IT WASNT WORKING I WOULD PUT ANOTHER ONE IN THERE WITHOUT DELETING THE ONE PREVIOUS...DOES THAT MAKE SENSE? I WAS BASICALLY THINKING OK THIS ROM DOESNT HAVE THE BOOT IMAGE, BUT I HAVE MULTIPLE BOOT IMAGE FILES AND MAYBE IF I OPEN THE FACTORY ROM ZIP AND DRAG ONE OF THE BOOT IMAGES INTO IT THAT I COULD BASICALLY MAKE THE FACTORY ROM COMPLETE.....AS FAR AS THE METHOD I USED WAS A COMBINATION OF COMMAND PROMPTS AND THIS HASOON 2000 ALL IN ONE KIT..... BASICALLY I USED COMMAND PROMPTS TO FLASH THE CLOCKWORKMOD AND THEN THE TWRP AND WHEN I WIPED MY DATA AND THE OS IT SEEMED AS THOUGH MY CPU WOULDNT DETECT MY PHONE BUT I STILL HAD FASTBOOT ABILITY AND ADB AS WELL....I HAD GOT TO A POINT WHERE IT APPEARED ALL I NEEDED WAS A FULL FACTORY ROM FOR 4.4.2 KIT KAT AND IT SEEMED BASED ON MY RESEARCH THERE WASNT ANY TO DOWNLOAD THEN I FOUND THAT ONE WITHOUT THE BOOT IMAGE..... I TRIED TO FOLLOW YOUR INTRUCTIONS ON THE COMMAND AND IT JUST SAYS "WAITING FOR DEVICE"
 
for now,im going to assume that youre s on,as seperate boot image flashes are not neccessary when you are s off.

youre going to need to restore fsatboot connectivity. theres no reason it wont work,and no way to accomplish anything without it.

here are some general tips for troubleshooting:
troubleshooting connectivity issues:
*make sure you have changed to your adb/fastboot directory!
*make sure usb debugging is enabled(checkmarked) to use adb in the OS
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot(not hboot!),enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.
 
Ok im going to respond to each thing you stated in the order you stated it...first i cant do anything when it comes to making sure usb debugging is check because i dont have an operating system and now cant even access bootloader or recovery or anything for that matter. Before i got this htc screen with the triangles device manager was detecting my phone now when i connect the phone i get an error message saying "the last usb device you connected to this computer malfunctioned and windows doesnt recognize it" the recommendation is to disconnect and reconnect and if it still doesnt recognize it then the device may not be working properly. So basically it seems i cant follow any of these steps, wouldnt you agree? Or am i just ignorant to this?? IM ALSO ON WINDOWS 8.1 AND I DONT HAVE AN OLDER CPU UNFORTUNATELY AND I STAY IN THE COUNTRY SO I DONT HAVE A NEIGHBOR FOR MILES....
 
i forgot to respond to one of your statements...i was wrong when i said i was going from s-on to s-off i meant i was going from unlocked to locked bootloader not s-on and s-off i was s-off throughout this entire thing.....i know im s-off without a doubt....
 
CSMGHTCDNA said:
i forgot to respond to one of your statements...i was wrong when i said i was going from s-on to s-off i meant i was going from unlocked to locked bootloader not s-on and s-off i was s-off throughout this entire thing.....i know im s-off without a doubt....
Click to expand...

thAt is what i figured you meant. ;)

it doesnt matter if usb debug is enabled or not,you cannot use adb without a working OS or custom recovery.

windows 8.1 is notorious for fastboot prollems,and i have zero experience with it, i stuck with windows 7 becasue of all the phone issues in 8+,so unfortunately youre on your own getting it figured it out. i know there are some work arounds if you do some searching.

your other options are to obtain(borrow or purchace,there are lots of $75 andless laptops on craiglist) an older laptop to use for phone stuff,running an older,more phone friendly OS. you could also journey to a friend or relatives house and use their desktop,the files are small and unobtrusive. last option is to use linux,where drivers are not needed. you can create an ubuntu live cd and use that for phone work.

the good news,is that if youre s off,all youll need to to is run an ruu and your phone should be funtional again.you can use this one: AndroidRUU | The #1 source for Android RUU files

youll just need to get fastboot to recognize your device again :)
 
thanks again for responding and helping me... so let me get this right your saying that even though my phone is stuck on this screen that if I had windows 7 it would detect my phone? I don't understand I have htc sync manager (by the way my wife has a htc dna the same model and I plug her phone in with no issuses) so the drivers are installed and working properly on my windows 8...so we both agree that my adb isn't going to work...that ruu file is not going to work I have 4.4.2 kit kat so based on my research that ruu file is no good to me. I happen to update my firmware to 4.4.2 right before all this happended. how can I get fast boot to recognize my device again? I don't believe windows 7 would make a difference because my drivers are fine on the cpu its the device that's not working properly...right?
 
Ok i sent you a personal message so forgive me for being redundant but i realized i needed to submit to your knowledge and not combat what you were saying (not that i was trying to) but i really didnt think a win 7 cpu would help and low and behold i was wrong(of course i was wrong im the idiot that caused all this) so now i have fastboot abilities...now i just need a ruu that works on this 4.4.2 kit kat
 
CSMGHTCDNA said:
Ok i sent you a personal message so forgive me for being redundant but i realized i needed to submit to your knowledge and not combat what you were saying (not that i was trying to) but i really didnt think a win 7 cpu would help and low and behold i was wrong(of course i was wrong im the idiot that caused all this) so now i have fastboot abilities...now i just need a ruu that works on this 4.4.2 kit kat
Click to expand...

just run the one i linked above. once your phone is up and running,we can work on updating from there :)

almost forgot,you can extract rom.zip in this manner:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be renamed to PxxxIMG and flashed in hboot,from a FAT32 sd card

rom.zip can be flashed in this manner:
if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides :))

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

you can also try simply running the .exe file
 
Correct me if im wrong but the first list of steps wont work for me because the steps include me having the ability of using a sd card which the htc dna doesnt take sd card and the second list of steps wont work because im not working on an operational phone.....
 
That link says could not connect...too many connections as well....plus i heard 4.4.2 kit kat makes it where you cant go backwards to an earlier version....please research and confrim.....because i know ive tried that same exe file from the same source you provided....
 
CSMGHTCDNA said:
Correct me if im wrong but the first list of steps wont work for me because the steps include me having the ability of using a sd card which the htc dna doesnt take sd card and the second list of steps wont work because im not working on an operational phone.....
Click to expand...

Correct,you are wrong ;) the directions were written a long time ago,when most phones had an sd card. But rest assured,it does not affect the ability to extract rom.zip. this process is done entirely on your pc. Just ignore the sd card reference.
 
CSMGHTCDNA said:
That link says could not connect...too many connections as well....plus i heard 4.4.2 kit kat makes it where you cant go backwards to an earlier version....please research and confrim.....because i know ive tried that same exe file from the same source you provided....
Click to expand...

You heard wrong. When you're s off,there are no security checks,you can install any version that you wish. If the ruu failed,there were other reasons,and it has nothing to do with kit Kat.

What you need to do is follow the directions,and post a copy of your entire cmd window if you have any errors.

Again,if you are truly s off,the linked ruu will work fine.
 
PS,you still have not done these things:

scotty85 said:
it may help if you could enter the folowing command and paste back the info(xxx out your esn,imie):
fastboot getvar all
(the phone can be in normal fastboot or ruu mode for that command)

some links to what you have tried to flash may help as well,as well as the process you tried to use to flash them.
Click to expand...
 
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.02.01.0207
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: 22222222
(bootloader) battery-status: good
(bootloader) battery-voltage: 4008mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.092s

C:\adb>
 
Excellent. The linked ruu will work fine. :)

Have you tried:

Fastboot reboot-bootloader

?

That should get you back to Norma fastboot.
 
thank you so much again....but yes ive tried but it just goes back to that same screen with the four triangles was going to attach a pic of the screen but i dont know how....here is the cmd window after doing it....


C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s

C:\adb>
 
1
 
CSMGHTCDNA said:
ive tried that still says could not connect. too many connections. and did you see that i cant get to the bootloader screen?
Click to expand...

Yes,the fact that you are stuck in ruu mode is not a big deal to run an ruu.

May be an issue with the site. I think I have it downloaded,when I get back to my pc I can upload it if its still not working.
 
ok sorry for being redundant....i dont want to frustrate you....yeah that site worked the other day...what i dont understamd is before i got stuck in ruu mode i tried that same link and it didnt work....i dont know i will be up waiting for you...ty again...
 
You must log in or register to reply here.
Back
Top Bottom