Database Info

[Q] HELP flashing kernel PLEASE

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

[Q] cyanogenmod7

First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes

ant_wailes said:
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
Click to expand...
Click to collapse
You or anyone wouldn't happen to know off hand if the kernel is UVed or OCed? This sounds like a UV or OC problem. Its an easy thing to fix if it is and I find that's is always best to rule out the easy stuff first! Some phones don't like to be UVed or OCed at all and freezes like this sometimes are caused by exactly that, UV or OC.
edit: and oh yeah, WELCOME! If you really like CM ROMs, give absolution a try (at the very least, if you or someone doesn't know if the kernel is UVed or OCed, you're be using a ROM I'm familiar with and if the problem persists on this ROM, diagnosing the a UV or OC problem should be fairly simple and I'll know how to get that fixed quickly for you since I haven't used the straight CM ROM in quite some time!) Actually come to think of it, did you check the md5 number? you could have downloaded a bad link causing a bad flash. It's rare most of the time but I have seen it happen..

If you havent downloaded any apps and dont mind reflashing the ROM just down load the full wipe place in ROOT (No Folder) of SD Card go into recovery.
Full Wipe (DO NOT RENAME AFTER DOWNLOAD)
http://www.megaupload.com/?d=CJPE5CB7
1. Choose zip from SD Card (Full Wipe 1.5) and Install
2. Choose zip from SD Card (Cyanogen ROM) and install
3. Reboot system and enjoy.
I dont like to do the wipe cache, wipe dalvik whatever method, the zip 1.5 does a full wipe all on its own. Its an EXT4 Wipe so I use it for all EXT4 ROMS that I like to try out.
!!!WARNING: When you flash the full wipe do not exit recovery without installing your ROM. So make sure that when you enter into recovery thru Rom Manager to reflash make sure that you have both (Full Wipe Zip) and (Your ROM Zip) on your SD Card before installing.
I tried cyanogen and completed hated it. Absolution is the Bomb!!! But to each their own flavor.
ENJOY

@reponse
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes

ant_wailes said:
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
Click to expand...
Click to collapse
Not a problem man! Be aware though with the 1.5 wipe that it DOES format your system and data to EXT4, and if I'm not mistaken if you make a back-up on EXT 4 and then format back to EXT 3, it will not work and the same applies for vice versa. If you do end up trying Absolution just drop on by the Q & A if the freezing problem persists, I or one of the devs will try to give you hand the best we can..feel free to PM if you go with Absolution

So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!

ant_wailes said:
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
Click to expand...
Click to collapse
No, if you use the full wipe it pretty much just does the wipe data, wipe cache and wipe dalvik cache in one flashable zip. I typically use the 1.5 then wipe data, cache and dalvik cache. It is completely overkill and really not necessary but I do it just the same. No, EXT4 should no cause a problem. I'm pretty sure that almost all the ROMs are now EXT4 supported. I believe it would say it if it wasn't at this point. I know the major ROMS (ARHD, CD, Bindroid, MIUI) are all compatible with EXT4. The only issues you will find with EXT4 is the issue I mentioned in my first post and if you want to use gene's tool to unroot.

Welcome to xda and yes I had the same problem I was setting up setcpu and I sneezed and I accidentally pushed it all the way over to 1.9 and my phone didn't like it it just froze...I was worried :/ so I turned my phone back on and went into setting and forced setcpu to close (mind you it took a few restarts lol) but yes I had let it reset itself and now it's working again I just need to remind myself to do a nandroid once a day xD hehe
Sent from my Inspire 4G using xda premium

No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium

Reinaldo33897 said:
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I believe there is a 1.3 wipe that formats to ext 3 again, just in case the OP wanted to format to ext3 before flashing a new ROM as opposed to flashing a new rom and then having to wipe and then flash again.

Cool Thx I'll do s search for the 1.3. It be good to have.
Sent from my Inspire 4G using xda premium

Asus transformer tf101 going crazy

I have transformer tf101 (Honeycomb 3.2.1 + 16GB + Dock) that I purchased in August 2011. For first 6 months I was on stock ROM and everything was working fine. After that I flashed Android Revolution HD 2.2.0 on my tablet and then it started behaving crazily . Whenever I open browser it will automatically start zooming in/out, scrolling. It will totally go haywire and will start clicking left/right.
I searched on net and found that some of other unlucky guys are facing the same issue . I have attached a .txt file that contains the link to you tube video depicting the problem.
I have tried many ways such as using superwipe script and then reinstalling the ROM's. Even, I have tried with new ROMS(ICS one's) that are there but still the problem does not seem to go away. I have searched a lot but could not find the solution to this issue. Can somebody please guide me how to get rid of this problem. I believe this is the best android forum where I am hoping that someone will help me with this problem.

