Related
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
squeezyb said:
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
Did you relock the boot loader?
Sent from my DROID RAZR using Tapatalk 2
yes i did
squeezyb said:
yes i did
Click to expand...
Click to collapse
More info would help like what errors you are getting
Sent from my DROID RAZR using Tapatalk 2
adb wont even find my device, so i am not getting any errors. is there a working RUU i can rename to PJ53IMG, and flash that through the bootloader?
http://forum.xda-developers.com/showthread.php?p=28723878
Sent from my DROID RAZR using Tapatalk 2
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
i know this is something simple that i can flash, but it is not working
squeezyb said:
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
Click to expand...
Click to collapse
Either should work but try the other
Sent from my DROID RAZR using Tapatalk 2
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupted on my end
squeezyb said:
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupt
Click to expand...
Click to collapse
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Have you tried the recovery? Check to see if that works. If not try to fastboot a recovery. The command is "Fastboot flash recovery". Try with TWRP. If that takes then try to flash a ROM with that.
blazingwolf said:
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Click to expand...
Click to collapse
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
On my side ill say do what the ther said, if you still have supercid you can unlock device and flash recovery and flash a working rom if you want it booteable
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
squeezyb said:
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
Click to expand...
Click to collapse
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
blazingwolf said:
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
Click to expand...
Click to collapse
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Great to hear.
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
No truer words are spoken
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yep. And somehow time stands still for an eternity until something happens to let you know its alive.
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
prairiedogn said:
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
look here: http://forum.xda-developers.com/showthread.php?t=1435228
Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
jdawg0024 said:
Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Click to expand...
Click to collapse
this is basicly an RUU rite? i wish there was a fix for the prox sensor.. im sensor is all f ed up since jelly bean dropped
Weird, is this widespread? I didn't have any issues with stock or custom (Pacman) ROM I am using now.
Sent from my EVO using xda app-developers app
happens to me, when i call some one the screen goes black, and i can turn it on with the power button but when i put it up to my ear it goes black again and doesnt come on when i move it away as its supposed to
evo401 said:
this is basicly an RUU rite? i wish there was a fix for the prox sensor.. im sensor is all f ed up since jelly bean dropped
Click to expand...
Click to collapse
Yes this is like the RUU except you put this file on the ROOT of your SD card and boot into HBOOT and it will reflash the ROM.. This is for STOCK UNROOTED phones.
waterbound said:
Weird, is this widespread? I didn't have any issues with stock or custom (Pacman) ROM I am using now.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
pacman rom is aosp
not sense
lol
jdawg0024 said:
Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Click to expand...
Click to collapse
Great post man. I am not having luck with ruu. It will be great if you post MD5 to confirm the download.
djisia87 said:
Great post man. I am not having luck with ruu. It will be great if you post MD5 to confirm the download.
Click to expand...
Click to collapse
Not sure how to make one of those as I didn't get one from HTC
Sent from my EVO using xda app-developers app
I'm gonna try this. I've been having a serious bug with my phone where it essentially will stop responding to touch. If I do a simpull it starts working again but it'll stop soon after. Done factory resets, cache wipes, etc. Now I'll have to try this just in case. (I already have a new phone ordered on its way but I might as well cover all my bases)
So this is just the totally stock software from HTC and I don't need a root or an unlocked bootloader or anything? Cuz I haven't done any of that.
MrSteez said:
I'm gonna try this. I've been having a serious bug with my phone where it essentially will stop responding to touch. If I do a simpull it starts working again but it'll stop soon after. Done factory resets, cache wipes, etc. Now I'll have to try this just in case. (I already have a new phone ordered on its way but I might as well cover all my bases)
So this is just the totally stock software from HTC and I don't need a root or an unlocked bootloader or anything? Cuz I haven't done any of that.
Click to expand...
Click to collapse
This is the stock Factory image
Sent from my EVO using xda app-developers app
jdawg0024 said:
This is the stock Factory image
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Alright well I tried it and it didn't fix my problem anyways. Replacement's on its way!
MrSteez said:
Alright well I tried it and it didn't fix my problem anyways. Replacement's on its way!
Click to expand...
Click to collapse
mine said signiture failed. Can anyone advise
nextlevel_44 said:
mine said signiture failed. Can anyone advise
Click to expand...
Click to collapse
Try redownloading it..
jdawg0024 said:
Try redownloading it..
Click to expand...
Click to collapse
I did. I am on hboot 2.09.0000 radio 1.05.11.0606 stock recovery and relocked if that helps at all. I have tried running the JB ruu and it takes about 3 min but my phone is still tampered and wont reboot
nextlevel_44 said:
I did. I am on hboot 2.09.0000 radio 1.05.11.0606 stock recovery and relocked if that helps at all. I have tried running the JB ruu and it takes about 3 min but my phone is still tampered and wont reboot
Click to expand...
Click to collapse
The JB RUU is screwed up. I've downloaded it a few times and it doesn't actually make any changes
Rxpert said:
The JB RUU is screwed up. I've downloaded it a few times and it doesn't actually make any changes
Click to expand...
Click to collapse
Is There any ruu i can run other than that one seeing that i am on hboot 2.09.0000 i tried this file again and it goes through the whole process then does nothing
nextlevel_44 said:
mine said signiture failed. Can anyone advise
Click to expand...
Click to collapse
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
xHausx said:
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
Click to expand...
Click to collapse
Mac......yuck
Sent from my EVO using Tapatalk 2
Ok I finally got lucky. When I 1st flashed this file it had no affect on the P. Sensor. (Still didn't work). All of a sudden today its working perfectly, including VVM. (No longer getting a black screen while listening to messages). I don't know what would have caused it to start working but it is now. My phone is still 100% Stock
Edit: Upon further review the P. Sensor is still messed up. It will work flawlessly when outside during the day (bright light) but still turns the screen off under low light situations
Sent from my EVO using xda app-developers app
xHausx said:
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
Click to expand...
Click to collapse
Thank you for your help, I redownloaded the file and it appears to load and go through the motions but in the end it ends up back at the bootloader screen still saying tampered. I am trying to get this phone back to stock and nothing I try from the ruu to this img doesnt work. Any help will be greatly appreciated.
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Is it overlaying the signal bars or above the bars, like the data indicator in AOSP?
Sent from my CarbonROM 4.3'd HTC DNA
jlinn75 said:
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Click to expand...
Click to collapse
I had to reset mine to stock, relock it and return it on warranty, apparently there is a known issue with the sim card slot or tray or something. On my third now, debating whether to unlock and try again. No matter what I flashed on it, RUU, stock roms, anything, I couldn't get it back working right. Always had the roaming. New sim card didn't work either.
So your gonna have to do some work to get it back to stock and proper relocked, and then request a new phone from verizon.
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
jlinn75 said:
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This happen to me also. Luckily I had an upgrade available.
So reverting back to stock and then getting a new sim won't work.?
Sent from my Nexus 7 using Tapatalk 4
Harvey Dent said:
This happen to me also. Luckily I had an upgrade available.
Click to expand...
Click to collapse
what phone did you end up getting?
jlinn75 said:
what phone did you end up getting?
Click to expand...
Click to collapse
I ended up getting the S4. Wanted the One but figured I would give the S4 a go.
I just ****ing got this phone and having the same exact issue.. Got it off swappa so now looks like I'm ****ed
Sent from my Nexus 7 using xda premium
I to have the triangle
Are their any current threads on how to ruu back to stock?
I also have the triangle and was told flashing back to stock would fix it I guess we'll see lol
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Kevin3328 said:
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried replacing my sim with no luck. Is there a step by step guide to return to s-on with the moonshine method?
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
I did that and it did not work I had to warranty replace it
Nothing will fix it sorry guys
Sent from my HTC6435LVW using xda app-developers app
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
eyegor said:
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I don't think this has anything to do with renting towers. The same thing happened to me while I was flashing the GPE rom for the DNA. I spent two days trying to revert back to s-on and stock out of the box. Finally figured out how to do it. Next I took the ota and the triangle disappeared and showed 4G LTE.
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
I have the 'triangle' problem on a moonshine s-off DNA, but ADB doesn't recognize the phone, I only get "list of devices attached" and blank. It will connect in fastboot, but I've tried 3 computers, multiple usb ports, installing and updating drivers, etc. The device shows up in windows attached by usb and I can drag and drop files- any ideas? I am NOT a programmer by the way, so have been trying to rely on step by steps. Is there a way to fix it without adb? I guess even if I have to go back to box stock that will be better than no phone!
Also, the other things I've read do say you have to lock the bootloader in order to flash the stock hboot and run the RUU.
Thanks in advance-
Click to expand...
Click to collapse
Try these drivers for adb
https://db.tt/GMMd9IFX
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
Try these drivers for adb
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Planedoc, thanks for that, nogo however...when I tried to manually install those I got a Windows (7) error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."
I did try to install Koush's universal drivers as well via the exe he provided, and it still didn't recognize the phone in ADB, and then every time I plug the phone in it tries to install it's own drivers again, currently the DNA is showing up in device manager with device name: HTC6435LVW, Device type ortable devices, Location: Port_#0004.Hub_#0005, and driver files \Windows\system32\DRIVERS\WinUSB.sys and \Windows\system32\DRIVERS\WUDFRd.sys
Maybe I'll try my wifes macbook tonight and see if it shows up there.
Good evening yall, I have serious problem with my Droid DNA and need some help bad.
A couple days ago I noticed that my phone kept losing service so I researched it on Google and found out it could be something with the Sim card, easy to fix by getting a new one. I also read somewhere that it could be something that can be fixed with reboot and re flash of my ViperDNA Sense5 2.5.2. So I made a recovery and wiped the data off my phone with CWM, after re-flashing and rebooting into the rom I tried to use the Viper Authentication Wizard but wasn't able to complete because of the faulty SIM. I kept re-flashing and recovering with CWM for a couple more times still and on some boots the signal would return but I couldn't make calls because the error "android.process.system not responding".
I've tried to flash the Radios and Ruu back to stock and flash a stock rom but now it boots to a black screen with the status bar.
Please help I can't use my phone!!
I rebooted the phone while it was activating using the Activation Wizard in ViperDNA rom and relocked the boot-loader also which I think made more problems.
I've also used adb and fastboot commands and got a new SIM from Verizon, yesterday I flash cm10 and was able to receive a couple text messages before I lost service again. Since then everything I do doesn't work need some assistance.
Boot-loader screen says this
Unlocked
Monarudo PVT ship S-Off RH
CID-22222222
Hboot-1.54
Radio-1.01.01.1112
OS-3.06.605.4
Is the sim card not being detected at all? If that's the case one suggestion I can make before you go for a replacement or some other route is getting a new sim tray from HTC. Htc made a thicker tray and I got it a while ago and since then I have not had any issues with my sim card. If you contact them and tell them they will send it to you free or charge. I would try that. This sounds like a hardware issue not so much a software version.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Is the sim card not being detected at all? If that's the case one suggestion I can make before you go for a replacement or some other route is getting a new sim tray from HTC. Htc made a thicker tray and I got it a while ago and since then I have not had any issues with my sim card. If you contact them and tell them they will send it to you free or charge. I would try that. This sounds like a hardware issue not so much a software version.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea the SIM card isn't being detected at all, I'll give them a call tomorrow. Its just weird, any reason why this started happening now?
albike77 said:
Yea the SIM card isn't being detected at all, I'll give them a call tomorrow. Its just weird, any reason why this started happening now?
Click to expand...
Click to collapse
Be prepared to get you a nice cold beer and some lunch. You'll be on the phone all day.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
albike77 said:
Yea the SIM card isn't being detected at all, I'll give them a call tomorrow. Its just weird, any reason why this started happening now?
Click to expand...
Click to collapse
Ok so I got the new SIM tray and card but it's still not being recognized by CM10, so I tried flashing to a ViperDNA and now its (CWM) giving me an error "E: Can't open sdcard/rom (bad)"
I've tried wiping cahes and formatting disks but nothing is helping
This is driving me crazy please help
albike77 said:
Ok so I got the new SIM tray and card but it's still not being recognized by CM10, so I tried flashing to a ViperDNA and now its (CWM) giving me an error "E: Can't open sdcard/rom (bad)"
I've tried wiping cahes and formatting disks but nothing is helping
This is driving me crazy please help
Click to expand...
Click to collapse
you need to flash the recovery posted in the OP of viperdna for it to work properly
.torrented said:
you need to flash the recovery posted in the OP of viperdna for it to work properly
Click to expand...
Click to collapse
Thanks for the quick reply
So I was able to flash ViperDNA with twrp-beta but now it doesn't actually boot just stuck in the booting animation.
By flashing my recovery to the one on Viper page would that erase my previous recovery? And would my signal return?
Edit: Cant find the recovery in the OP
albike77 said:
Thanks for the quick reply
So I was able to flash ViperDNA with twrp-beta but now it doesn't actually boot just stuck in the booting animation.
By flashing my recovery to the one on Viper page would that erase my previous recovery? And would my signal return?
Edit: Cant find the recovery in the OP
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=2910#downloads
This is the download page for the rom the twrp beta img there is the one you need. Flash it through fastboot or flashify.
Than flash viper rom and you will be all set.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
http://forum.xda-developers.com/devdb/project/?id=2910#downloads
This is the download page for the rom the twrp beta img there is the one you need. Flash it through fastboot or flashify.
Than flash viper rom and you will be all set.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea I've tried that but my phone doesn't completely boot. (Stuck in bootloop)
albike77 said:
Yea I've tried that but my phone doesn't completely boot. (Stuck in bootloop)
Click to expand...
Click to collapse
So I see you have done lots to your phone and the original post said you had this and that what is your current radio and hboot? If you went back to the original stock then did you moonshine and unlock your bootloader again? I hate to say this but I had a dna that suffered from this and I had to replace the whole board, the top one, which was 65$ but if you are handy with solder you could do it for I think six. Anyways, current info please.
Try the ruu first. Then if it still doesn't boot it's hardware related.
Sent from my HTC6435LVW using XDA Premium 4 mobile app