I recently installed MildWild 4.3 (the Oxygen version) on an HTC Desire. Ever since, apps that were running fine with the stock ROM are crashing very frequently (50% of the time or more). Also, twice now I've had the entire phone completely lock up while using the browser. Even after pulling the battery and starting it up again, still nothing - it would just hang on the white HTC screen. I had to boot into recovery and clear the cache (regular and Dalvik, although both might not have been necessary) to get it to work again.
Anyone have similar issues, or suggestions as to how I could fix this? Thank you!
Make that three full-on, phone completely choked crashes now, within a week. Clearing cache partition alone seems to have worked this time, so looks like Dalvik was unnecessary.
Any ideas as to what might be going on, and how I could fix it short of putting an entirely different ROM on there?
Thanks!
I think you just go fot another ROM
Do this steps before install: Wipe data/factory reset, wipe cache and wipe dalvik
Try that one and post then if phone works or not
Sent from my HTC HD2 using Tapatalk 2
gesange said:
I think you just go fot another ROM
Do this steps before install: Wipe data/factory reset, wipe cache and wipe dalvik
Try that one and post then if phone works or not
Sent from my HTC HD2 using Tapatalk 2
Click to expand...
Click to collapse
I did do all those before trying this ROM, so I guess I will have to try another. *sigh* Don't have time right now, but hopefully I can limp by for a couple weeks.
Related
hi,
I am trying to install multiple ROMs on my inspire and see which one is better so far I have installed CM7 and CoreDriod 6.7; I felt CM7 is good and faster however when I stalled CoreDriod 6.7, I am noticing very slow response and my inspire is responding very slowly if I do anything, just wondering if others also noticed samething, ...would appreciate your feedback.
Thanks.
kalva7 said:
hi,
I am trying to install multiple ROMs on my inspire and see how which one is better so far I have installed CM7 and CoreDriod 6.7; I felt CM7 is good and faster however when I stalled CoreDriod 6.7, I am noticing very slow response and my inspire is responding very slowly if I do anything, just wondering if others also noticed something, ...would appreciate your feedback.
Thanks.
Click to expand...
Click to collapse
CoreDroid and CM7 are apples and oranges, however you shouldn't be having any slowdown issues in CoreDroid. The times I've used it, it has been just as responsive as any other ROM. Sounds like you may have a bad flash - be sure to do a full wipe before installing any ROM (in CWR it is the "wipe data/factory reset" option). Personally I also like to manually format the /system partition since the wipe data option doesn't do this (in CWR the format /system option is under "mounts and storage"). I think during installation many ROMs already format /system anyway though before it starts writing files to this partition.
If you keep having problems with CD after reflashing, just build your post count up to 10 and then you can post in the support thread in the dev section. It is a nice ROM worth checking out.
It is also very important to wipe dalvik-cache by going into (from recovery) advanced- wipe dalvik-cache.
Sent from my Inspire 4G using XDA Premium App
I had to flash and wipe coredroid twice to get ride of leftover cm7
Try leedroid its the most stable for me
Mr.Nun.Ya
Keep in mind that Sense ROMs (coredroid) do a lot of restoring on your first reboot. A lot of your apps are being restored, as well as a lot of your settings. It's usually a little slow at the beginning, but if you give it some time it should stabilize itself. If not, then the other guys are right, it was a bad flash or you didn't wipe correctly.
ThEiiNoCeNT said:
It is also very important to wipe dalvik-cache by going into (from recovery) advanced- wipe dalvik-cache.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
True, however that is a redundant step. The dalvik cache is automatically wiped when you run "wipe data/factory reset" in CWR (dalvik cache is stored on the /data partition and the /cache partition, both of which get wiped by this command).
After doing a proper wipe and flash to a new Rom I have found it best to do a full restart a few minutes after after the Rom settles down after the first boot-up.
I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.
I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App
So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App
Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!
Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App
OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App
Ok bizarre problem guys. I have an international 6810 running Paranoid Android 2.13. I was browsing Facebook on Sunday morning via the app when the tablet rebooted mid scroll.
When it boots it gets right to the 'almost loaded' part of the boot animation where the brightness drops a little bit. However instead of booting to android (and if you've cleared dalvik cache the next thing you would see is the 'Upgrading - 1 of 200' messages there), it reboots and does this cycle endlessly.
I can get into bootloader and recovery (which is currently the first one I installed - CWM 5.5.0.4) and I can Wipe Cache fine, however as soon as try to Wipe Dalvik Cache the tablet reboots, which leads me to think there might be something wrong with the Dalvik Cache? This also (obviously) means I'm unable to do a Wipe Data/Factory Reset as that also attempts to wipe Dalvik Cache and causes a reboot.
I am able to flash roms (though I've only tried reflashing PA 2.13 so far and it will not boot with the same issue described above) and other zips successfully (i can run Aroma scripts without issue and have tried the emmc_scan_all_partitions_once.zip without problem (from a Galaxy Note thread and linked to in the 'How to avoid Superbrick' 7.7 thread)).
I'm looking at the 'Superbrick' thread wondering if I need to move my cache to another area but I'm loathe to do so if its something simple!
Anyone have any ideas?
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Uvaavu said:
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Click to expand...
Click to collapse
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Uvaavu said:
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Click to expand...
Click to collapse
I'm facing the same problem with mine. Stuck in bootloop until i wipe Dalvik Cache.
What exactly did you do to make it stop bootloop-ing?
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?
Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.
Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.
jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?
All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app
Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1
I am Having the same prob with galaxy tab2 7.0(gt-p3100)
Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???
nimrod.sixty9 said:
Had a bit of trouble trying to do this last night, which resulted in a few hours lost sleep. I went formatting everything in CWM and realized after the fact, I also formatted the internal SD card. Luckily ADB worked in transferring the zip (learn something new every day).
Anyway, after all said and done, all my apps were still on the phone. This is after formatting and new ROM...
How can I truly start from scratch to make sure this new ROM is 100% fresh and free of any unnecessary apps from previous ROMs?
Also, what would be the best current radio and link to said radio?
TIA
EDIT: I had just realized the issue with Factory Reset/Wipe Data. This one I had forgot to mention as I could never use it as all options said no and the menu was not scrollable. Just decided to try and use the volume buttons and sure enough there was more to scoll to.
That said, would the following be a proper procedure to follow;
Wipe Data/Factory reset
Wipe Cache
Format: System, Data, Cache, Boot
Wipe: Dalvik then Fix Permissions
Install order: Rom first, Gapps second, Kernel last
Reboot
???
Click to expand...
Click to collapse
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2
beneath-a-burning-turtle said:
The method I follow is
1. Wipe Data/Factory Reset (this takes away all your downloaded apps?
2. Wipe system/cache/dalvik (this wipes everything else)
3. Flash ROM, Gapps, Kernel
The thing with android is, even if there are some files left over from the previous ROM, they'll get overwritten with the ones from my new ROM, taking them away regardless. The reason you wipe everything to make sure there aren't any files that won't get overwritten. So basically, wipe everything and flash, and you'll have a fresh new ROM also you don't need to fix permissions after you wipe everything because they'll be no permissions to fix! Lol
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.
nimrod.sixty9 said:
Thank you, good sir! Now running nice and clean!
Still need that newest radio if ya know it.
Click to expand...
Click to collapse
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2
beneath-a-burning-turtle said:
I don't know it offhand but its probably somewhere on the development forums. I just noticed I said "my new rom" in my original post, I meant "the new rom" just in case you were a little confused (probably not but that would've annoyed me if I didn't address it)
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Newest radio I can find is from last year. Maybe that the newest. I know for certain signal and data is a million times better. However, I still have no 4g
And Im having an issue I ned to report about the ROM but XDA wont let me post... :crying: