I have the EVO 3d and recently installed this ROM "MIUI.us 2.1.6 HTC EVO 3D CDMA [01-07-2012] by jdeloach" I just wanted to test it out a few days and see how well the EVO 3d handled it. I was impressed with the ROM and had no trouble with it but just wanted to go back to another custom Android ROM. So after flashing the new custom Rom and my phone booted up I started to get several MIUI force close. I used Rom Manager and Have done the same thing on my EVO 4g without any issue but this time on boot I still get the MIUI force close. After about 4 or 5 force close it stops until next reboot. Just wondering if anyone has seen this before and is there a quick fix? I couldn't find a thread on this issue so here I am. It may also be something simple but I have never had this problem and therefore have no idea how to stop it. I have done everything I can think of. Different ROM's, format SD card, factory data reset, put factory ROM back on, nothing seems to get rid of the MIUI force close at start up no matter what ROM I have flashed.
When flashing new ROMs, I generally like to run what's been termed a "Superwipe" or "Format All" script. You flash this just like you would flash a ROM, however it wipes all of the partitions (minus the WiMax one, and probably one or two others) so that no data is left over from the previous install.
I use myn's Warm Format All tool here. This is from this thread. It's NOT specific to the Warm TwoPointThree ROM, so it's a great tool to keep on your SD card whenever your ready to flash a new ROM.
Just flash it before you flash your new ROM.
Hope this helps!
Thank you very much.
Well I be darned. I spent three days trying to understand why it was doing what it was doing and your suggestion fixed it instantly. I did try something similar to what you said to do but with another zip with no luck. So I was a little skeptical, but after I flashed the zip file you told me to download and then flashed my ROM which is Infected ROM Eternity ROM for Rooted HTC Evo 4G![Sense 3.5] it was fixed
I owe them guys a plug cause this ROM is pretty darn good. Anyways I knew it was something pretty simple I just needed to be pointed in the right direction, so, many thanks to you for helping me get rid of those annoying MIUI force close. I really do appreciate you quick and helpful response.
HTC EVO 3D, Quietly Brilliant.
A man is not complete until he's married
and then he Finished.
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
dzap said:
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
Click to expand...
Click to collapse
i can't tell what kernel on here, its i flashed silver needle and then the rom and it nevered booted up.
I had the same problem using ROMs from XDA. Found that I used RUU to back to stock and it stopped. Haven't had a single reboot since I went back to stock where I would get reboots constantly, to the point the phone was useless.
Since I have S-Off, used the root patch to get root access, but only can be done with S-off...
djcro said:
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
Click to expand...
Click to collapse
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
cobraboy85 said:
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
Click to expand...
Click to collapse
yeah, most likely your issue is flashing a kernel NOT COMPATIBLE with the new base....
oh and your only compatible kernel at this time is stock
i tried to do the ruu step and none of the verisons workked, anybody have anymore ideas?? this is were i downloaded the ruu's from for sprint http://www.filefactory.com/f/4ef0ef536face67a/
Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
incarceration said:
Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
Click to expand...
Click to collapse
what hboot are you using? sounds like the rom isnt getting the permission it needs to install the boot systems and data partitions also are you unlocked if youre on hboot 1.5 or if you have atleast hboot 1,4 with s-off?rooted?
incarceration said:
Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
Click to expand...
Click to collapse
I also had this problem on my Replacement EVO 4G, which scored me a free upgrade to an EVO 3D lol. Is your phone Refurbished?
Are you restoring apps+data or just apps???
#Root-Hack_Mod*Always\
If your using an after market battery, take a look at my post :
http://forum.xda-developers.com/showthread.php?p=24126392
Sent from my PG86100 using Tapatalk
Thanks for replies!
Bit of background:
-This is a new phone (and by new, i've owned it since it was out of the original box), not a refurb.
-HBoot 1.4
-S-OFF
-When I mentioned restoring the apps from MyBackup Pro, It was only with APKs; but it also happened when I just had it redownload them all from Google Play. I did the restore method via MyBackup Pro as an attempt to see if it would help.
-Stock battery
The only thing I can think is it's an app that is just not sitting right with the ROM?
I'm using the Infected Eternity ROM now and it just will randomly restart when it sits there idle.
incarceration said:
The only thing I can think is it's an app that is just not sitting right with the ROM?
I'm using the Infected Eternity ROM now and it just will randomly restart when it sits there idle.
Click to expand...
Click to collapse
What software are you guys ? 2.17 or 2.08 ? I have seen a few folks have issues flashing 2.17 builds because they are still on 2.08 software and never updated to the latest...
When I look under "About phone" it says my software number is 2.17.
I've done the RADIO Only update, other than that I haven't done any other updates. I know there's the software update thread but I was hesitant to do it because I wasn't clear on what it was doing except for the RADIO ONLY update. I don't want to update my HBOOT to 1.5 lol
Bump? To the top!
Are you flashing a different kernel with your rom??? Also you should flash the aio that freezas or haux put up because I'm taking a guess here but I think your running a newer base Rom with out the updates and from what I've read that can cause some issues. Here's the hboot link that haux posted flash the one with out the hboot. I've personally flashed both of theese zips without issue. Also you should "IMO" not ever use Google to restore your apps or data. It has been know to cause system conflicts. I've never used mybackup so I can't comment on that but I'm sure its better than Google Lol I'd recommend using tb or tb pro. Also I'd recommend only backing up really important apps and just reinstalling the rest to avoid conflicts in the future. Hope this helps.
http://forum.xda-developers.com/showpost.php?p=21441428&postcount=403
Also after you flash that you should do this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
That should help with the issues. Hope it does.
#Root-Hack_Mod*Always\
The first link I get this: "Valid download request check failed.
Please click here and try your download again."
I just did this about 20minutes ago before reading your reply: http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Do you think that is the same thing and sufficient for what I may be missing that's causing it? Next I'll do an SD card wipe if it continues
Are you trying to download this from your phone ??? If so try a pc. Also i have the zip if you cant download it. However I just tried it and the link works. Remember download the non hboot zip. Also if your trying from your phone use the stock browser and open up the settings menu and uncheck mobile view to see if that will allow you to download the zip. Also the first link I posted is a more up to date zip than the one you flashed.
#Root-Hack_Mod*Always\
incarceration said:
When I look under "About phone" it says my software number is 2.17.
I've done the RADIO Only update, other than that I haven't done any other updates. I know there's the software update thread but I was hesitant to do it because I wasn't clear on what it was doing except for the RADIO ONLY update. I don't want to update my HBOOT to 1.5 lol
Click to expand...
Click to collapse
If you have s-off on 1.4 you can update to 1.5 without losing s-off. That's what i did, used htcdev method to unlock bootloader and retained s-off. I used revolution to get s-off originally.
And you probably need to flash all the 2.17 stuff i used a zip that had everything in it found here : http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Hope that helps
Updating with the update I linked seems to have worked!
Thanks guys for the help
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 own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance