So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Update
micahl88 said:
So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Click to expand...
Click to collapse
So, I finally got adb/fastboot to work after about three hours of work including a variety of manually installing adb interface drivers/htc drivers and other misc work. After completing that, I flashed the firmware that santod has uploaded to hopefully resolve 4g issues, but still no 4g :crying: .I have my network settings set to cdma/lte of course...I would love any help.
Thanks
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
yesitsneuner said:
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
Click to expand...
Click to collapse
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
micahl88 said:
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
Click to expand...
Click to collapse
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
zandarillis said:
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
Click to expand...
Click to collapse
Oh, I actually did not. Thanks for clarifying that for me, I will just keep checking back for rom patches.
Thanks.
finanandroid said:
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
Click to expand...
Click to collapse
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
micahl88 said:
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
Click to expand...
Click to collapse
Ok, I reflashed a recovery from a different source and finally got stock recovery to run then factory reset and then MAGIC 4G reappeared. Thanks. Now, what caused this to happen? Should I not reflash another rom? 4g is more important to me than other roms...
Related
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
aftafoya said:
So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
Click to expand...
Click to collapse
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
synisterwolf said:
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
Click to expand...
Click to collapse
Current:
S-OFF
Kernel: Snuzzo's Funky v1.3
Rom: Neo's AOKP v1.5 Linaro
Radio: 2.22.10.0801, 2.22.10.0803
HBOOT: 2.27
I am s-off with hboot ver 2.27. The last RUU I flashed was 4.03.605.2 from micromod's thread here. I believe that I used version 1.2. I followed his instructions first flashing the firmware, then recovery, then the ota global plus. This was the same firmware that I was originally on before I left NeoMax2.0. It kept bootlooping so I flashed Neo's AOKP again. Both his AOKP and AOSP work just fine besides the data problem. I also flashed snuzzo's funky kernel v1.3 and it didn't help. So currently I'm stuck in AOKP/AOSP with only 3g data speeds. Should I try flashing an older RUU?
once my phone charges up, i'm going to flash the stock 3.14 ruu. i'll check back and let you know if it worked.
it's a no go. flashed the 3.14 ruu from shippedrom.com and kept boot looping. sometimes it would get to the 2nd htc splash screen but it wouldn't actually get to the rom. fresh out of idea's, could use your magic synister!
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
forey79 said:
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
Click to expand...
Click to collapse
Thanks for the reply, I'll try it out tonight. I'm thinking that maybe I will try to flash the global that originally came with my phone. I can't remember the exact one, but I think it was the gb version just before ics came out. I'll post an update with the results.
hmm looks like you have the right radios and hboot or anyway its the same as i have but it still wouldn't hurt to start over the only reason i say something is because i skipped the factory reset in boot loader and i had data problems im not the smartest android on the block here...lol so i try not to tell people stuff that i dont know about that well just what worked for me
And flash Neo's CM9 RAGE rom (aka funky symbol rom).
AOKP has issues where you can lose 4G by going into network settings, CM9 apparently does not. Also, make sure your network mode is set to the one that supports several different data modes, even if you don't get them. Trying to use the one that just says CDMA/LTE prevents 4G signal.
And just FYI, you can run neomax 2 on top of the global firmware, you just can't use it as a true global phone since it is an older rom.
Sent from my Rezound using Tapatalk 2
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
So tonight I've run into an issue that confounds me. I am a veteran flasher of roms and kernals and never have I found myself so stuck.
I did the following:
1. I applied Facepalm S-Off to my phone earlier and it worked fine, data still worked.
2. I later went to flash Beastmode. I was running Cubed and forgot to reset to stock before flashing.
3. My phone wouldn't boot. So I flashed back Cubed with Fastboot, and the phone boots.
The issue is that now I have no radio. I see the Verizon Wireless on the lockscreen and there are bars on the top bar, however whenever I try to make a call, it says call ended unexpectedly (paraphrase) and whenever I send a text it says SMS Problems. I have wifi, but I need my phone to work as a phone! It also says "Preparing SIM" every few minutes. Any ideas what could be wrong here?
I am currently on NOS N7 with the included Beastmode Kernel.
Thank you in advance for helping me out! I'm a little lost here.
I really hate to bump things, but I need a phone that is... well a phone. If anyone can help that would be great. I am going to have to go to Verizon if not. I have reset everything including unlock flags to stock in preparation of that sad reality.
flash a stock rom and different kernel
azhockey said:
So tonight I've run into an issue that confounds me. I am a veteran flasher of roms and kernals and never have I found myself so stuck.
I did the following:
1. I applied Facepalm S-Off to my phone earlier and it worked fine, data still worked.
2. I later went to flash Beastmode. I was running Cubed and forgot to reset to stock before flashing.
3. My phone wouldn't boot. So I flashed back Cubed with Fastboot, and the phone boots.
The issue is that now I have no radio. I see the Verizon Wireless on the lockscreen and there are bars on the top bar, however whenever I try to make a call, it says call ended unexpectedly (paraphrase) and whenever I send a text it says SMS Problems. I have wifi, but I need my phone to work as a phone! It also says "Preparing SIM" every few minutes. Any ideas what could be wrong here?
I am currently on NOS N7 with the included Beastmode Kernel.
Thank you in advance for helping me out! I'm a little lost here.
Click to expand...
Click to collapse
I'm having exactly Dane issue after flashing beastmode 4.3, how did you fix it?
Sent from my HTC6435LVW using xda app-developers app
motumbo said:
I'm having exactly Dane issue after flashing beastmode 4.3, how did you fix it?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Return to lock using "fastboot oem lock"
Download HTC DROID DNA’s RUU.exe, this is a stock firmware by HTC, which contain radio, systems and bootloader.
make sure that your phone is being detected by your computer. then reboot it into bootloader. When you see Fastboot USB in the middle section run the ruu.exe on your computer.
This should repair bootloader and radios.
dragonstalker said:
Return to lock using "fastboot oem lock"
Download HTC DROID DNA’s RUU.exe, this is a stock firmware by HTC, which contain radio, systems and bootloader.
make sure that your phone is being detected by your computer. then reboot it into bootloader. When you see Fastboot USB in the middle section run the ruu.exe on your computer.
This should repair bootloader and radios.
Click to expand...
Click to collapse
Thanks for your answer. I've tried return to stock with success and now my phone is in full stock state but it keeps showing preparing sim card every two or three minutes exactly as it was before. When I switch the phone to 2g the problem is gone, I bought this phone online and I'm a gsm user so I own the most expensive 2g phone in market.
Phone was perfectly working in all roms and almost every kernel, the problem came up just when I flashed beastmod 4.3 kernel then I went into bootloops and I flashed stock kernel and it booted since that I've been with this issue. I'm gonna try different sim cards because I don't believe this is a software issue anymore.
After trying several ROMs that would not connect to VZWs LTE network (Cyanogenmod, LiquidSmooth), I decided to go for a stock-ish ROM: NuSenseSIX-MAX which is an HTC One port. It installed without a hitch and says its on LTE but then after about 10 minutes, switches to 3G and won't go back to LTE unless I reboot the phone, and after 10 minutes, back to 3G. I installed the latest firmware and baseband (1.02.01.0207) so that isnt the issue. Anyone experience this? Have any ideas?
killerroomba said:
After trying several ROMs that would not connect to VZWs LTE network (Cyanogenmod, LiquidSmooth), I decided to go for a stock-ish ROM: NuSenseSIX-MAX which is an HTC One port. It installed without a hitch and says its on LTE but then after about 10 minutes, switches to 3G and won't go back to LTE unless I reboot the phone, and after 10 minutes, back to 3G. I installed the latest firmware and baseband (1.02.01.0207) so that isnt the issue. Anyone experience this? Have any ideas?
Click to expand...
Click to collapse
Any luck finding a fix? I am having the same issue.
You guys need to flash a stock recovery and perform a factory reset with the stock recovery installed.
Many aosp roms corrupt the NV radio partitions and nothing will fix that except stock recovery.
So back up anything important on the device, grab the stock recovery, load it up.
Then either from hboot, or rom settings menu, or from stock recovery (exclamation point/phone image/volume up+power to get menu) factory reset.
That will fix the NV radio partition that corrupt.
Then you can reflash a custom recovery and set back up your rom.
This is the only true fix for this issue.
Yes RUU will fix it too because it does the factory reset with stock recovery as well, but that's not necessary, just having the latest firmware, stock recovery and doing the reset is all it takes. :good:
Same rule applies on the m7 and m8 as well...
santod040 said:
You guys need to flash a stock recovery and perform a factory reset with the stock recovery installed.
Many aosp roms corrupt the NV radio partitions and nothing will fix that except stock recovery.
So back up anything important on the device, grab the stock recovery, load it up.
Then either from hboot, or rom settings menu, or from stock recovery (exclamation point/phone image/volume up+power to get menu) factory reset.
That will fix the NV radio partition that corrupt.
Then you can reflash a custom recovery and set back up your rom.
This is the only true fix for this issue.
Yes RUU will fix it too because it does the factory reset with stock recovery as well, but that's not necessary, just having the latest firmware, stock recovery and doing the reset is all it takes. :good:
Same rule applies on the m7 and m8 as well...
Click to expand...
Click to collapse
Tried this - no love.
Steps done: Flashed stock recovery, chose factory reset from modified hboot, flashed custom recovery and PA 4.6 ROM.
burtonlax said:
Tried this - no love.
Steps done: Flashed stock recovery, chose factory reset from modified hboot, flashed custom recovery and PA 4.6 ROM.
Click to expand...
Click to collapse
Number one cause of the problem: Aosp roms
First thing you went and installed after fixing the issue: Aosp rom
I've been having network issues as well for a couple of months now. I think it's actually a Verizon issue as I just got a certified replacement device that's having the same problems as my old device. The issue seem to have coincided with the latest update/as well as Verizon's switch to xlte for certain phones. My signal strength/bars is a lot weaker than before. I also have a lot of drops to 3g and 1x in a 4g area that seems to have trouble switching back to 4g. When I called to report the issues/get a replacement device they said that they are aware that many DNA users have been having issues since the latest update. Hopefully we get another update to fix these issues. Also I've never loaded anything aosp on this device. Just stock and viper.
Sent from my Nexus 7 using XDA Free mobile app
I had this issue for a very long time. Couldn't stay connected to 4G to save my life. But as Santod said, you need the stock recovery and stock hboot, then do a factory reset from hboot. I have been connected to 4G for the last 3 days since I fixed this prob. Now waiting for my new sim tray. I actually RUU'd to stock 3.06 and still had little to no 4G. Factory reset and instantly connected to 4G. Gave it a whole 24hrs, no issues or disconnects, then weaksauce and firewater. Now back on Viper and I haven't seen 3G or 1X for 3 days and counting. Hope it helps.
--X
I.M.famous XMAN said:
I had this issue for a very long time. Couldn't stay connected to 4G to save my life. But as Santod said, you need the stock recovery and stock hboot, then do a factory reset from hboot. I have been connected to 4G for the last 3 days since I fixed this prob. Now waiting for my new sim tray. I actually RUU'd to stock 3.06 and still had little to no 4G. Factory reset and instantly connected to 4G. Gave it a whole 24hrs, no issues or disconnects, then weaksauce and firewater. Now back on Viper and I haven't seen 3G or 1X for 3 days and counting. Hope it helps.
--X
Click to expand...
Click to collapse
Ok, so I flashed stock recovery and stock hboot and did a factory reset from hboot - however my previous rom still loads... shouldnt the factory reset delete the rom? I'm not sure how to verify the factory reset worked.
burtonlax said:
Ok, so I flashed stock recovery and stock hboot and did a factory reset from hboot - however my previous rom still loads... shouldnt the factory reset delete the rom? I'm not sure how to verify the factory reset worked.
Click to expand...
Click to collapse
Factory reset only erases /data (without wiping /data/media) /cache and resets NV partition.
Sent from my HTC6500LVW using XDA Free mobile app