Im currently on the original leaked USCC Froyo rom and am have alot of issue. I was wonders...
a. should I reinstall this rom to fix issues
b. will I need to revert back to stock, root, install clock work then upgrade?
c. Is there alot of people having issue with the froyo build?
issues im experiencing are lag, freezing, issue where standby button randomly takes screen shots, and a few other random issues
what should I do?
First thing I would is redownload the rom and reflash it. That is usually the easiest fix. Are you still having problems? Will try to help you where I can!
K ill redownload it and reinstall it and see if it helps
Reinstalled leaked froyo plus I installed the red CMW and voodoo.
Havent played around to much but I have noticed it runs alittle faster but thats prolly because the lagfix. still having some freezing though
What exactly is freezing? Certain apps or when you try to do certain things?
its freezes in both some times it freezes when im trying to play music sometime it freezes when im texting sometimes it right when the phone boots. it seems completely random and never had any of these errors on enclair with CMW and voodoo.
You may want to try a reset on it next. Make sure you back up everything with titanium first tho. Factory reset option in recovery. You may have to do this after a reflash tho. You may also need to wipe the dalvik cache before a new flash too. Those are the things I would try if you are still having issues.
Also be careful which things you back up with titaniun, I've read restoring certain data onto a new rom can cause issues like that
Sent from my SCH-I500
thanks for the replies I just went ahead and installed the newwer E16 rom which is running much better
So, I've been using Coredroid roms since rooting my phone and everything was perfectly fine. I've switched between other roms and ultimately concluded that I preferred the Coredroid roms. Everything was running great on version 7.6. I installed version 7.1 and once my battery reached 30 percent it started restarting over and over again. So I flashed back to the backup I made of 7.6, it seemed okay for about 20 minutes and again started rebooting it's self. So now I'm putting version 8.0, during the setup it reboots it's self. What can I do about this?
Completely wipe via recovery. Go to mounts and format data,system,catche then factory reset and then flash the rom.
Sent from my Desire HD using XDA App
You should move this to Q and A...
But on a serious note try doing what the person above said and if that does not work(it most likely will) then try to remove the battery for a few minutes...then when you turn it back on check the temperature of your battery...
Possibly your device is getting to hot and is shutting off as a safety precaution, are you overclocking higher than 1500?
if all else fails hit with a hammer j/k
Thanks for the help guys. I did a full wipe as said above and installed coredroid 8.0 all issies have stopped. Thanks a ton, and for the record i was not overclocking any more than what cimes with the rom its self. No adjistments made by me.
Sent from my Inspire4G using XDA App
Glad you got it working. Please post any further Questions in Q&A
Thread closed
Hello XDA,
Sorry for the long post but I am desperate!
The first ROM I ever flashed was CM 10 M2 which ran well and went without any problems. For this I used CWM. I found a stable nightly early in December and decided to update. I also wanted to store my backups on my external however, so I switched to TWRP and created a new backup of my stock TouchWiz rom using TWRP then backed my CM10 M2 up just in case. I flashed the update without wiping the data (factory reset) but did wipe the dalvik cache. This worked fine; all my apps were still there as well as my background. So when GooManager told me there was a 10.1 update for my Rom I thought why not try it out. I figured this was a big update so I wiped dalvik and did a factory reset. After flashing I ended up in a loop of "com.android.something or other has stopped" which turned into "setup wizard has stopped". The homescreen would not load. Fine. Booted into recovery last night after this and reinstalled my latest backup of the nightly I had been using for about 20 days. Seemed OK but the "android activation" screen was taking forever so I pushed home, plugged my phone in and passed out. I Woke up this morning and tried to send a text but it wouldn't send. Tried to call and I couldn't. Now I have restored every recovery I had (Stock, M2, Nightly) multiple times and same problem except that in stock I get a roaming charge warning. I was sure returning to stock would solve this. Does anyone know what I can do? Im not sure exactly how to factory reset but am willing if thats what it takes.
Thanks a ton!
Pups
Try here: http://forum.xda-developers.com/showthread.php?t=2065285. It has worked for several people.
Quick background - unlocked, and rooted months ago. Clean Flashed CR5.6 ten days ago (first and only ROM flashed). Flashed WaWasabi theme few days later. Yesterday morning I flashed a mod that broke Wasabi theme. I reflashed Wasabi, still broken. Each time clearing cache and Dalvik. Dirty flashed CR5.6, clearing cache and Dalvik again. Worked fine. Flashed Wasabi theme, worked fine. Did a full charge. Played on my phone to 1am without a problem.
Went to bed with the phone next to me, it was on and not hooked to a charger. Heard a slight buzzing sound on and off. Looked at phone and it was boot looping. It gets to Verizon and 3 bars, then boot loops.
So does this mean I have to Odin? Never had to Odin so I'll be researching that now. Thanks!!!
I would restore my nandroid, that should fix you right up.
If you don't have one, Odin time.....
Either that or try a clean flash of your ROM. If you think that ROM is bad, you can also always download a different ROM to your SD card using a computer and clean flash that.
rpz3.14 said:
Either that or try a clean flash of your ROM. If you think that ROM is bad, you can also always download a different ROM to your SD card using a computer and clean flash that.
Click to expand...
Click to collapse
Thanks guys. I couldn't get into recovery VolUp+Power+Home for some reason, not matter how many times I tried. Finally worked and tried the lazy way of clearing caches, but that didn't work. So I did a clean install and it seems to be fine again. Now for the rebuilding everything part that I really don't like....
But I'm concerned about why it just started boot looping out of the blue.
If you have a nandroid, you can go to backup/restore and do advanced restore of data and it will out everything back the way you had it on your clean install.
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)