i was updating my phone yesterday. added the new cwm 3 and a new rom. I was fine to go back to stock so i used the comm rom then when it rebooted I installed amazon appstore, di some customizations. Then I turned of my phone and went to bed. I woke up and my phone was crashing left and right. Launcher 7 fc, amazon fc pretty much useless. I thought it was a bad rom, so I used the evil fascination rom ([ROM][ED01][5/25/11] Evil Fascination v3.6.0 - xda-developers) and did used that. I installed everything back then i restarted same thing. Any advice would be very much appreciated since i am going out of town tomarrow.
midnight93933 said:
i was updating my phone yesterday. added the new cwm 3 and a new rom. I was fine to go back to stock so i used the comm rom then when it rebooted I installed amazon appstore, di some customizations. Then I turned of my phone and went to bed. I woke up and my phone was crashing left and right. Launcher 7 fc, amazon fc pretty much useless. I thought it was a bad rom, so I used the evil fascination rom ([ROM][ED01][5/25/11] Evil Fascination v3.6.0 - xda-developers) and did used that. I installed everything back then i restarted same thing. Any advice would be very much appreciated since i am going out of town tomarrow.
Click to expand...
Click to collapse
Wipe cache/dalvik and try to flash it again. If that doeant work, odin stock and work your way up. There are plenty of how to guide stickied in general.
Sent from my SCH-I500 using XDA Premium App
Just out of curiousity. What is cache/delvik cache
It is my understanding that it is kind of a full system cache if you boot into recovery it is like the third option to wipe it also did you do a full data wipe when installing the new rom's?
Sent using my Evo 4g with Cyanogen 7 nighty 87
Dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. Sounds confusing. It's similar to the prefetch files in Windows.
To delete this you need to have red clockwork and the 'wipe dalivk cache option' is under 'advanced'.
Hope this helped and don't forget to press the thanks button!
Thanks guys for the info. Will updTe u in a minute
Ok. So I wiped cache, then i wiped data, then I installed ef 3.6.0. Still failed. Any other suggestions beside's odin stock, cuz that seems so boring
Try a PBJ Kernel (evil comes with his voodoo 50)
so try 100 of SV voodoo
Related
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
I flash chingys latest version of gingeritis which is VIII .. I had flash the gb radio he suggested and did a full wipe... But when the phone starts up I get no service what so ever I can't even turn the radio off or on.. ...help??
Sent from my ADR6400L using XDA App
Check the md5 of the radio and redownload if it doesn't match. If it matches reflash both. Wipe everything a few times before flashing the Rom.
I have flashed a couple of the Different releases of Chingy's ROM and had not problems other than the FC on weather on the old ROMs. Now that it has been fixed it is literally flawless and smoother than stock with the goodies of GB.
This is what I did and do everytime I flash a ROM. Overkill yes but I have NEVER had a ROM take badly, or not boot up on the tb or droid like so many stories I keep hearing.
My Method:
1) Backup, Backup Backup. Everything. I use Ti Pro only for the stuff I cannot download anymore: Wifi Teth, Music Search and Download, etc. because Restoring old apps is never as good as downloading from the market. I also backup all my texts to Gmail using SMS backup. And Folder Organizer has a backup, and of course nandroid.
2) Boot to Recovery
3) Wipe like you went #3 I wipe once everything once, then wipe Cache, then Dalvik, then Battery stats, the Wipe again. Only once b/c Chingy's ROMs wipe as well. If it was another ROM I would wipe one more
4) Then Update.zip
5) Then Wipe again.
6) Then Update.zip
7) Then boot. (no service b/c the Radio hasnt been updated yet)
8) Then turn OFF.
9) Turn back on holding down and install Radio.
10) Now I'm running my favorite ROM on the tb to date Gingeritis VIII
I still havent rebooted it since I put it on this morning and I have restored all my Widgets, and 150+ apps and 3000+ txts. I have synced with my accounts mail fb and everything. Im also running Sense live weather Wallpaper and Lockscreen widget.
Flawless.
haha i do the same so i thought i was paranoid, glad to see its just precautionary and others do it too
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
First off this is the wrong section
Second yea u need to always wipe everything when switching to a new ROM. I use Synergy and the first boot will always be laggy. Synergy let's your Google account download all the apps that u previously had which really slows the phone down. What I'd do is wipe EVERYTHING. Then flash the ROM again. During setup, only setup your Google account and leave for Facebook or whatever other accounts u set up for later as it may speed up things for the first boot. And then I'd just put the phone down n let it do what it needs to do. Synergy is a fast and smooth ROM. The first boot is always laggy on any ROM that allows Google to auto download previous apps. Hope this helps
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
wetbo529 said:
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
Click to expand...
Click to collapse
Follow these procedures:
- Normally you'd perform a nandroid first after flashing into clockwork recovery, but I don't know that you'd want to do that since the ROM is running poorly; your call (I would anyway)
- Wipe Data I always do this, no matter what. That might sound extreme, but I've never had one issue with any of the three android phones I've owned.
- Wipe Cache
- Wipe Dalvik
- Flash Rom
- Flash Radio (if necessary)
- Reboot
Play with the ROM for a while before you flash a different kernel. You might find one of two things: 1) The kernel that came with the ROM is plenty fast and does everything you need, which leads to 2) The kernel you flashed originally could be the cause of the slowness.
Ir's possible the ROM is the issue, so following the above procedure will rule everything else out. Let us know how it goes.
this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!
Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?
Try wiping dalvik/partition/cache before and after installing the custom ROM
I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk
Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk
the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM
@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk
Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk
thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes
and just a thought, but i keep fixating on the .PIT file. your thoughts?
Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium
if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...
1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition
i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?
I have been running MIUI on an x2 for a few days and I went to use my Camcorder and it crashes. I tried several different ones and it just keeps failing. It starts to record and then does a FC. I downloaded different cameras and they do the same thing. I even tried some different once through downloading the Apks from this device and from the Atrix.
Does anyone have any ideas?
Probably a silly question but did u manually do a reboot, or go into applications and clear the catch and data. Also when you installed the miui did u do the three wipes first?
Sent from my DROID X2 using XDA
Lol good question. I have done these. I can try to reflash it?
Sent from my Milestone X2 using XDA
Lol, sorry if that was obvious but I know I usually over look the easy stuff. I have only ever had these problems when I didn't wipe the data and catch after I flashed
Sent from my DROID X2 using XDA
I am going to try to do that. Thank you for trying though.
No prob hope u get it
Sent from my DROID X2 using XDA
From what I have been able to read its something to do with permission settings for the camcorder. If I can just get help how to change this to the proper settings that would be great!!
This is a bug that has been with the rom since the beginning.
I hope you find a workaround.
If you follow Aceoyame on twitter you can see his progress on the next release based on Dragonkillerz work on cm9. Some are saying this summer, just in time to take some video
Sent from my DROID X2 using XDA
lol, Yeah from what I have been reading I think its about the permissions. But I am trying to figure out exactly what file.
I wanted to give an update. Talked with Ace and he said there will be an update out to fix this sometime in the next week. Great news!
Sent from my Milestone X2 using XDA
That is great news. Good on ya mate.
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
joshahouck said:
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
Click to expand...
Click to collapse
Nand backup your miui and let Ace know of your discovery! He's trying to find a correction
Sent from MB870 W/ Cm7.2 Rc1
SUCESS I THINK YES...