Related
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?
This thread is now irrelevant as Jellybean is available for the device.
The old post can be found below:
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time, then my guess is that this issue will not effect you, BUT it may strike you at any given time!
For those of you who insist on upgrading to ICS, *PLEASE* backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.
A quote from an effected user:
ringnutz said:
I also had the can't mount data problem, I tried for 3 days to get it to work. I ended up sending it back to Samsung after reverting everything to stock. I was on cm9 though and one night it just started bootlooping while i was asleep. I.e. it would fully boot then restart after 5 seconds or so. So I tried reverting to stock and trying again, which is when I got the can't mount data issue. I literally tried every combination of wiping, recovery, Odin/heimdall, and the only thing that would get past the Samsung logo was cm9, which would just stick at the boot animation forever. I got tired of messing with it and thought it could have been a hardware problem, so I sent it back under warranty
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
A quote from an effected user:
daviddavid123 said:
i installed cm9 and ics 4 then my tab hard bricked and internal memory damaged
Click to expand...
Click to collapse
A quote from an effected user:
krbabb said:
I dont have posting privleges in the developer forums but i thought i would let you know whats up with my tab.
Rooted it, got cwm on it and flashed cm9. Worked for about a week without issue then started the bootlooping issues. I couldnt even wipe the data in recovery.
Used odin to go back to stock HC according to your instructions. Then i thought it bricked cause it just got stuck on the default screen showing galaxy tab. Tried installing HC a few more times but it never booted.
Tried one more time but now with the stock ics. Still nothing so i gave up.
Only thing is i couldnt power off. I planned to let the battery die. So it just sat on the default gakaxy tab screen and about 30 minutes later it showed the samsung boot animation.
I let it sit for another half hour with samsung pulsing. Nothing. So i reboot into recovery (stock) which i couldnt even get to before now, wipe everything like 5 times then reboot the device.
Booted up and works like a charm. I thought this thing wad gone.
Not sure if the stock ics tar file did the trick but let everyone know that mine came back to life. It possible other devices could be bricked but maybe there is a chance for some people.
Sent from my GT-P6210 using xda app-developers app
Click to expand...
Click to collapse
If you have flashed ICS and you have bricked your device I am sorry. I know there are a few people out there who have....
To conclude, everybody please be careful about tinkering with your device. I know ICS has great speed enhancements and all, but as of right now your box of ice cream sandwiches may or may not be poisoned.
For the daredevils:
CM9 [View thread]
Guide to flashing ICS [View thread]
EDIT: Our case is not the same as the other galaxies.... Ours effects the data partition while theirs effects their emmc... I'm assuming ours may be a bug with the firmware installation / recovery as it was with theirs however I'm not sure why it is effecting users on CM9....
EDIT 2: We should all be cautious and NOT wipe at all using Samsung's ICS Recovery. I was chatting with aorth and he suggested that that may be the cause of the issue. His recovery (or the one I posted in my guide) are safe to wipe on.
EDIT 3: I guess we also have reports of the emmc being corrupted as well...
Just don't wipe data/factory reset using recovery ICS (RECOVERY 3e). Use recovery 5.5.0.4 or 6.0.x.x......only you wipe for up new rom, everything will be OK.
Sent from my GT-P6200 using Tapatalk 2
Yeah, i experienced this type of total brick. I flashed p6200 ics firmware with mobile odin and than did factory reset in ics recovery mode. I think this was the reason of hard brick. After some time tablet did shut down and didn't turn on. Service fixed the problem, they said that main board died.
Ignore this post.
StrumerJohn said:
That's not the case I afraid...
Click to expand...
Click to collapse
I really don't think it was a problem with upgrading. I had been on cm9 for over a month, then I woke up one morning and it was bootlooping. I got all the can't mount data errors afterwards, so it's either a hardware problem or cm9 is somehow magically corrupting the /data partition. I hadn't even installed anything recently
EDIT: Samsung just sent me the email that the repair is finished, they replaced the main board, so it definitely was a hardware problem.
Sent from my myTouch 4g via Tapatalk
This issue was brought up a couple months ago by aorth, I think its in his CM9 thread or in one of the rooting or CWM threads. I don't think it is an issue that will be going away any time soon as Samsung isn't in any hurry to fix it, that is if they even can or want to.
Using stock ICS for almost 3 weeks now.
I was backing up and restoring all of the partitions via CWM 6.0.1.0 two times.
Nothing weird happening for the moment.
I use the ics wipe/factory reset and I don't have any problem, I have 6210 .
Well, aorth entioned sth like this before, here his post:
aorth said:
Maybe you guys have heard, but some early ICS ROMs for Galaxy Note and other similar Galaxy S II variants have triggered hard bricks due to faulty MMC firmware handling erase commands improperly. I never bothered to read up about the issue until now, but it looks like we should also be careful.
Chainfire just released a tool to print out whether your device has a known-bad firmware revision, Got BrickBug?. As you can see, my device has firmware revision 0x19. This revision has been known to cause hard bricks on other devices using Samsung ICS ROMs.
CM9 is safe (Entropy512 haxx0red the kernel), but we should be careful.
Click to expand...
Click to collapse
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Well, aorth entioned sth like this before, here his post:
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if I had the bad one, but mine worked fine for months too. Then out of the blue it bootlooped and when I tried to fix it by reverting to stock, I got the error. Hopefully when it comes back it will have a different firmware revision (if that's what the problem was)
Sent from my myTouch 4g via Tapatalk
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
02xda2 said:
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
Click to expand...
Click to collapse
If you flashed it using Mobile Odin that's normal because it uses its own recovery.
Ok, so what's the verdict? This bug sounds very scary.
Given that I'm running a stock ICS flashed via ODIN, should I be running:
-Stock recovery
-CWM
-Something else
to avoid bricking while factory reset?
I also use mobile Odin to flash ics and no problem. So, could you say that with Mobile Odin are safe from this problem?
Just read this http://www.reddit.com/r/Android/comments/xj2hd/i777_superbrick/, seems some of the things said could be relevant for us.
I have a galaxy note and Entropy who is dealing directly with samsung on this issue has a thread over on the galaxy note page. Lots of information over there.
I use the free emmc bug check app by vinagre https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en to check my samsung devices on ics. Not entirely sure that the same case applies for the note and the tab plus though but it does give me peace of mind.
Just to err on the side of caution, I always odin flash back to gingerbread to wipe cache and other stuff before upgrading. This seems to have worked for me so far. *fingers crossed*
Check out that app above, its free and have a read of entropy's thread http://forum.xda-developers.com/showthread.php?t=1698977 but beware they don't take kindly to noob questions. I just mainly read entropy's updates and replies and ignore most of the rest of the stuff there.
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
hi,
i have flashed the stock ICS, the Austrian version using ODIN3. i have been running it since july 18th.
so far i dont see any problem with my tab..
just to say, i have flashed the firmware atleast 3 times, just as an exercise. and have factory reset it after ICS flash atleast like 5 times now.
everything so far works fine. i use the stock recovery for factory reset.
after the 1st flash, i had root.. then thought of unrooting, so flashed the firmware 2 more times.
and in between the flashes, i have factory reset a lot of times.
so far, the bootloop problem which i used to have when on HC, is not there. hopefully, it wont occur in ICS.
hope, this helps developers.
Zarvox said:
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
Click to expand...
Click to collapse
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Or use this method:
http://forum.xda-developers.com/showthread.php?t=1661590
Sent from my GT-P6200 using Tapatalk 2
giangp1 said:
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
Thanks with manual method described in this thread I've confirmation that my data partition became corrupted.
Yes it is alive !!!
I've deleted mmcblk0p9 (DATAFS on my P6210) and recreate one with smaller size (3 GB) than normal (15.2 GB).
When the tablet boot I realise I've 1.68 GB of storage
Now I may increase the size of data but previous tries told me if data reach 5 GB in size the creation of partition fail.
Update 03/28: Problem resolved with assistance from BadaB!ng developer of collective rom. Thank you for the help. Will post reference link.
Update 03/27: Problem not resolved. 4.04 system was some factory test image and everything I tried to flash or update caused the problem to repeat.
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
fftlambet said:
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
Click to expand...
Click to collapse
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
seshaz said:
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
I have no way to confirm that, however, that is where I made the last change that required root and reboot occurred. From that reboot, I could only get to the Samsung Galaxy Note 10.1 screen. I need to make an update...I was mistaken when I said it was fixed. The 4.04 image that I flashed worked but was not complete...no lock screen, had some factory test program on it, and anything new I flashed or updated to resulted in getting the screen stuck on Samsung Galaxy Note 10.1 again. I am trying to find other images to odin flash or another instance of this issue.
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)
Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:
Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app