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?
Related
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
kailehu said:
Sorry, I'm new and I understand this is where I have to post. I hope that's right. I've looked everywhere and none of the other posters' responses have helped me.
I have a p7510 which for the moment is rooted stock. I've used other ROMs: AOKP, CM9, CleanROM. They all work fine but recently I tried CM10 and eventually another AOSP JB ROM because I was desperate to exhaust every option. I know about wiping cache, Dalvik and data and formatting system so that's not the issue. I've also switched recoveries and recovery versions, reflashed stock and rerooted, tried again and again between wipes-- I even started to wonder if maybe I just wasn't patient enough but I waited over an hour with no results. Whats the deal here?
Click to expand...
Click to collapse
o-l-a-v said:
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.
An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine :good:
(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
I've got the same freakin' problem on my Wildfire S w/ CM9 alpha 7-rom. Bootscreen for over an hour. Cleared cache, installed rom and then gapps with CWM. Starting to wonder if it's the hboot or something.*An answear for what we noobes (maybe just speaking for myself ) is doing wrong, would be fine*(Would have posted this in the developers thread, but i got >10 posts on XDA...)
Click to expand...
Click to collapse
I'm sorry to hear that but I'm also glad it's not just me, and wouldn't be a huge stretch to call me a newb.
Did you do the following? In order and full:
Make a backup
Format data
Format system
Format cache
Format dalvik cache
Factory Reset
Install ROM .zip file
Install the latest (unless otherwise specificed) gapps .zip
, but as you stated, you've supposedly done all of that. The only other thing I can think of is that the ROM might be corrupt and cause a bootloop. Look at the dev thread to see if others are experiencing the same issue. Also i'd recommend TWRP instead of CWM.
Click to expand...
Click to collapse
Unfortunately, I've tried both recoveries already. I've gone through each step every time and I've never done it that specific order consciously, but I feel like I must have just by chance in all the times I've tried this. I'll try again though exactly like you listed and see what happens. Thanks.
No dice. I'd like to give more info than that but I don't know what else to try.
I apologize in advance for being a noob, this is my first go at customizing ANYTHING android.
I got my Asus Transformer TF300T in January, had some hardware issues with it and exchanged it. I JUST got it back and decided to go custom before i got it all set up and then i would have to start over.
So I followed THIS guide and successfully installed Baked 7, Initially I used CWM as the guide told, but I could not get a boot image backup, so I used the same method and installed the most recent TWRP and it worked flawlessly.. I was unhappy with how the notification bar was at the top, I liked the stock where it was at the bottom. I could not find initial details on how to revert back to stock rom, so i decided to give some other custom roms a try. I was very interested in scottsmods CleanROM, but their website does not have the download anymore(that I could find) and thats where all the links in guides point to. So instead I installed CyanogenMod using THIS Guide. I immediatly noticed problems with this rom. It did not pick up my SD card, there was an error window that would pop up and go away before i could read it. It would not get on wifi.
I did further research into going back to stock, so I followed THIS guide its not directly XDA, but it followed the same style that i had learned previously(fastboot, etc) I did change to the support page of just the TF300T on the asus site, the guide links to the 3g one. I could not find my SKU in my device because the cyanogen rom changed the "Build" number. So I have tried each from the asus site and flashed them and would get stuck on the asus boot screen. I waited over an hour on each one before i decided it was frozen and to move to the next.
I didnt get any of the stock firmwares working. So I reflashed to TWRP, and attempted to go back to baked. I couldnt get the zip to install in twrp. but i was able to get cynogen to install again. It doesnt have the error window thing and the wifi works but still no SD.
I want to go back to stock, or baked if stocks not possible.
Stocks already been tried to the best of my ability, so i tired baked. Baked is on my external SD card, as in cynogen I cant access the internal one to move the files over.
Baked gives me an error saying unable to open zip file.
What am I missing? I cant seem to figure this out. Any and all help or ideas would be greatly appreciated!
well, first off, you went from Baked 4.1 to cyo 4.2, now as i understand it . They moved the file system around in 4.2, and if you want to go back to 4.1 you have to wipe everything, I use TWRP 2.4.1.0 . Now I can understand not wanting to lose everything you've had set up.. Always do a back up before any major Flash. Just incase if your on a rom now thats decent save your files, perform a wipe, flash a rom , Clean rom in the xda threads is what im using.. Running great BTW. lemme know if it helped or didn't... lol Clean ROM Inheritance is a stock based rom. with an oc kernel which makes the tab perform like its supposed to. just be sure if you do decide to flash it you choose a kernel in the installer with T = Wifi, G=3G, 4G, etc. you want the T G
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Goddly said:
well, first off, you went from Baked 4.1 to cyo 4.2, now as i understand it . They moved the file system around in 4.2, and if you want to go back to 4.1 you have to wipe everything, I use TWRP 2.4.1.0 . Now I can understand not wanting to lose everything you've had set up.. Always do a back up before any major Flash. Just incase if your on a rom now thats decent save your files, perform a wipe, flash a rom , Clean rom in the xda threads is what im using.. Running great BTW. lemme know if it helped or didn't... lol Clean ROM Inheritance is a stock based rom. with an oc kernel which makes the tab perform like its supposed to. just be sure if you do decide to flash it you choose a kernel in the installer with T = Wifi, G=3G, 4G, etc. you want the T G
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Is the 4.1 the same as 7? because 7 was the latest version available from team baked.
Edit: wait a sec... i think I understand. You mean baked 7 was 4.1 android and cyo was 4.2 android?
as far as data goes, i've already done all that. i did factory reset, wipe cache/wipe davik thing each time, no bueno. I have no data on the device as it was brand new outta the box. in TWRP, theres an option for wipe data, but factory reset says it wipes data and cache. should i still do the wipe data option instead of factory reset? so... wipe data/wipe cache/wipe davik instead of factory reset/wipe cache/wipe davik?
And also, I'm trying to flash a rom, back to baked from cyo because atleast baked worked. but it tells me its unable to open my zip files.
Do you have a link to the download of CleanROM? I've checked the official threads here and the download links take me to scottsroms.com and their download page only has the nexus10 and nexus 7 along with a bunch of phones.
Talvir said:
Is the 4.1 the same as 7? because 7 was the latest version available from team baked.
Edit: wait a sec... i think I understand. You mean baked 7 was 4.1 android and cyo was 4.2 android?
as far as data goes, i've already done all that. i did factory reset, wipe cache/wipe davik thing each time, no bueno. I have no data on the device as it was brand new outta the box. in TWRP, theres an option for wipe data, but factory reset says it wipes data and cache. should i still do the wipe data option instead of factory reset? so... wipe data/wipe cache/wipe davik instead of factory reset/wipe cache/wipe davik?
And also, I'm trying to flash a rom, back to baked from cyo because atleast baked worked. but it tells me its unable to open my zip files.
Do you have a link to the download of CleanROM? I've checked the official threads here and the download links take me to scottsroms.com and their download page only has the nexus10 and nexus 7 along with a bunch of phones.
Click to expand...
Click to collapse
Wipe everything.. data from 10.1 is not supported... do you not have a useable backup? If you do restore it. Y o u have to be able to put stuff in storage. Or wipe what i told you, and reflash baked if you already have it.
http://forum.xda-developers.com/showthread.php?t=2049322
Clean rom.. download deodex, 3.3. Put it on the root of sdcard0 (first screen when you press storage, sdcard0 ,)
Wipe, in twrp, in the wipe options, cache, dalvik, factory, system, data.. then f
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Goddly said:
Wipe everything.. data from 10.1 is not supported... do you not have a useable backup? If you do restore it. Y o u have to be able to put stuff in storage. Or wipe what i told you, and reflash baked if you already have it.
http://forum.xda-developers.com/showthread.php?t=2049322
Clean rom.. download deodex, 3.3. Put it on the root of sdcard0 (first screen when you press storage, sdcard0 ,)
Wipe, in twrp, in the wipe options, cache, dalvik, factory, system, data.. then f
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Talvir said:
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Click to expand...
Click to collapse
Yes.. which kernel did you choose? You need to flash the stock kernel.. what version of twrp are you using?
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Talvir said:
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Click to expand...
Click to collapse
OK! so I got my tablet working with cleanROM at last!!!
I figured out why the zip files werent opening. for some reason my tab was only able to install from zips DIRECTLY on the internal sd card. whenever it tried one from the external sd card, despite being mounted, it was always unable to open the zip and would fail.
CleanROM got stuck initially because i used the WW version instead of the US version. Once i reflashed with the US version it worked great! had an issue with the start wizard crashing, but that went away after it stabilized. I stared customizing and playing and had no issues other than the SD card notification. That was an option i didnt choose to patch because i didnt know prior how annoying that notification was. it wouldnt get out of my notification window! so I flashed again, with that option enabled so that the sd card didnt bug me in the notification window.
I just got it back up and running, after the second flash with that modification added, and other than the start wizard still crashing(again, i let it sit a while and now it worked) it seems to be working great!
I hope my experiences can help newbies in the future that may have similar issues!
Talvir said:
OK! so I got my tablet working with cleanROM at last!!!
I figured out why the zip files werent opening. for some reason my tab was only able to install from zips DIRECTLY on the internal sd card. whenever it tried one from the external sd card, despite being mounted, it was always unable to open the zip and would fail.
CleanROM got stuck initially because i used the WW version instead of the US version. Once i reflashed with the US version it worked great! had an issue with the start wizard crashing, but that went away after it stabilized. I stared customizing and playing and had no issues other than the SD card notification. That was an option i didnt choose to patch because i didnt know prior how annoying that notification was. it wouldnt get out of my notification window! so I flashed again, with that option enabled so that the sd card didnt bug me in the notification window.
I just got it back up and running, after the second flash with that modification added, and other than the start wizard still crashing(again, i let it sit a while and now it worked) it seems to be working great!
I hope my experiences can help newbies in the future that may have similar issues!
Click to expand...
Click to collapse
So.. which kernel did you choose? You should download the 2.0 kernel installer on the same thread, and choose the Unters tf300tG because you have 3g.. you will find your tablet runs ALOT smoother and faster than stock, but you need to flash the stock kernel first. Its a good way to do kernel flashes.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Also, you might want to get a different micro SD card, since the one you are using is having issues.
mike-y said:
Also, you might want to get a different micro SD card, since the one you are using is having issues.
Click to expand...
Click to collapse
??? it s jut a notification mod..
and dont be afraid to thank my posts! lol i would appreciate it..
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
The kernel I used was the stock one.
I actually dont have 3G. mine is just a TF300T wifi only. Unless its the software that makes it 3G? But i dont think thats the case...
Would that alternate kernel give any other benefits other than 3G support?
Oh yea. Youll see a dramatic change in performance to say the least. Now. Im running a tf 700 kernel. But I would recommend you yo get the Unters TF300t kernel in the 2.0 Kernel Installer. Put the Installer zip on internal. Flash. Choose your kernel. Wipe cache and dalvik . Then reboot. You will not regret it.
Sent from my SPH-D710 using Tapatalk 2
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)
Hi my LG G2X p999's screen broke a while ago so I got the screen replaced and the screen didn't work so I brought it back to the store I got it fixed at and they installed a new screen and that one worked for a few months and is now not working, now the the screen will work only till the screen is locked and after that the screen will not respond to any touches, I am going to install a new firmware (I am right now running the stock firmware) but I am not sure if that will help, do you guys have any suggestions/help?
oh and I have been searching on XDA but have found nothing that relates very closely to my problem I did find one about the screen not working after 20 seconds but the situation was different.
I am not too knowledgeable when it comes to hardware issues. However, I would try to go ahead and flash a different ROM. CM7.2 is always a trusty flash. You can get the latest nightly from get.cm. Good luck.
Pain-N-Panic said:
I am not too knowledgeable when it comes to hardware issues. However, I would try to go ahead and flash a different ROM. CM7.2 is always a trusty flash. You can get the latest nightly from get.cm. Good luck.
Click to expand...
Click to collapse
Thank you very much, I will try that this weekend!:laugh:
Please, make sure to do a full wipe. Data reset, cache partition and dalvik cache, and finally format /system under mounts and storage.
Pain-N-Panic said:
Please, make sure to do a full wipe. Data reset, cache partition and dalvik cache, and finally format /system under mounts and storage.
Click to expand...
Click to collapse
I will!
Fixed it by flashing JB
Sorry for not updating this, I was able to fix the problem by flashing TWRP and a 4.1.2 ROM used the phone for a little while and didn't have any problems so this should be an appropriate solution to the problem.
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
I had this problem for months. I did a clean install and it fix the problem. Try doing that and it might work for you too.
What do you mean by clean install?
Gigatrig said:
What do you mean by clean install?
Click to expand...
Click to collapse
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt.
Sent from my SCH-I535 using xda app-developers app
kude87 said:
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt
Click to expand...
Click to collapse
Do you mean in the "mounts and storage" menu? Use format /system... /data... /sdcard? I think that's what you mean, but I've not had to use those before, so I wanna make sure.
Thanks
:laugh:
Gigatrig said:
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
Click to expand...
Click to collapse
I had the same problem with my phone, I made a thread a little while ago with what I did. http://forum.xda-developers.com/showthread.php?t=2492304 ask any questions you have on there I want to improve it as this was a very frustrating and time consuming fix for me.