[Retired][ROM]Superclean 2.9.2 EA15/EB01/EB16/EC10 Based

I've got the random reboot issue as well. Something crashes, I feel the vibration I associate with a force close, then the phone will reboot. At first I thought it was because I put it in a dock but today it happened repeatedly. I thought it was because I turned the screen off. Maybe I hit the power button to long and it restarted.

Sent from my SCH-I500 using Tapatalk

Hey voghan, did you read three pages back where Adrynalyne was asking for logcats of the crashes? I would imagine the more info he has on this the better chance he will have to come up with a solution.
 
  • Like
Reactions: jcom86
Hey voghan, did you read three pages back where Adrynalyne was asking for logcats of the crashes? I would imagine the more info he has on this the better chance he will have to come up with a solution.

Great catch Shark, I forgot to mention that! I sent Adr my logcat a little while ago so we'll have to wait and see what he comes back with.
 
Kernel is included in the ROM. While you are downloading the ROM, before you unplug your phone, after you put the zip file on your sd card, delete update.zip from your sd card, you won't need it anymore. After you do that, turn off usb storage, turn phone off and flash this file in ODIN MEGAUPLOAD - The leading online storage and file delivery service should only take 7 seconds, put battery back in, DO NOT reboot phone, boot directly to recovery by holding volume up, volume down, and volume buttons until samsung logo flashes for the second time. As soon as you see it flash for the second time, let go, you will boot directly to red cwm-recovery-all, the one without the bitmap error messages. Flash the 2.9 zip from there and once you reboot your phone you will boot directly to that red cwm every time (except for rebooting to recovery from Rom Manager, which we are discouraging everyone from doing for now.) If you long press the power button and go to recovery from that menu or if you do the volume up, volume down, power button thing you will boot directly to the new cwm red without having to go through stock blue recovery. Yay! Thanks to Adrynalyne for including the cwm-all in 2.9.

The kernel included with the 2.9 ROM is the regular EB01 kernel, correct. I flashed DXC's 2.8 package via odin and have the tether kernel.

If I'm understanding your instructions correctly...
1) Place the 2.9 ROM .zip on the sd card.
2) delete update.zip
3) flash cwm-recovery-all via ODIN
4) replace battery and boot directly into CWM
5) flash 2.9 ROM
6) reboot and enjoy 2.9 with the the stable EB01 Kernel

Did I get it right? :D
 
The kernel included with the 2.9 ROM is the regular EB01 kernel, correct. I flashed DXC's 2.8 package via odin and have the tether kernel.

If I'm understanding your instructions correctly...
1) Place the 2.9 ROM .zip on the sd card.
2) delete update.zip
3) flash cwm-recovery-all via ODIN
4) replace battery and boot directly into CWM
5) flash 2.9 ROM
6) reboot and enjoy 2.9 with the the stable EB01 Kernel

Did I get it right? :D

Yes you did, but I got it wrong and have confirmed it is even easier now. Eliminate steps 2, 3, and modify 4 to just booting to recovery, apply sdcard:update.zip, in red install zip from sd card, then choose zip from sd card. Adrynalyne included the cwm-recovery-all in 2.9 and it overwrites the old red cwm. You can even leave update.zip right where it is if you want, the way Adrynalyne has it you go right past update.zip and will boot to the cwm-all every time.
 
  • Like
Reactions: Les3631
Think there are two ways, one you need to connect to your computer and use adb. The other is to use alogcat which can save it to a text file under an alogcat folder on your sdcard


I just installed alogcat on my phone. Is it retroactive or do I have to wait for it to crash again?
 
Me too, random reboots times 3 today. Vibrates twice and just reboots.

See my post below yours and see if you can supply Adrynalyne with the information he is looking for. If you're not sure what that is, scroll back a page or two and read through the posts. Someone gave some instructions on how to get the information.
 
Can't get much easier than just flashing 2.9 in cwm! Awesome!

I know. Isn't he? And 2.9 is super stable, solid as a rock. I've been flashing all kinds of combinations and everything I can think of and have yet to have one force close or issue of any kind.
 
See my post below yours and see if you can supply Adrynalyne with the information he is looking for. If you're not sure what that is, scroll back a page or two and read through the posts. Someone gave some instructions on how to get the information.

