Ok so I recently had two evos flashed to boost one works flawlessly the other for some reason the camera doesn't work I went into apps and the one that works is 4 kb the other says 0 kb....somebody suggested changing roms I did it and it fixed camera issue. Now the phone won't receive media messages......any ideas? Please help.
Seems most likely its an issue with that phone. I would try a complete restore, and then reroot and try again. If you have the same issue then likely something in the phone isn't agreeing with boost.
Your post is very vague. What rom did you flash and is it Sense or AOSP? Did you do a complete wipe and clean install?
posting & replying via the XDA Premium app
Sense yes I did a clean install and wiped everything I'm pretty sure they were since but here's a list of em The roms I've tried are plutonium poison editon, Azarel x v 4.0 ,calkulins evio 2 Rom v 1.8 , kings unleashed ultra blakk r3
And was the camera working before you flashed any new ROM's?
No camera worked before it was flashed to boost tho
Related
Guys I have a quick question. I'm currently running Supersonic Sprint stock rom but I'm rooted and and my 32GB card is partitioned correctly. My question is should I flash to B1 currently available now or should I wait for 1.1 to come out today or sometime tomorrow? Do I need to wipe extra stuff upgrading to 1.1 if I have B1 installed?
Thanks
MikeF0209 said:
Guys I have a quick question. I'm currently running Supersonic Sprint stock rom but I'm rooted and and my 32GB card is partitioned correctly. My question is should I flash to B1 currently available now or should I wait for 1.1 to come out today or sometime tomorrow? Do I need to wipe extra stuff upgrading to 1.1 if I have B1 installed?
Thanks
Click to expand...
Click to collapse
well thats up to you on flashing......its def not for the person who hasnt flashed alot before. It takes time to load.....some screen issues and no custom kernels yet. Some apps force close but that being said if you can deal with some of the quirks the rom has its awesome. Make sure to read the posts and understand whats working and not. I always go the fresh install route on every update just to make sure.
I'm a noob also..
I have used VIRuS ROMs and I like them alot. I am currently using his Revolution B1 and it does have a few bugs but I look past them. Its a super ROM. My biggest bug is the lockscreen but it seems to have fixed it's self. I had a hard time unlocking screen but followed what someone posted (let it sit for like 5 min) and it fixed its self. VIRuS just posted some thing in the Dev form
Just saw...
VIRuS just posted that he got ahold of another HTC Sprint leaked ROM.. it's named the Shooter.. he's working on porting it to our EVO.. this one sounds more like the EVO3D than the Kingdom ROM. Cross fingers..
Hello everyone.
I just have one small question regarding the following ROM:
http://forum.xda-developers.com/showthread.php?t=1054250
Anyway, I LOVE rmk's ROMs. I'm an avid user of Virtuous.
When I found out about the HTC Desire Z Gingerbread ROM leak, I picked up rmk's slightly tweaked version and overall, I was thoroughly impressed.
When I found out about the T-Mobile G2 ROM leak, I went to rmk's thread and picked up the ROM. But after I was done flashing it, when I was about to go through the standard Google activation process, I was bombarded with several force close notices that kept me from proceeding with the startup, among them this kept popping up.
"Sorry, process com.android.phone is not responding"
Can anyone tell me what I can do to fix this?
Before, I was using Cyanogenmod 7.0.3, if that is of any help.
Do I need to come from a Sense ROM or does it make no difference if I'm coming from an AOSP ROM?
Maybe because you have a DZ not a G2?
Have you tried reflashing and maybe fix permissions?
-Nipqer
It sounds like you need to win and flash the rom agian. I recommended using amazinglarrys superior when moving from one rom to another. And I would give this http://forum.xda-developers.com/showthread.php?t=1076786version of the tmous gb rom a go it has had a bit more work done to, and includes an oc kernel and its gets rid of a load the tmobile bloat. I have been using it on my dz since it was released and have no problems what so ever.
[sig]My mission is to hit 1000 posts by 23/05/2011[sig]
Did you not wipe before switching roms???
Sent from my T-Mobile G2 using XDA Premium App
I flashed my Virtuous 1.0.2 backup, wiped, then flashed the ROM from rmk40's thread.
It's getting along just fine.
Sent from my T-Mobile G2 using XDA App
Im currently running 1.9.16 miui an for some reason my mms arent downloading so i can view them can anyone help?!
sent from 2.3.3 rooted evo ;D ™
Have you tried re-flashing the rom? Did you install on a clean wipe?
MIUI will cause problems like this, if it's not a clean install, just like the above poster stated.
I had a similar problem, then realized I'd forgotten to wipe, so I did that an reflashed, no more issues!
Mistress of Mischief
I always wipe by ill try it again thanks
sent from 2.3.3 rooted evo ;D ™
i have this problem too. did clean wipe and all that shazz and still having the same problems. =(
Yeah im having the problem still i was wondering if the was like a falshabls zip that would fix it
sent from 2.3.3 rooted evo ;D ™
I have the same problem except I have CyanogenMod 7 the latest stable version.
I've noticed mms issues on MIUI 1.9.16 as well. I haven't really looked into a fix since I don't use mms very often. I can send them but I either don't receive them at all or they don't download. I've been having issues with downloading through the stock browser as well, so I feel that the two are related.
I have the newest release downloaded, just haven't flashed yet. If I have issues on that one I will probably roll back to 1.9.2 or 1.9.9. I suggest anyone else with the problems to do the same. I installed on a clean wipe, so I know that isn't the issue.
Sent from my Evo + MIUI using Tapatalk!
I got annoying and strange problem. I've been running Andromedus Test Builds, but after 75 bulid I lost wifi, so I installed CM9 beta5 and everything was fine. Today camcorder did force exit and didn't want to run properly. Did nandroid, upgrade to beta6 w/ kernel 7 and lost wifi additionally. Then did recover of beta 5. Nothing changed. Now I'm running again Andromedus Test Build, but very low number - 64. And it seems to work right. But why, for sake, any new upgrade goes crazy? Any ideas?
Have been trying different kernels. DZ unlocked by htcdev (so every one must be upgrading manually).
Hope my english is good enough to understand me
Those are still beta builds - expect bugs if you use them
Sent from my HTC Vision using xda premium
What do you mean by lost wifi? It doesn't toggle or just doesn't find your network?
Also, I assume you're doing full wipes between roms as the test builds are odexed and the cm9 unofficial rom isn't. If you don't wipe you're gonna be boned..
Sent from my HTC Vision using xda premium
This is a general note for those interested in a fairly stable ROM for the US version of the (CDMA) Wildfire S running 2.3.5 (Marvelc.)
After trying several other ROMS, some supposed to be stable with CDMA but were not, I can state the MIUI v4 - 2.8.10 by Henry_01 DOES work with my US Cellular WFS after updating from v2.3.4 to 2.3.5. However, I had problems when installing via cwm recovery for reasons I cannot fathom, but everything went smooth after reverting to twrp 2.2.2 and doing the simple wipe thing...
Just for the record... Yes: Both Data and Wifi worked straight from 1st boot.
Nice Work Henry-01 ^5
UPDATE:
MIUI v4 failed... I couldn't find a fix for the GPS, I'm guessing because I couldn't find an option in Settings to activate GPS... but the ROM was still stable otherwise.
I will try other ROMS and add my findings here as I go until I have something working at least 90% I don't expect 100% as these ROMs need to be tested and continually developed, especially for marvelc.
Currently running: cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc
This appears to have updated my android version to v4.0 ? It doesn't come with GAPPS so I installed myself using goo.im goomanger from there site v2.2.
This was yesterday. Checked and working:
Wifi, Data, GPS, SMS, Phone.
Camera/Camcorder and browser. (Browser seems a little slow and glitchy... but that may have been down to the connection... not sure yet.)
I will test further today...
SuperSu, Link2sd,
gryffon said:
This is a general note for those interested in a fairly stable ROM for the US version of the (CDMA) Wildfire S running 2.3.5 (Marvelc.)
After trying several other ROMS, some supposed to be stable with CDMA but were not, I can state the MIUI v4 - 2.8.10 by Henry_01 DOES work with my US Cellular WFS after updating from v2.3.4 to 2.3.5. However, I had problems when installing via cwm recovery for reasons I cannot fathom, but everything went smooth after reverting to twrp 2.2.2 and doing the simple wipe thing...
Just for the record... Yes: Both Data and Wifi worked straight from 1st boot.
Nice Work Henry-01 ^5
Click to expand...
Click to collapse
you should install twrp 2.3 with goo manager
icu64 said:
you should install twrp 2.3 with goo manager
Click to expand...
Click to collapse
Tried twrp 2.3 but it wouldn't work... hence using 2.2.2..
+ goomanager is included in MIUI v4 ....
I'm just sharing my own experience with this particular phone/rom/etc...
Can you flash cron mod with that recovery?
Sent from my Marvelc using Tapatalk 2
icu64 said:
Can you flash cron mod with that recovery?
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
I'm not familiar with "Cron mod" but... I did try the marvelc cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc yesterday, I couldn't get the cm7 or cm9 working while using cwm recovery but never tried the cm9 Alpha9 until now, and of course I used twrp as I find it appears to work great on my device.
Anyway, this alpha9 is to date: The ONLY ROM I've installed on this MarvelC wfs that actually works with wifi/data/gps having no issues, and I flashed gaps by downloading goo manager from the goo.im site.
Now to test and read some more and find out if I have any bugs on this rom.
As I've tested quite a few roms this week... I may at some point start a thread with all roms that I COULDN'T get to work on the wfs US cdma...
jelly bean roms work pretty great, except GPS but if you turn WiFi on (don't need to connect to an access point) it gets you dead on. for me at least. and yes you can flash cronmods int2ext+ with twrp 2.2, so im guessing you can flash the rest as well.
Sent from my Marvelc using xda app-developers app
demi_fiend said:
jelly bean roms work pretty great, except GPS but if you turn WiFi on (don't need to connect to an access point) it gets you dead on. for me at least. and yes you can flash cronmods int2ext+ with twrp 2.2, so im guessing you can flash the rest as well.
Sent from my Marvelc using xda app-developers app
Click to expand...
Click to collapse
For me, the GPS needs to work, for travel. Wifi does get you very close but that is no good when using the navigation to follow a route by instruction. I didn't even realize at first that the wifi did that and thought that the GPS was 'Working' in CM9. Alas it was not... So another failure for me :/
well the only two roms that work flawlessly with our phones is jmz sense and teamblueridge sense. which kinda stinks because they're gingerbread.
Sent from my Marvelc using xda app-developers app