Ever since I downloaded this one theme and it didn work, My phone cannot install themes. Every time I install a theme, I will boot up, get force closes that I dont even know what force closes because im stuck on a black screen, and I always have to restore back to my last save. What is up with this.
What rom are you using? That would help out things a lot better
We need more info. We need to know what ROM you are using, what theme you tried flashing, and any other info you can provide. Otherwise, you just have a story for a first post that no one is going to do anything with but read over and move on.
Sounds like dbdata issue. Try adrynalyne's 2.7 fix. He has a tar/odin file in there that will fix your phone.
makav3ll1 said:
Ever since I downloaded this one theme and it didn work, My phone cannot install themes. Every time I install a theme, I will boot up, get force closes that I dont even know what force closes because im stuck on a black screen, and I always have to restore back to my last save. What is up with this.
Click to expand...
Click to collapse
Had the same issues. Had to flash to bare bones stock via Odin and start over. I was running sc 2.6 voodoo.. Flashed 2 themes, on the 3rd it was FC hell; even if I restored my very first theme (VA Green at that time) it would FC hell. Only think g that wiould load was my theme free sc 26voodoo
Did you figure this out?? It's doing to me again. Sammmme ****, on my 3rd theme i get fc loops and cannot flash any themes... currently on sc 2.8voodoo
Sent from my SCH-I500 using Tapatalk
I have stock eb01 deodexed. Some themes work once I install a theme that gives me force closes, then install another theme over that. I really have gaven up and Dont care anymore. I guess the fix is the re-flash stock eb01 with odin, but im way to lazy
Background:
Unlocked, Rooted, S-Off, ICS Leak RUU 605.22
Was running Ivysaur Rom with no issues at all. On Sunday afternoon, the phone started acting up, wouldn't light up when pressing power button, huge lage problems and all the sudden, incoming calls lock the phone requiring a battery pull and outgoing calls lock during call resulting in battery pull. Well Sunday night Venosaur was released so I tried to update to that, update went good, but no fix. So desperate, last night I flashed the new leaked RUU. Everything went great, thought everything was working, but now, no incoming calls at all and outgoing locks the phone. Please help me, i'm at my wits end.
Upon further investigation, it seems as if I'm getting tons of Android Process has stopped, where you either select ok to close or wait. These are happening in the background for some reason. I've ran fix permissions, just tried clean wipe 5x and then flashing scroslers new debloated of the leak. Still having issues though. I think these process stoppages are causing my messaging issues too, as in no landscape texting which now comes and goes.
What should I do?
Wipe data/cache/system/boot in recovery and re-install rom. Be very careful of what data you are restoring as it sounds like a data issue to me.
dottat said:
Wipe data/cache/system/boot in recovery and re-install rom. Be very careful of what data you are restoring as it sounds like a data issue to me.
Click to expand...
Click to collapse
+1
I've once had similar issues flashing one ROM over another without wiping data properly. Could be due to different UIDs, folder layouts, etc. compared to the ROM pre-Ivysaur. And then Titanium Backup restores wreak havoc due to the differences. Remembering to do nandroid backups helps for just such occasions.
If sure about being fully clean before flashing, check MD5 of your downloads for corruption, check network settings in the ROM, reflashing the RUU twice in a row before using, and reverting back to PKMN ROM or downgrading to try and fix the call issues.
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?
Hi. I havent posted very often here. I really appreciate what all the devs do here! Anyways. I have a brand new HTC One. Unlocked the bootloader through hassoon's all in one toolkit, rooted it with SuperSU, and flashed the kernel called ElementalX. I used all the default settings while setting up ElementalX. Im not sure if my camera stopped working after I flashed all the kernel and everything else, but I am trying to use the camera now, to check out Zoe and just fool around with it, but I cannot get the camera to load. I went to settings>apps>all>camera> and cleared all the data, all the cache, and force stopped. Tried to connect the camera again, no luck, still says cannot connect to camera. I also reboot the phone and no luck still. I just installed nova launcher free edition, so im going to try and switch back to the Sense UI instead of Nova and see if that helps.... anyone experiencing any similar problems? or know of any ideas to fix this???
Thanks again!
SonneKonig said:
Hi. I havent posted very often here. I really appreciate what all the devs do here! Anyways. I have a brand new HTC One. Unlocked the bootloader through hassoon's all in one toolkit, rooted it with SuperSU, and flashed the kernel called ElementalX. I used all the default settings while setting up ElementalX. Im not sure if my camera stopped working after I flashed all the kernel and everything else, but I am trying to use the camera now, to check out Zoe and just fool around with it, but I cannot get the camera to load. I went to settings>apps>all>camera> and cleared all the data, all the cache, and force stopped. Tried to connect the camera again, no luck, still says cannot connect to camera. I also reboot the phone and no luck still. I just installed nova launcher free edition, so im going to try and switch back to the Sense UI instead of Nova and see if that helps.... anyone experiencing any similar problems? or know of any ideas to fix this???
Thanks again!
Click to expand...
Click to collapse
Anyone? Any ideas?
Anyways. I reflashed the Kernel. But this time I opted in for the Camera fix option, which I opted out for last time because the installer says you dont need to do the camera fix if on a stock rom, which % am on a stock rom. Well, after it was all done and flashed again, with the camera fix this time, the camera seems to work. So I will reboot it again (the instructions of the kernel say you need to), and see if it still works.