Related
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!!!
hello.
so here is my problem.
a friend of mine who owns a S3 , recently comes across this problem
no SOUND during calls, both incoming and outgoing (front ear speaker , back speaker and headphones , none of them work!!!)
but VIBER works fine (has sound in front ear speaker).
I flashed some ROM such as stock MB5 , Omega V43 , Android Revolution HD 23.3 ...etc , none of them has good luck , i also tried few different radio ... but still ...
any idea ? i don't think it should be a hardware problem because VIBER works.
If it's not hardware issue, try getting phone back to the factory settings, flashing stock ROM, unrooting, etc... And then you'll see.
Good luck
Sent from my GT-I9300 using xda premium
Maybe it's because of locked phone? I flashed ROM, but didn't unlock it, could it be the reason?
Sent from my GT-I9300 using xda premium
I doubt but... Which ROM did you used? And how did you performed flashing(via Odin or recovery)?
Sent from my GT-I9300 using xda premium
Fons1ca said:
I doubt but... Which ROM did you used? And how did you performed flashing(via Odin or recovery)?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The ROM I mentioned in OP, via recovery...
Sent from my GT-I9300 using xda premium
I have tried AOKP and Slim, still no good
Sent from my GT-I9300 using xda premium
If youve tried everything? Try using megawipe to wipe before flashing rom, also redownload the rom again via the pc & also ask the dev what the m5 sum is & check it against your re downloaded rom before reflashing again & see if that works?
Hope this works if so press that thanks button :thumbup:
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Try this out:
(Optinal backup)
1. First go to sammobile.com and find a PROPER firmware for your s3. Downloaded file should be .zip but extract it as .tar.md5 file.
2. Put your phone in download mode - Hold Vol Down + Power + Home for 10 seconds then press Vol Up to continue.
3. Download Odin 1.85 and run it.
4. Make sure that only Auto Reboot and F.Reset Time are checked and click on PDA, select the .tar.md5 file that you just extracted... Click start
Once it's done, put ur phone into recovery and wipe data/cache and then reboot...
Sent from my GT-I9300 using xda premium
deanr1977 said:
If youve tried everything? Try using megawipe to wipe before flashing rom, also redownload the rom again via the pc & also ask the dev what the m5 sum is & check it against your re downloaded rom before reflashing again & see if that works?
Hope this works if so press that thanks button :thumbup:
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Click to expand...
Click to collapse
if i may, what exactly is megawipe ? wipe everything ? i don't won't format internal SDcard because over 8GB datas and causes lots time to copy and past ... beside i really don't think internal SDcard has anything to do with it ...
with all due respect, it sounds like everything i have tried , what different does it make with my procedure ?
phone is not on my hand right now , will try so tomorrow.
everytime i install new ROM , i did WIPE data/cache, format /system partition and even fix permissions ...
no good at all , really strange !
i have never come across with such problem.
i googled and searched around XDA , some says it is hardware problem , but consider viber does work so i don't think it's hardware.
this is driving me nuts now ...
however it is Nerwork LOCKED phone ... but as far as i know , it should has nothing to do with it , but maybe need to put it under concern ...
oh wait a sec ,, i didn't upgrade the bootloader , could it be related ? i don't think so ...
didn't upgrade because the red mark over up-right side screen you know ...
but the way , everytime i try to test dial , it always has something like network dropped or no service or something like that , i can't exactly translate it ...
qtwrk said:
with all due respect, it sounds like everything i have tried , what different does it make with my procedure ?
phone is not on my hand right now , will try so tomorrow.
everytime i install new ROM , i did WIPE data/cache, format /system partition and even fix permissions ...
no good at all , really strange !
i have never come across with such problem.
i googled and searched around XDA , some says it is hardware problem , but consider viber does work so i don't think it's hardware.
this is driving me nuts now ...
however it is Nerwork LOCKED phone ... but as far as i know , it should has nothing to do with it , but maybe need to put it under concern ...
Click to expand...
Click to collapse
What do you mean phone is locked? Locked to one network? Or been locked because its been reported stolen or because its been locked due to the bill not been paid? Cause there is a solution to unlocking the sim to any network look in this forum for the apk. But if its cause the phone is locked due to an unpaid bill or been reported lost of stolen.... there is no fix (unless you wanna move out of europe?)
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Vibes uses wifi so maybe flashing a new modem will fix your problem.. I've had this happen to me a few times on different phones and different android's.. Usually a few reboots fixed it but you need to try flashing a few radios for your country first..
Sent from my GT-I9300 using xda premium
deanr1977 said:
What do you mean phone is locked? Locked to one network? Or been locked because its been reported stolen or because its been locked due to the bill not been paid? Cause there is a solution to unlocking the sim to any network look in this forum for the apk. But if its cause the phone is locked due to an unpaid bill or been reported lost of stolen.... there is no fix (unless you wanna move out of europe?)
sent via my super modded Foxhnd 2.2 with Tapatalk 2
Click to expand...
Click to collapse
Sorry for my unclear description.
It is network locked phone, locked to Spain Orange, but my SIM and her SIM are orange as well, and both SIM works fine in my phone, able to data connection, SMS and calls.
But both our cards doesn't work on her phone...
Sent from my GT-I9300 using xda premium
NatTheCat said:
Vibes uses wifi so maybe flashing a new modem will fix your problem.. I've had this happen to me a few times on different phones and different android's.. Usually a few reboots fixed it but you need to try flashing a few radios for your country first..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I almost flashed all radio I can find... but...
Sent from my GT-I9300 using xda premium
SOLUTION during calls(phone A->phone B damaged; B->A)not work soundmicro or speaker
FROM PORTUGAL:
For help i found solution during calls(phone A-> phone B damaged and B->A) not work sound (micro or speaker)
Status:
->new fone SIII bloqued to vodafone
->android 4.1.1 using band base: I9300BUDLI2 and compilation number: JRO03C.I9300XXDLIH
->someone unlock the phone
->during calls using network TMN the problem appears
->searching net, some soluction like turn off S-voice etc. Not work. OK.
->install some kernels and some cook roms, not work.
->using viber is work fine the call. Sow, i guess hardware is god, problem is software.
->sms works fine
Solution: send to reparation.
Steps:
->put triangle away: 0
->install last stock Csc TPH: XXDLJ4 , october 2012
Done...but even now....lets go try some calls....A->B.......B->A.....hum, reboot phone and replay. Replay using another Phone: C->B; B->C.
AND WILL WORKS.
I don´t now what the boy using the unlock phone, but not problem in hardware. Is problem in some layers from hardware and Android.
In your case, just flash rom origin wen phone is seller.
Have a good day.
EDIT:
I try the Chaos rom, some diferent customs and works the phone calls. Sow, flash a stock rom the country and carrier that the phone was sold
Jomota7 said:
FROM PORTUGAL:
For help i found solution during calls(phone A-> phone B damaged and B->A) not work sound (micro or speaker)
Status:
->new fone SIII bloqued to vodafone
->android 4.1.1 using band base: I9300BUDLI2 and compilation number: JRO03C.I9300XXDLIH
->someone unlock the phone
->during calls using network TMN the problem appears
->searching net, some soluction like turn off S-voice etc. Not work. OK.
->install some kernels and some cook roms, not work.
->using viber is work fine the call. Sow, i guess hardware is god, problem is software.
->sms works fine
Solution: send to reparation.
Steps:
->put triangle away: 0
->install last stock Csc TPH: XXDLJ4 , october 2012
Done...but even now....lets go try some calls....A->B.......B->A.....hum, reboot phone and replay. Replay using another Phone: C->B; B->C.
AND WILL WORKS.
I don´t now what the boy using the unlock phone, but not problem in hardware. Is problem in some layers from hardware and Android.
then at night I cooked a rom install and see.
In your case, just flash rom origin wen phone is seller.
Have a good day.
Click to expand...
Click to collapse
Do you mean even if I'm on a different country/region I should flash XXDLJ4 modem? Thanks!
Sent from my GT-I9300 using xda premium
cavjr08 said:
Do you mean even if I'm on a different country/region I should flash XXDLJ4 modem? Thanks!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I do not know what really causes the problem, but the main thing is: take the last stock rom FULL country and carrier that was bought the phone. In my case the XXDLJ4 is a rom vodafone in Portugal. I don´t now is work in another country or carrier.
For in the midst of several layers between hardware and software are sections that cooks do not touch rom (settings network operator and country) and performing jailbreaks or wrong things can corrupt those sections.
It was so decided.
If you want you can test a stock rom than the original phone, in my case gave error when using a rom free carrier, the charge for the phone (via ODIN) stopped. More certain is the size in MB of the sections are different from carrier to carrier (or country to country??).
Try it.
Everytime i flash a modem i get no service i need my t-mobile 4g please help i know i have t-mobile 4g in my area it doesn't matter what modem i flash when i reboot it says i don't have a sim inserted causing me to go back into recovery and do a restore
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Which ROM is your phone on?
Do you know your APN setting?
Class_of_punk26 said:
Everytime i flash a modem i get no service i need my t-mobile 4g please help i know i have t-mobile 4g in my area it doesn't matter what modem i flash when i reboot it says i don't have a sim inserted causing me to go back into recovery and do a restore
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem till I ditched TWRP for CWM. My I717 seems to like ClockworkMod better. Just couldn't get TWRP to flash the modem correctly. *#06# will give you the "Null Null" IMEI message if you have the same problem as me. Use Kies to recover and initialize the device, its under "Tools". When done you will be on JB with proper IMEI. Flash CWM through odin and go from there.
**EDIT**
Turns out that the problem I was having might have been because of outdated modem files. The issue is resolved for me with the modems at the following link. 4g lte has never been this fast before these drivers. Fast and stable, be sure to give the OP a thank you.
Link: http://forum.xda-developers.com/showthread.php?t=1679722
Moto Mouth said:
I had the same problem till I ditched TWRP for CWM. My I717 seems to like ClockworkMod better. Just couldn't get TWRP to flash the modem correctly. *#06# will give you the "Null Null" IMEI message if you have the same problem as me. Use Kies to recover and initialize the device, its under "Tools". When done you will be on JB with proper IMEI. Flash CWM through odin and go from there.
Click to expand...
Click to collapse
I've been having the same issue. I started with Stock, went to CWM ver 6, CM 10.1. Decided to flash a modem, and then it would say unknown baseband / no phone number / no IMEI. After trying many modems and restores, I have restored through KIES back to factory as of now.
If anyone has an idea, it would be appreciated.
I live in Florida the only way I get 4g LTE is with stock modem...I used to have the same issue...so I just keep it stock...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
thystra said:
I've been having the same issue. I started with Stock, went to CWM ver 6, CM 10.1. Decided to flash a modem, and then it would say unknown baseband / no phone number / no IMEI. After trying many modems and restores, I have restored through KIES back to factory as of now.
If anyone has an idea, it would be appreciated.
Click to expand...
Click to collapse
no need to do anything.just go to app setting ...running ..you will see ''sim'' app running just close it and restart your phone it will show your imei ...n baseband all....
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