So when I tried my first JB ROM (infection), I started having some pretty significant stability issues. So after a while I assumed it was just the ROM, but after now also trying Liquid, and still having the same issues, I'm wondering if there's something else going on. Specifically, the phone randomly reboots often, and sometimes will just hang when I go to turn the screen on for a minute or more, before finally starting to respond.
When I installed Liquid, I did a system wipe and formatted the cache and delvik cache twice. At this point should I try formatting the data partition, and the SD card? I'm using CWM. Any suggestions?
Jfichtner said:
So when I tried my first JB ROM (infection), I started having some pretty significant stability issues. So after a while I assumed it was just the ROM, but after now also trying Liquid, and still having the same issues, I'm wondering if there's something else going on. Specifically, the phone randomly reboots often, and sometimes will just hang when I go to turn the screen on for a minute or more, before finally starting to respond.
When I installed Liquid, I did a system wipe and formatted the cache and delvik cache twice. At this point should I try formatting the data partition, and the SD card? I'm using CWM. Any suggestions?
Click to expand...
Click to collapse
Try a different ROM. I had stability issues as well, with both of those ROMs.
Freedom First said:
Try a different ROM. I had stability issues as well, with both of those ROMs.
Click to expand...
Click to collapse
Any JB ROMs you've had luck with?
All your issues are caused be the fact that min frequency need to be upped to 384mhz ....I've had best stability with ondemand governor and sio scheduler set on boot under performance in settings...4.1.2 and 4.2.2 based roms have softboot errors straight after install and this fixes most of them...you'll get better stability out of cm9 ICS based ROMs or cm10.2 which is 4.3 based ROMs...still changing your min frequency is a necessity...also when flashing especially new different ROMs...please don't forget to clean flash everything...dirty flashing by only wiping dalvik cache and cache will carry over every issue from precious ROMs...plus its highly recommended in all the original posts....another issue is make sure you use twrp or cwm....amon ra causes many issues on the rezound
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
To add,make sure you are on the latest hboot and radios. Be warned it will require s-off to restore/downgrade the firmware and radios if you do update them.
Related
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
must wipe before going to different rom. you may have issues booting up.
affliction said:
the reason i ask is i want to know if anyone has had a problem going from rom to rom with out going back to there back up then flashing the new rom?
Click to expand...
Click to collapse
I've had no problem at all. I always do a full wipe before flashing a new rom though. If you don't want to do a full wipe, and you're only updating the same rom (for instance, from viper 1.1 to viper 1.2 or something), then you could try minimally wiping cache and dalvik cache. I always recommend a full wipe for best results though. I consider a full wipe to be wiping system, boot, data, cache, dalvik cache, and sd-EXT (if you have an EXT partition on your sd card)
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
USSENTERNCC1701E said:
I've successfully flashed joelz' ShooTeR ReWInD 3D over stock OTA w/o wipe with no issues and then flashed Evervolv's Absurd over that with no wipe and no issues.
Click to expand...
Click to collapse
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
k2buckley said:
That will most likely start giving you problems eventually, if you continue not to wipe. Things from one rom will start showing up in the next rom you flash, and you'll most likely start getting weird little bugs here and there. At least it always did with my Evo 4G. A full wipe is usually recommended, but every flasher has their own techniques.
Click to expand...
Click to collapse
+ 1 to full wipe, you will get bugs eventually, might battery life or maybe apps won't install or work, right now might be cause all the roms are mostly the same with no heavy customization but when they start messing a lot with roms you migh get screw
If you don't have an Evo3d well you don't have an Evo3d
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
USSENTERNCC1701E said:
Both these roms are based on the stock OTA ROM for 3VO. Also "format("ext4","EMMC", "/dev/block/mmcblk0p23")" is written into the updater-script of both ROMS, wiping the /system partition prior to install. Flashover issues usually happen when you start throwing AOSP and ports into the mix. That being said, I'm meticulous about backups and will never blame an issue in a flashover on the ROM without a fresh install or a peek into the zip to ensure the issue exist.
Click to expand...
Click to collapse
It's still best to do a full wipe if you ask me. I do it even if I'm flashing the exact same ROM with say, one tweak in one of my battery icons or something. I always wipe lol.
yeah i just hate dealing with a full wipe everytime so i figured i would get some opinions on the issue right now im running steel rom and want to flash viper so im not sure what i want to do
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.
So I finally got around to installing the last of Task's 4.2.2 JB roms (6/24/2013 release) after using Task's 4.1.2 release for a long time (if it ain't broke don't fix it?). I did a full wipe, flashed the ROM, gapps, and put back the data for the apps I installed from the play store (not the system app data). I verified the MD5 sum of the ROM when I downloaded to my computer and again after I moved it to my phone, so I'm reasonably sure I got a good copy of the ROM.
One issue I have is that when I got to "Kernel Settings" in the settings menu, the settings app force closes with the message "Unfortunately Settings has stopped". Not sure what to do here - is the thing that manages the kernel settings something separate that I could clear the app data for?
Another thing is that I used to be able to have the wireless network name the phone is on in the pull-down status shade. I looked for it in ROM Control -> General UI where it was before but I can't find it there or anywhere else.
Battery life isn't as good as it was on 4.1.2 either. A couple of times I've looked at the phone and it had 40-50% battery left, and when I looked again a few hours later, it was dead. The battery was completely drained. I suppose it could be the battery, but this started happening after I installed 4.2.2 so I doubt it. The battery is about 9 months old. No apps were running at the time the battery was drained - I had closed anything that was running earlier.
I poked around in the (closed) ROM thread but couldn't find anything about the kernel settings issue or the wireless name setting (other than when Task put it in the ROM).
Anyone got any ideas?
Just curious as to why you would flash such an old ROM. There are sevral newer roms in active development here. Many 4.2.2 and 4.3 that are quite stable.
Sometimes in order to get a true battery indication you need to let the rom settle through several battery cycles (charge and drain the battery several times).
If you are having problems with stability like you describe you can boot into recovery, wipe cache, in advanced wipe dalvik cache, then reboot. If this doesn't fix you problems you can always try a new kernel ie STI, or AJ's.
Let me recommend you try one of the newer roms. Task has a 4.2.2 that is quite nice. Many are running Carbon that is now up to 4.3.1. If you really like 4.1.2 try out Cook's rom, or Sho's. Both of those have been recently updated.
Butchr said:
Let me recommend you try one of the newer roms. Task has a 4.2.2 that is quite nice. Many are running Carbon that is now up to 4.3.1. If you really like 4.1.2 try out Cook's rom, or Sho's. Both of those have been recently updated.
Click to expand...
Click to collapse
I'm using Tasks 4.2.2 ROM, and that's the one I'm having the problems with. I realize that wasn't exactly clear in my original posting.
So clearing the cache didn't fix your issue?
Flashing a different kernel didn't fix it either?
At that point it is time to factory reset.
Regardless the ROM troubleshooting is basically the same.
Sent from my SGH-I777 using xda app-developers app
Butchr said:
So clearing the cache didn't fix your issue?
Flashing a different kernel didn't fix it either?
At that point it is time to factory reset.
Regardless the ROM troubleshooting is basically the same.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Clearing the cache didn't fix it, but I didn't expect it to since that was done when I did the factory reset before flashing the ROM.
I'm probably going to find a different ROM to use.
Look for a ROM that seems to be in active development. I haven't seen an update on tasks four a while it seems. He may have moved on. The collective has a recent update. I see a lot of people using carbon. Cook updated his pretty regularly. Happy flashing.
Sent from my SGH-I777 using xda app-developers app
Did you specifically clear the Dalvik cache?
I have the same issue and it happens when Trickster MOD is updated, at some point. I get the same message you do. The app would run from the app menu, just not from System -> Kernel Settings.
A full wipe and reset brings everything back. I only recently considered that possibly deleting the dalvik and regular cache may correct the issue after a Trickster update. I have to set aside a little time to backup and test this.
How do/did others handle updating the Trickster app?
The Dalvik cache and regular cache were cleared when I flashed the ROM and I did it again a few days ago, but it still fails going to System->Kernel Settings. I wasn't aware this ran Trickster MOD, and that runs fine from the app menu.
If I have to go thru the full wipe/reset/etc again, I'm going to look at some other ROMs when I do that since Task is no longer updating his ROM for this phone.
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button