This is really basic but have you tried cleaning the screen?
Other then that, have you tried going back to a HC rom and see if you don't have any issues. I understand you want the latest and greatest version rom but to determine a fix and narrow down the problem maybe you should try all the alternatives.

Thanks for replying. I had cleaned up my screen and there was not a single app/widget on my homescreens. I flashed back to HC ROM but still the problem persist . I have tried all ways of flashing th ROM's but still the problem doesn't seem to go away. I have not tried the stock ROM for HC that came with my tablet (i didn't take the backup when I flashed new ROM).
Looking at the issue it seems to me as if this problem is software related rather than the hardware.If this would have been hardware related then I should have got this on day1 of my purchase.

stryke504 said:
This is really basic but have you tried cleaning the screen?
Click to expand...
Click to collapse
I think he meant literally "clean the screen." Like with a towel and some cleaner.

typci said:
I think he meant literally "clean the screen." Like with a towel and some cleaner.
Click to expand...
Click to collapse
And dont forget to wash your hands (Im serious, that actually affects the responsiveness of the screen)

I cleaned my screen (Literally ). The problem is still there . Can it be because of the browser. I am currently using Dolphin HD browser for my browsing. I will probably install stock browser and will check with it.

Your text file is rubbish too...no link, it's actually the HTML code for an error 404..which is funny.......not only is it not a working link, or even a link at all, it's a 404 in HTML..LMAO

Sorry for the bad attachment. I have the link.doc containing the link.

Yesterday, I tried with the stock ROM and everything was working fine till the point I connected my tablet to Wifi and upgraded my Google Market to Play store. As soon as the app was updated the same problem started recurring. Now I have uninstalled the updates for google play store but the problem is still there. But the good part is that the frequency of the random zooming/clicking has decreased and it happens in browser only. Earlier it was happening in all the apps. Can somebody please direct me to the link to US stock ROM (for HC 3.2.1). As of now I am running WW_ stock rom. I just want to try out the same with US_ stock ROM as well.

First of all, don't use super wipe script. Just wipe normally with CWM.
Do these options in CWM
1. factory reset/wipe data
2. clear cache partition
3. wipe dalvik cache
4. mounts and storage -> format /system
5. mounts and storage -> format /data (this is done by factory reset but just to be sure)
Get the official ICS rom from Asus' website. US or WW doesn't matter.
Flash it with CWM after doing the wipe procedure above.
Don't let google sync or anything restore any kind of back up.
If the same problem happens again, you got a problem that requires RMA.
Honestly it already sounds like you need to RMA but you should make sure before wasting money and time on RMA.

I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
I have a big problem with RMA. I purchased my tablet in US and so it has North American Warranty. I am not residing in US. Thus for RMA, I have to ship my tablet back to US which will be expensive as well as an overhead . So I am planning of trying all the possible steps before I have to ask the Asus support in my native country. Please let me know if you know any stable version of Stock ROM. I read and found that some of the stock ROM's are having serious issues with Wifi/GPS etc.

harshbedi said:
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
Click to expand...
Click to collapse
Something could have gone bad during flashing.
What version of CWM are u using?
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
harshbedi said:
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
Click to expand...
Click to collapse
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.

I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .

harshbedi said:
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
Click to expand...
Click to collapse
i would first get on the newest version of recovery:
http://forum.xda-developers.com/showthread.php?p=16557195
it is touch based, but i just went into cwm and the regular method of volume and power keys work fine. AND you have to store the rom on the internal sd card in order to flash, it can't access the external card once you update.
and personally i'd wipe EVERYTHING like 3 times seems kinda of the standard.. i'm super ocd so i wipe it all 5 times before i flash.. might want to pick up an ASOP rom like
EOS:
http://forum.xda-developers.com/showthread.php?t=1520764
or KANG:
http://forum.xda-developers.com/showthread.php?t=1542302
see how that works.. could always pick up the stock ASUS rom though
FYI: to flash those new EOS and KANG roms you NEED to be on that version of cwm i linked

I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?

harshbedi said:
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
Click to expand...
Click to collapse
All this could have been caused by you never wiping cache and dalvik cache.
Yea, download the ICS firmware from Asus website. It will be in a zip. You extract it once. It will have another zip. That's the flashable zip.
You flash it in CWM like you would do for any other ROM.

Yes, I never wiped cache and dalvik cache.
I will check this today and will post my observations. I am keeping my fingers crossed and hoping that this should solve the problem.
Thanks for the info.

Thanks horndroid for the lovely info...It worked.
I cleared the cache and dalvik cache and then I flashed the new revolution 3.2.0 (ICS) Rom and as of no complaints. I have been using the tablet continuously for last 3-4 hours and no issues as of now. I am hoping that it continues to work the way it is functioning right now. I am loving my transformer again . I will use it for few more hours and will update my observations. I am still keeping my fingers crossed.
Moreover, Revolution 3.2.0 is awesome(Thanks to Mike and his team). Very stable and the GPS is awesome. Sitting in my room it acquired my position(No Wifi) within seconds.

horndroid said:
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
Click to expand...
Click to collapse
Yes. This is worth pointing out again and again.
Most roms (in my experience) wont even boot unless you wipe cache and dalvik.
And the roms that do boot runs like ****.

Now I have used my tablet for 16 hours..No issues..Running perfectly fine. I believe wiping cache has solved the issue.
I was reading about dalvik cache and came to know that during boot Android always create this cache (if it is not there). So if this problem comes again, can I wipe the cache and dalvik cache without flashing a new ROM. Is this advisable?

no keyboard on nexus s

I recently bought a nexus s and once rooted the keyboard dissapered. It was fine until i flashed a rom unsuccessfuly, then turned the phone off. Once turned back on the keyboard was no more. If anyone could help me find a zip. to flash or a way to put a new keyboard on the phone I would appreciate it. the phone is basicly useless without the keyboard now, ive tried recoving to factory condition, flashing from an earlier point, and so forth. Please help!!!

You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2

jojoost said:
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Billchen0014 said:
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
Click to expand...
Click to collapse
Dictionary http://db.tt/3echUtSP and IME: http://db.tt/EUAXXcsR

re: i flashed gapps
Sent from my Nexus S using Tapatalk 2[/QUOTE]
I flashed a gapps zip from the site you linked me to and now when the phone turns on it says setup wizard is not responding and give me the option to force close. Nothing happens from that point its just stuck in a force close loop. I hope to god i didnt brick this thing. Is there a way to fix this problem? I didnt backup before flashing gapps and ive tried to restore the phone and wipe it clean but no luck. Any help would be greatly appriciated because i just got the phone, mainly to use it as a fun project seeing as smartphone customization has become my new hobby, and Im usually very good at it but now I am just afraid ive bricked the phone and I bought it unlocked so i paid a fair amount of money for i. Please help if there is a solution. Thank You,

Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).

Thank you
Oogway13 said:
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Click to expand...
Click to collapse
Thank you very much, I followed and executed your instructions and now im running ice cream sandwich 4.0.4. not bad from going from almost a bricked phone to running one of the best versions of android. I downloaded offical roms this time instead of custom ones, first a version 2.3.4 and a 4.0.3, flashed the ics rom first and worked like a charm. Thank you very much, even got an update 5 min after i flashed the rom. You saved me 200$ and the embaracement of having a worthless phone. Im sure ill have more questions in the future, so glad there are ppl out there with the same passion for smartphone customization that i have. Much obliged. Omar

[Q] P5110: Random Rebooting (CyanogenMod 10.1 - RC5)

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)