I pm'd him just waiting for a response.
 
  • Like
Reactions: Landshark
Wanted to thank you guys again. So far I think this is definately your best build Adrenylyne!! You the man!!!:)
 
loving the 2.9 its running great sick wit it Adrenylyne the steel blue theme is running great on it minus the market not falloing along the app theme but still fantastic
 
One thing I noticed on SC2.9 NV is normally when my phone boots up, the screen comes online and then the media scanner kicks in for 2 seperate cycles before I can really "use" my phone. On 2.9 it seems to come online pretty much right away, and i don't notice the media scanner for some time.

Is this normal?

By the way, my phone now is rebooting almost constantly, quite a change for earlier today and the past few days.....
 
Since removing launcher pro a few hours ago, I have been trying to recreate the reboot issue with my phone and I haven't been able to do so. In an attempt to further test this I went back to post #335 of this thread (on page 34) and did a complete reinstall as described by Adrynalyne using 2.9 voodoo as my final install. This "clean install" seems to have fixed the issue completely for me. I'll report back later.
 
Since removing launcher pro a few hours ago, I have been trying to recreate the reboot issue with my phone and I haven't been able to do so. In an attempt to further test this I went back to post #335 of this thread (on page 34) and did a complete reinstall as described by Adrynalyne using 2.9 voodoo as my final install. This "clean install" seems to have fixed the issue completely for me. I'll report back later.

I'm on Non Voodoo....will that matter? I don't have a desire to go Voodoo right now....
 
ok so lookin around im hearing lots of DONTS for using set cpu on fascinate and also DONTS on over clocking does anyone have anything good to say about it ? im curious about overclocking but not at all knowledgeable about it but my looking around isnt producing much information
 
Thank you. Sorry if I was a pest, just trying to help Adrynalyne help all of you.

All good man, no worries.

I think I might just flash 2.9 again. I wiped cache and d cache when I did it last night. Maybe this time I'll do it two or three times as some people had mentioned.
 
I'm on Non Voodoo....will that matter? I don't have a desire to go Voodoo right now....

Remove launcher pro first and see if that works. I suspect, that if the removal doesn't work it might be because of a bad install you had. Follow the steps from post #335 but instead of using 2.9 voodoo like I did just use the nonvoodoo. REMEMBER TO PERFORM ALL OF YOUR WIPES!!!

And honestly, it is incredibly easy to go voodoo and if you're on the fence about it you should use this opportunity to do so now. ;)
 
All good man, no worries.

I think I might just flash 2.9 again. I wiped cache and d cache when I did it last night. Maybe this time I'll do it two or three times as some people had mentioned.

If you decide to flash 2.9 again DO NOT forget to wipe, I did three of each just to be sure. Also, if you have the time I suggest following landshark's steps from post #335. It may or may not make a difference but I haven't had the reboot issue since doing so.
 
ok so lookin around im hearing lots of DONTS for using set cpu on fascinate and also DONTS on over clocking does anyone have anything good to say about it ? im curious about overclocking but not at all knowledgeable about it but my looking around isnt producing much information

I would have to concur and give you a big fat NO on both of those. I had set cpu for a short time and had nothing but problems with it, uninstalled. Perhaps you may have read some of the same posts, but I think I remember reading overclocking is likely to fry our batteries. Our batteries have a small computer in them that regulates the charge on the battery. Our batteries would be damaged by overcharging, so the computer stops the charge at 100%, then if you don't unplug the phone, the battery drains to about 95%, then starts charging again, and cycles that until you unplug the phone. That's why people have been noticing when they leave their phone on the charger overnight and unplug it in the morning the battery may show anything from 95 - 100%. Because of that computer the danger of overcharging is eliminated when charging the phone, so there is no harm in throwing the phone on a charger whenever you want to because what's worse for our batteries than overcharging is letting it drain all the way empty. That protection for overcharging does not, however, extend to overclocking.
 
  • Like
Reactions: T3CH9ICIAN

Latest posts

Trending Posts

Forum statistics

Threads
956,984
Messages
6,970,922
Members
3,163,681
Latest member
Rukhshan