Related
Hello,
I'm using LeeDrOiD, Froyo 2.2
My phone randomly froze up on me 3 times this last month. One time it happened when the screen was on, last two times it was on standby; I left my phone working just fine, only to find it locked up sometime later.. I couldn't do anything with the phone, couldn't even hard reset. I had to remove the battery to restart.
What can be the reason?.. Do stock ROM users experience this also?.. Or is it because of the Froyo?..
Any help would be appreciated.
Regards..
Did you perform a full wipe before flashing the rom? Lee always recommends it. Back up your stuff, boot into recovery and perform a full wipe, including the dalvik cache, then re flash the rom. If that doesn't do it, hit the LeeDroid rom thread. It has about 100000000 posts, and I'm sure you'll be able to search and find someone who had a similar problem. See what was suggested. 9/10 times, a wipe and re flash solves random hang ups.
Sent from my HTC Desire using XDA Premium App
Is it a boot loop (the ROM stuck on boot screen) or is it just a freeze?
The first one maybe is this issue. It appears that happens sometimes even on Froyo too.
it can be from the rom. some have that problem some dont. i had and changed the rom. now my phone is stable.
try some gingerbread roms
but stock is the most stable one -.-
Hello again, a belated thanks for all the previous responses; I have to bump this thread though.
When I first posted this thread I was using the "leedroid" ROM, right now I'm using the "reflextsense" ROM... The freezing is actually more frequent in reflextsense...
Btw, just to clear up, @z3r0n3: it's a freeze, not a boot loop.
I'm using these ROMS on stock sd card 4gb class2. Can this be the reason?.. I'll soon get 8gb class6, would this be a solution?
Ah ok, ruled out rom issue then!
Are you running setcpu to overclock too high? A symptom of pushing it too far is freezing up. Start scaling it down in small increments until stable.
If not overclocking, and now not rom, perhaps try re flashing your radio?
Sent from my HTC Desire using XDA Premium App
change kernel for one of the newest snq's
http://dl.dropbox.com/u/13432479/bravo-kernel/index.html
it's always the matter of wrong kernel or too big overclocking
I am not using setCPU program, not overclocking either.
My radio is the last linked version in the forum: 32.54.00.32U
@wnp_79: The kernels in your link are not for my ROM..
My ROM: http://forum.xda-developers.com/showthread.php?t=791315&highlight=ReflexTSense
Any kernel suggestions from this link?
Btw, this can be helpful:
kernel: 2.6.32.28-halcyon
http://i1103.hizliresim.com/2011/3/31/2967.png
Any of these kernels should work on ReflexTSense, since they are Sense based. Recommend the latest InsertCoin/LeeDroid one.
But first, you should try the kernel you mentioned, the 1000mv one.
Sent from my customized HTC Desire using TTP
This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....
So, I thought I was fairly flash proficient with my Epic, until my replacement showed up. I rooted it with CMW3101 one click and then flashed EH17 Hurricane 1.6 full. Followed the instructions to a T with flashing the 8 lock and AIO mods.
After 30 minutes I would get FC's on everything. So I did it again, same response. So I said eff it, lets flash SFR 1.2, as I have never had any problems with it. I Wiped 3x and flashed that, rebooted, and then flashed the honeycomb theme.
All seemed good to go for a couple hours. I used set CPU to 200-1.2 on conservative. Went to sleep with phone plugged in, and no alarm in the morning! Phone had the blue led on, I unlocked the screen only to see constant FC's again!
What am I doing wrong? I never had these problems in the past. What can I do now as I am FC'ing on SFR 1.2?
Neckberg said:
So, I thought I was fairly flash proficient with my Epic, until my replacement showed up. I rooted it with CMW3101 one click and then flashed EH17 Hurricane 1.6 full. Followed the instructions to a T with flashing the 8 lock and AIO mods.
After 30 minutes I would get FC's on everything. So I did it again, same response. So I said eff it, lets flash SFR 1.2, as I have never had any problems with it. I Wiped 3x and flashed that, rebooted, and then flashed the honeycomb theme.
All seemed good to go for a couple hours. I used set CPU to 200-1.2 on conservative. Went to sleep with phone plugged in, and no alarm in the morning! Phone had the blue led on, I unlocked the screen only to see constant FC's again!
What am I doing wrong? I never had these problems in the past. What can I do now as I am FC'ing on SFR 1.2?
Click to expand...
Click to collapse
hmm.. i would suggest to ODIN ec05 again. reroot. redownload all the files and try it again.
If you want to go one further.. once u do the above. setup the system to your liking. then make a nandroid backup. then wipe everything again, restore your nandroid, flash a kernel and see how it goes.
unfortunately I think you are right. I wasn't doing anything I different from before with my other epic, but I never had these problems again. Good idea to start from scratch.
And even though Hurricane says it has journaling on it is recommended to flash the journal on zip before flashing themes.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
And even though Hurricane says it has journaling on it is recommended to flash the journal on zip before flashing themes.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do this on every GB ROM and it really seems to help
Sent from my SPH-D710 using xda premium
More fun. So yesterday I odin'd stock and one click rooted. Flashed SFR1.2. ran the 10 mounts fix and flashed Twilight Zone 1.1.1. This morning, again, no alarm and phone was completely unresponsive. SetCpu is set to 400-1.0 on demand. I had to do a battery pull then it booted normal. Now 2 hours later it just rebooted on its own on my desk.
I don't get it. This replacement phone has been finicky.
I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2
Have you tried doing a super wipe between flashes?
Should fix Shutdown Freeze
rfail1988 said:
I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Hhhhmmmm, have you flashed any ROMs or was that a stock flash?
Even with stock flashes you can have issues just asking [for instance when I got a phone from Tmobile nothing would fix the shutdown menu not appearing for me then once I re-flashed a new ROM low and behold it worked].
Or if you are using the SmartAss V2 governor [or anyothers dependant on it like I believe lionheart is] in your CPU speed tweaking app you may want to use on demand or conservative instead. If you flashed any kernel, CPU tweak scripts you may need to check the values that applied [usually in init.rc folder somewhere as a script [just open in any text editor to read them]. Also definitely could be any UnderVolt settings [where you set voltage used by CPU under certain speed conditions and if set lower than the cpu can tolerate then when it switches to speed that is set too low is when it shuts off] . Undervolting can be done in either System Tuner or Faux Clock [swipe screen to left on open and viola global under/over volt setting ]. If you have not done any of these things or are unsure read below and see if that helps.
What I would try [in order]
First run backups in titanium backup and nandroid [titanium is so you can restore apps back without having to re-install and reset your settings and nandroid just to be safe if you are newer to working with Android Devices in this way]
Then Reboot in to recovery [on boot [right after you feel the very first vibrate] hold BOTH vopl keys in [press in center] and release when you see Samsung Logo, just be sure you release before it goes off screen]
Tap Clear Cache [in Main Menu]
Tap Clear Dalvick Cache [in advanced]
Flash Fix Permissions script [found in QA and in Dev threads for this phone] you want the Fix Permissions v2 by Minotauri zip [look at my past posts I have linked my mirror page to many posts]
You just save it to either internal or external sd and flash it just like you would when installing a ROM in cwm Recovery Menu
and reboot and see what happens [this should nail it really after clearing both caches and fix perms I bet]
if that does nothing reboot clear caches [if you had to wait to see] and go to mounts and storage and format /data [only]
Restart and see what happens...
If that really does nothing be sure to re-download your ROM via WiFi ONLY [or copy from computer]
be sure to flash darkside super wipe [google it, my mirror page, the forums, its everywhere] and Kernel Cleanser Script BEFORE YOU FLASH THE ROM
[Like So]
Boot in to recovery Flash Darkside Super Wipe
Flash Kernel Cleanser [another script [google, my mirror page, forums again]]
Then Flash ROM [and NOTHING else]
Boot phone [skip account setup we'll be back] wait 3 min after initial lockscreen if unsure] and don't do anything [no app installs setting adjusts nothing]
Restart in to Recovery again
Wipe Cache and Dalvick Cache
Install aany helper zips [like super user, toggles zip whatever with any custom radio being the last thing]
Restart Phone
You should not have shutdown freeze after reboot and clearing cache you should prolly still have it on initial boot, pull battery if needed and manually boot in to recovery as above.
RealPariah said:
Hhhhmmmm, have you flashed any ROMs or was that a stock flash?
Even with stock flashes you can have issues just asking [for instance when I got a phone from Tmobile nothing would fix the shutdown menu not appearing for me then once I re-flashed a new ROM low and behold it worked].
Or if you are using the SmartAss V2 governor [or anyothers dependant on it like I believe lionheart is] in your CPU speed tweaking app you may want to use on demand or conservative instead. If you flashed any kernel, CPU tweak scripts you may need to check the values that applied [usually in init.rc folder somewhere as a script [just open in any text editor to read them]. Also definitely could be any UnderVolt settings [where you set voltage used by CPU under certain speed conditions and if set lower than the cpu can tolerate then when it switches to speed that is set too low is when it shuts off] . Undervolting can be done in either System Tuner or Faux Clock [swipe screen to left on open and viola global under/over volt setting ]. If you have not done any of these things or are unsure read below and see if that helps.
What I would try [in order]
First run backups in titanium backup and nandroid [titanium is so you can restore apps back without having to re-install and reset your settings and nandroid just to be safe if you are newer to working with Android Devices in this way]
Then Reboot in to recovery [on boot [right after you feel the very first vibrate] hold BOTH vopl keys in [press in center] and release when you see Samsung Logo, just be sure you release before it goes off screen]
Tap Clear Cache [in Main Menu]
Tap Clear Dalvick Cache [in advanced]
Flash Fix Permissions script [found in QA and in Dev threads for this phone] you want the Fix Permissions v2 by Minotauri zip [look at my past posts I have linked my mirror page to many posts]
You just save it to either internal or external sd and flash it just like you would when installing a ROM in cwm Recovery Menu
and reboot and see what happens [this should nail it really after clearing both caches and fix perms I bet]
if that does nothing reboot clear caches [if you had to wait to see] and go to mounts and storage and format /data [only]
Restart and see what happens...
If that really does nothing be sure to re-download your ROM via WiFi ONLY [or copy from computer]
be sure to flash darkside super wipe [google it, my mirror page, the forums, its everywhere] and Kernel Cleanser Script BEFORE YOU FLASH THE ROM
[Like So]
Boot in to recovery Flash Darkside Super Wipe
Flash Kernel Cleanser [another script [google, my mirror page, forums again]]
Then Flash ROM [and NOTHING else]
Boot phone [skip account setup we'll be back] wait 3 min after initial lockscreen if unsure] and don't do anything [no app installs setting adjusts nothing]
Restart in to Recovery again
Wipe Cache and Dalvick Cache
Install aany helper zips [like super user, toggles zip whatever with any custom radio being the last thing]
Restart Phone
You should not have shutdown freeze after reboot and clearing cache you should prolly still have it on initial boot, pull battery if needed and manually boot in to recovery as above.
Click to expand...
Click to collapse
Lionheart works fine. Smartass v2 is a mess.
OP, what is your min clockspeed?
Sent from my SGH-T989 using xda premium
Thanks, ill try that after work today i didnt superwipe althoigh i have the file so ill try that and reflash my rom.
Sent from my SGH-T989 using Tapatalk 2
rfail1988 said:
I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I have this same issue but no solution. It happens about 2 times a month, not enough to bother me but I have to pull the battery to get working again. I am using Juggs 5.0 with CPU tuner and the sophisticated profile minimum clock is 192 Max is 1512. I did do a super wipe before flashing and cleared caches and so forth. I was using gingersnap rom before and I wanna say it was happenening then too but I could be wrong. I always assumed it was something to do with the cpu settings, usually happens when I start an app shortly after waking the device.
Sent from my SGH-T989 using XDA
mr1ncred1ble said:
I have this same issue but no solution. It happens about 2 times a month, not enough to bother me but I have to pull the battery to get working again. I am using Juggs 5.0 with CPU tuner and the sophisticated profile minimum clock is 192 Max is 1512. I did do a super wipe before flashing and cleared caches and so forth. I was using gingersnap rom before and I wanna say it was happenening then too but I could be wrong. I always assumed it was something to do with the cpu settings, usually happens when I start an app shortly after waking the device.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Dont clock to 192. 384 is the min
G1ForFun said:
Lionheart works fine. Smartass v2 is a mess.
OP, what is your min clockspeed?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
My min clock speed is 192, and i am on jugg 5.0, but have had the same issue with foxstar and another rom that i cant remember. I havent messed with oc/uv settings, and have even eliminated my setcpu screen off profile so it wont happen in theory while not in use. Usuly it happens while being used in non-cpu-intensive apps like dolphin of tapatalk.
I have since cleared dalvik and cache (again) and it hasnt happened yet after a few hours. Only time will tell!
Sent from my SGH-T989 using Tapatalk 2
rfail1988 said:
My min clock speed is 192, and i am on jugg 5.0, but have had the same issue with foxstar and another rom that i cant remember. I havent messed with oc/uv settings, and have even eliminated my setcpu screen off profile so it wont happen in theory while not in use. Usuly it happens while being used in non-cpu-intensive apps like dolphin of tapatalk.
I have since cleared dalvik and cache (again) and it hasnt happened yet after a few hours. Only time will tell!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Like I said, don't clock that low
Looks like the cpu values arent the problem. I also fixed permissions and it died soon after i turned up my min values. A superwipe, kernel cleanse and reflash seem to be in order!
Sent from my SGH-T989 using Tapatalk 2
Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2
xcrazydx said:
Dont clock to 192. 384 is the min
Click to expand...
Click to collapse
For the record I raised my min to 384 but didn't solve the problem. Happened this morning surfing the web using Dolphin HD. Like I said tho, doesn't happen often enough to make me mad, and I don't think I'll be running this rom too much longer
Sent from my SGH-T989 using XDA
mr1ncred1ble said:
For the record I raised my min to 384 but didn't solve the problem. Happened this morning surfing the web using Dolphin HD. Like I said tho, doesn't happen often enough to make me mad, and I don't think I'll be running this rom too much longer
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
What kernel?
wow! U da man!
rfail1988 said:
Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the same problem with my SGS2? can you tell me the exact sequence? maybe we should make it a sticky, as I have seen many threads with the same problem but no definite solution!
Possible fix for the T-Mobile Samsung Galaxy S2 Sleep of Death.
Hey I had to work on a couple of phones just like your phone. After a couple of weeks with the phone, I found this out by accident and maybe it can help. Instead of just writing down the steps I made a video let me know if it works. I was able to reproduce on a couple of phones but don't know for sure if it is just a luck.
Here is my video.
http://youtu.be/SV3oDycVSb4
rfail1988 said:
I have flashed multiple gb roms with this same issue. My phone will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
---------- Post added at 08:41 AM ---------- Previous post was at 08:05 AM ----------
Hey I had to work on a couple of T-Mobile Sleep of Death Galaxy S2. After a couple of weeks dealing with the phone, I found this out by accident and maybe it can help. Instead of just writing down the steps I made a video let me know if it works. I was able to reproduce on a couple of phones but don't know for sure if it is just a luck.
Here is my video.
http://youtu.be/SV3oDycVSb4
rfail1988 said:
Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!
http://forum.xda-developers.com/showthread.php?t=1805773&page=117
Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?
I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper
So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app
Ukb wont boot here.
Sent from my HTC_Amaze_4G
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium
A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.
ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app
jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium
hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2