Related
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?
Hey guys; I've been using dastin1015's ROMs for almost a year now on my Sprint Evo 3D. I definitely don't know everything (probably not even close) about using custom ROMs, but I'm not a complete noob.
That said, I screwed up. I successfully replaced my 4ext touch recovery with TWRP as dastin1015 says must be done for this ROM. I then wiped everything except my SD card and 'System' and flashed the latest ROM located here (Villuminati 12/08/13), and the "full complete" GApps package located here (4.4).
I rebooted the phone, and admired the new CM splash screen. Once the ROM loaded, I immediately got a couple of stock (system) apps (com.android.phone and ThemeManager along with some others) forceclosing repeatedly, preventing the phone from fully booting and making it very difficult for me to reboot the phone into recovery-- the messages popped up over and over again on top of the menu for reboot. I eventually did manage to get back into TWRP though.
At that point, I wiped *everything* except my SD card, and flashed the ROM and GApps again. Now I'm having the same problem, but with even more system apps force-closing, and I cannot reboot the phone or do anything else with it via the phone itself.
What do I do now? Can I fix this with ADB?
I read that using this 4.4.1 GApps might solve or prevent this problem, but it's iffy. In any case, unless someone has a better solution, that's the next thing I wanna try after managing to reboot into recovery. Do any of you think that will work?
Thank you.
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Glad to hear it dschlemmer.
The proper answer to the first part of my question (can I fix this in adb) is "of course, you idiot, just connect the phone to your pc and type "adb reboot recovery" and then wipe and re-install your old ROM or something."
However, I can't get the PC to recognize the phone, despite it having the proper drivers and having recognized it before. I think it's stuck at a phase in its boot-up that comes before the usb debugging is activated. My PC recognizes something is plugged in, based on the ding noise it makes (it's a Win 7 Pro x64 machine, and I think most of us are familiar with that ding noise), but the normal behavior of searching for and finding the drivers and then telling me the device is ready to use never occurs. Neither is there that "safely remove hardware" button in the taskbar.
So, of course, if the computer itself doesn't recognize it, adb can't either (confirmed by typing "adb devices" and it showing nothing). Is there anything I can do, or have I actually managed to completely (irreparably) brick my phone?
EDIT: The usb port is functioning, at least, as is whatever part of the circuitry or firmware controls the LED while plugged in and/or charging, because that works just like it should. It's just that I can't do anything but repeatedly cycle through the same "Unfortunately, the process com.android.phone has stopped", "Unfortunately, Themes provider has stopped", and a couple other messages that get covered up by those two, including one I briefly saw that mentioned "Settings". Haven't been able to see any of the others for long enough to identify any part of them.
EDIT2: I forgot about using the bootloader. Completely forgot. Stupid. Successfully in recovery, about to flash the same ROM with the new GApps. If it gets screwy again, I'll just remove the battery, replace it, and get into the bootloader to get into recovery.
dschlemmer318 said:
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
electrickoolaid said:
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
Click to expand...
Click to collapse
i flashed rom then 12-6_gapps_standard_4.4.1_signed then reboot this is the link for the gapps : http://forum.xda-developers.com/showthread.php?t=2012857
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!
Hello all any help would be greatly appreciated, I have a HTC DROID DNA, 4.4.2 kitkat, Verizon, and decided i wanted to get my feet wet by flashing a ROM, well i got more than my feet wet, I am a total newbie please be patient, but a fast learner, so onto the problem, after reading for a 2 days straight i used weaksauce to get temp root, then ran firewater to get s-off, afterwards i installed CWRM and sideloaded cyanogen mod with google apps, upon install all was going great I had bars, it said 4g LTE then i tried to make a call and no go, i went into setting messed around with network tabs but nothing really worked, In my about phone i have an IMEI but my IMEI v is 00 and my phone number is also showing up as 0000000000 so i did factory data wipe, and rest, went back to stock same problem, I dont know if verizon did this or cyanogenmod, but the phone loads ROMS but i cant make calls please help.
EDIT: well i either figured it out or got really lucky, I reinstalled cynogenmod and it was showing my IMEI and phone number but no mobile network so i basically loaded up adb, and folowed the steps on this thread
http://forum.xda-developers.com/showthread.php?t=2612740
to reload stock bootloader, recovery and radio, did all that, then rebooted it reinstalled CM 11 and what do you know my radio works, IMEI is there, from within the ROM i downloaded CWRM manager and installed it, set up my phone, VVM with google voice and thoroughly enjoying CM stable, even though I thought this would be easy peasy and was just gonna get my feet wet, oh boy this has bene a hell of last 3 days, but it was fun i thoroughly look forward to learning more and hopefully contributing.
If this had been like a month ago when I was flashing busybox and getting sdcard fix to work, closed etc, I'd say its probably something I did. But this really came from out of the blue. I switched back to stock launcher because the message "Google app stopped working" kept appearing.
I cleared defaults on stock (like it says to do) but kept getting the message. Don't know if this means anything but 2 days leading up to this my phone kept informing me there were no new software updates, something it hadn't done in the past.
I'm using the latest update through the HTC site, rooted with stock kernel. Hoping someone can shed light. Thanks.
you must delete the data of it in the system partition i dont remember where it is after that you can try to download it again