5,596,235 Members 36,239 Now Online
XDA Developers Android and Mobile Development Forum

[Q] DNA texting and calling issue

Tip us?
 
Phibernaut
Old
(Last edited by Phibernaut; 8th February 2014 at 02:22 AM.)
#11  
Senior Member
Thanks Meter 12
Posts: 229
Join Date: Aug 2011
Location: Blairstown, NJ
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?

EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
 
finanandroid
Old
#12  
finanandroid's Avatar
Senior Member
Thanks Meter 108
Posts: 381
Join Date: Oct 2010
Location: Virginia
Quote:
Originally Posted by Phibernaut View Post
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?

EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...

a red "!" triangle over a phone, its stock recovery, reboot and go to setting and perform Phone Reset.
------------------------------------------
The Following User Says Thank You to finanandroid For This Useful Post: [ Click to Expand ]
 
sdamark
Old
#13  
sdamark's Avatar
Senior Member
Thanks Meter 197
Posts: 332
Join Date: Sep 2012
Location: Fountain Hills, AZ.
Quote:
Originally Posted by Phibernaut View Post
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?

EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
NVM

If you feel I've helped, hit Thanks.
The Following User Says Thank You to sdamark For This Useful Post: [ Click to Expand ]
 
Phibernaut
Old
#14  
Senior Member
Thanks Meter 12
Posts: 229
Join Date: Aug 2011
Location: Blairstown, NJ
Similar "!" images indicated recovery issues on my old Droid 3. Here they're a good thing and I'm back in action after using the steps discussed. Thanks all!

Sent from my HTC6435LVW using xda app-developers app
 
Phibernaut
Old
#15  
Senior Member
Thanks Meter 12
Posts: 229
Join Date: Aug 2011
Location: Blairstown, NJ
After a day or two of use I have lost LTE and a second reset has not brought it back. I have had past sporadic SIM card error messages upon boot of fresh CM installs but assumed it was normal. Connectivity would eventually resume but I'd nudge the card tray anyway. 3G seems strong & solid - thoughts/suggestions?

Sent from my HTC6435LVW using xda app-developers app
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Force Translucent Status Bar in KitKat ROMs with Xposed

It’s been a while since Android 4.4KitKat wasreleased, and we’re slowly … more

Fix the Ambient Light Issues on Your Google Nexus 5 using Xposed

The Google Nexus 5 is a great and rather popular device. This LG-produced … more

Google Glass XE16 Update Factory Image and Rooted Bootloader Now Available

You may recall that early yesterday, we talked about the XE16 … more