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.
Related
I have the HTC g2 tmobile phone. I have just gotten into the flashing/modding scene, and am having a blast tweaking the phone. I have been trying a lot of roms in the past days trying new ones I like or may not like. Anyway I had the Cyanogen nightly rom on there before I flashed with the virtuous sense v2.0. Everything seemed good until I tried unlocking the phone after the looong reboot. Now when I unlock it I get a lot of force closes. Specifically for messages, and media, then the phone just reboots. Keeps doing the same thing over and over? Any help? If I could just figuire out a way to reboot into recovery and flash w a diff rom, or is there something missing since Im getting the FC from a few things? Thanks a lot!!
hi wtfd00d, if u new to flashing rom and wanna flash a stable rom, try keep yourself away of any custom with name "Nightly/Nightly build" because Nightly build, although is kinda ahead of time, is still in development build and merely for testing. try flashing other rom if you would.
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
debinnv said:
Okay, I have gotten so blasted close with getting a custom rom on this phone. I can get them installed now and they are wonderful I tried gummy and aokp but for the life of me I can not get data to work I can not make or recieve phone calls. I am in roaming all the time too. I have gone through all settings and scoured the forum and I can not find an answer anywhere. Am I missing something totally obvious here? Does anyone maybe have any suggestion? Thank you guys for your help. It's just frustrating that I am so close.
Click to expand...
Click to collapse
What is the status of your Photon currently? Assuming it is rooted and unlocked, running what rom? Please provide info on what rom you are on now, which one you flashed from, and what process you used to get where you are. The more info provided the easier it will be to help.
Well lets see, currently I am back on stock, but here is what I did. I rooted, unlocked, installed CWM 5.0.2.7 I also flashed jokers recoveryv3 ( I follow QB's videos) So then I installed the gummy rom using this process. Format system, format data, format cache, wipe cache then dalvik cache. flash rom, flash rom again ( now I did not reboot into recovery after I flashed the rom the first time) I just went straight to install rom again. flash gapps, fix permissions. Reboot up and good loving it all. Waited 15 min then rebooted again. That's it. So I am at a loss. Thanks for help if you need any other info please let me know.
Oh I am on 2.3.4 with 198_7 also
In your system settings did you have "home only" or "automatic" selected for your roaming settings? For a lot of these roms, "automatic" is forced roam. And then if you didn't have roaming data enabled, that would explain why you were constantly roaming with no data.
Sent from my MB855 using XDA
Thanks so much .
I did have automatic checked but I did have roaming data enabled also. I flipped it around too with home only. I am truly beginning to think my phone is just plain "off " who knows. It's a shame though, I mean not that stock is bad on this phone but the custom roms are so much better imo. This is the first phone I have ever had a problem with. I have been flashing phones for years. Think I started with a HTC Mogul. That was a solid phone LOL
Does CM7 work for you? If it does then I reckon flashing that and setting it up, then instead of doing a full wipe keep your data and flash CM9 based rom over it, fix permissions and take it from there.
I have not tried CM7 but I can, sure can't hurt to try at this point. Thanks, I will give that a try tomorrow.
Have you tried *#*#4636#*#*? Sometimes flashing changes the radio in that menu. Be careful though, changing something can really Bork your phone. It should be on cdma prl I think
sent from my CM7 MoPho
Deb, my photon has never been kind to me with the 'flash twice' method. It always results in no data. Try cm9 again, but this time wipe cache, system, data, and dalvik, install version 3.1 of cm9, boot into it, reboot to recovery, wipe cache and dalv, then install the latest cm9 version. Always works for me. Good luck
Sent from my MB855 using XDA
Morning all, your all are great. Okay so I am ready to start again. I'm at stock right now so I need to get her all set up again. (Yes my phone is a she) Acvice, I am going to try your method first will let you know in a bit.
Looks like joker's site may be down so I need to try and find the 2 cm9 roms
I have this rom saved already on my computer
beta-0.6.9.1-cm-9.0.0-RC0-sunfire-UNOFFICIAL-signed.zip
Wonder if I should try that one or just wait
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
debinnv said:
After I install CWM 5.2.0.7 do I also need to flash joker's v3 recovery?
Click to expand...
Click to collapse
You don't have to, but I recommend it.
Sent from my MB855 using XDA
I think th3bill has 0.3.1 in his fixes thread
http://www.mediafire.com/?y7no1r460d4o8zf
sent from my CM7 MoPho
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
debinnv said:
Thanks, will also do jokers and thanks for the link bullfrog. dl'ng now
Click to expand...
Click to collapse
Glad someone provided you with that 3.1 link. Looking forward to see if it works out for ya.
By the way, you will know it worked if when you boot up in 3.1 you have working data. Flashing the newer version after that will essentially just update everything.
Deb, I take it the flash of 0.3.1 didn't work? Did you have data and then lose it when you flashed 0.6.9.3? What were your exact steps. I just rooted/unlocked and flashed my f-in-law's new photon and it worked just fine. Lemme know what you did and maybe I can help more
sent from my CM7 MoPho
Thanks bullfrog that's nice of you but honestly I'm good now As you know.
I didn't even try to install 0.3.1. I kept thinking about it, seeing I had no luck with 2 others previously so I decided to go the MIUI route and I'm a happy camper with that one. I am a flashaholic for sure, as we all are here. I am thinking though, I am gonna just be happy with where I am at for now. Of course I will most likely decide to give another rom a try at some point.
Of course I am already eyeing a few Samsung Epic touch's on ebay. I hear that one can be a brick just waiting to happen....weeeee I am having way too much fun
I'm glad you made it to MIUI. if you ever want to try cm9 or and of the similar ones (aokp, gummy, paranoid) I would suggest flashing that 0.3.1 first, then updating to the latest cm9, then flashing the variant
sent from my CM7 MoPho
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
beholder121 said:
Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
Click to expand...
Click to collapse
All right bro, so it's good that your phone isn't bricked, and it is just slow, so that's the first good part. I'll give you a couple of steps to help your EPIC (because 3D is epic) phone get into the fastest zone possible.
STEP 1) Flash a well-built, not in beta stages, stable rom like NegaLite-BluRom (/showthread.php?t=1745093)
STEP 2) Flash a stable, overclocked (for you) kernel. The best options are Mirage and ButteredToast. Those are the best and most common. DON'T FLASH THIS KERNEL WITH RECOVERY. Install Flash Image GUI apk on your rom (if you can't install it because of huge lag, try the adb method-check out a list of adb commands)
STEP 3) After flashing and rebooting, install an CPU manager of your choice (CPU Master is free)
STEP 4) Overlcock your phone to your need (this is probably your problem
STEP 5) Enjoy your lag-free phone.
*********************Additional Info:
NegaLite supports 3D (just check out its awesome 3D boot animation)
Its IceCream Sandwhich
It can be flashed with S-ON using 4EXT (install this before installing the ROM)
If possible with you lag, backup all your data and contacts using Titanium Backup (save you some time later)