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

[nghthawk47]

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.

I hear that, not on the fence, just don't need it. NV is fine for me. Not sure if I want to take out LP as it is what I have used on every build without a problem. I really don't want to wipe everything and start over from scratch if I don't have to, just went through that with 2.7 and the stuck Samsung screen. If indeed the problem renders LP unusable, I will revert back to 2.6 which was problem free for me with LP. I am waiting to hear back from Ady so I can give him this log and see what he thinks....

 

[PJnc284]

I just installed alogcat on my phone. Is it retroactive or do I have to wait for it to crash again?

It looks like it records back a little ways. I'd wait for adrynalyne to clarify as there are a lot of optional settings in the app and he's more familiar with the info he needs.

And the hiss/buzz when the screen comes on while on a call is back. Think it may have been the EB16 kernel that was helping before.

 

[Landshark]

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.

jcom, just wanted to pass on some info I pass on to all new rooters wanting to try voodoo. Yes it is super easy to load and install voodoo. It's just like rooting, follow the instructions exactly and it's a piece of cake. Where you will get into trouble with voodoo is not during the conversion, it's what you do once you are on voodoo. Mistakes made on nonvoodoo that can be fixed fairly easily can cause serious damage in voodoo. Burn into your brain that you cannot flash anything nonvoodoo over voodoo, big time trouble. If you aren't sure about something, go to Gunnermike53's voodoo thread, look for an answer, and if you don't find it ask, ask, ask. Gunner is the voodoo master and he won't steer you wrong. That's why I try to steer new rooters away from voodoo until they have gained experience in nonvoodoo with flashing, booting, creating bacups etc., especially experience fixing and getting out of problems in nonvoodoo.

 

[T3CH9ICIAN]

very much appreciate that its what i was seeing and reading ok thats great that i looked into it ill keep my phone the way she is haha thanks again im now gonna grab the steel blue 2.8 i think it my be y my market isnt the same as the theme. its the regular market look i liked the blue black look but under 2.8 i see a dl for market so is that sayin that 2.8 doesnt change the market or is that so u can just change specificly the market without the whole theme

 

[Lttlwing16]

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.

Thanks Landshark, but I went ahead and flashed the 2.9 before I read this, with no problem. When I go to into recovery from holding the power button and choosing it from the menu, it automatically goes to the red cwm, sans bitmap error. Do I still need to follow the steps above?

 

[craigcls]

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.

Cool, after all this reading, I thought I may have done something wrong when flashing 2.9. Now I feel better. I installed the SC 2.8 package a couple of days ago via Odin, after resetting my phone back to factory defaults. The next day I flashed 2.9 NV via cwm. It booted into blue, applied update.zip, went into red, then chose the 2.9 zip file from SD card. Now, whenever I go into recovery, it goes right to red and bypasses blue.

Question I have, there is still an option in cwm to apply update.zip. Why is it there, should I ingnor it, and what would happen if I clicked on it (I didn't )? Also, why does it say Voodoo at the top and have the Voodoo option when I installed the NV file (I double checked that)? One other thing, what is what's this about the white bitmap error messages in red cwm?

 

[PJnc284]

Also, why does it say Voodoo at the top and have the Voodoo option when I installed the NV file (I double checked that)? One other thing, what is what's this about the white bitmap error messages in red cwm?

You're on the correct one. The recovery says voodoo as everyone is using the same one. The one with the error message was an older one.

 

[Landshark]

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.....

Yes it is normal. Also last night Adrynalyne started a thread with a mod to eliminate the part of the media scan that scans the read only system, that way the media scan doesn't take as long and you can use your phone quicker. The script is in post #4 of this thread:
http://forum.androidcentral.com/ver...s-hacks/66652-mod-speed-up-media-scanner.html
Download the zip file to your sd card and flash it through cwm. Then you enter the commands in terminal emulator.

 

[Landshark]

Thanks Landshark, but I went ahead and flashed the 2.9 before I read this, with no problem. When I go to into recovery from holding the power button and choosing it from the menu, it automatically goes to the red cwm, sans bitmap error. Do I still need to follow the steps above?

No, you are good. I found out after I posted that, the way Adrynalyne has red cwm-all packaged in 2.9 overwrites the red cwm-froyo with the error messages. You can even leave update.zip where it is and don't have to delete it. Cwm-all will load directly and basically ignore update.zip

 

[nghthawk47]

Yes it is normal. Also last night Adrynalyne started a thread with a mod to eliminate the part of the media scan that scans the read only system, that way the media scan doesn't take as long and you can use your phone quicker. The script is in post #4 of this thread:
http://forum.androidcentral.com/ver...s-hacks/66652-mod-speed-up-media-scanner.html
Download the zip file to your sd card and flash it through cwm. Then you enter the commands in terminal emulator.

I guess my point of posting was to say there wasn't any delay at all with the media scanner in 2.9 as there was in previous versions. My post was stating the media scanning wasn't happening and questioning if that was a problem, or if it was by design in 2.9. I haven't loaded any special script, I just noticed when I upgraded to 2.9...

 

[jcom86]

I hear that, not on the fence, just don't need it. NV is fine for me. Not sure if I want to take out LP as it is what I have used on every build without a problem. I really don't want to wipe everything and start over from scratch if I don't have to, just went through that with 2.7 and the stuck Samsung screen. If indeed the problem renders LP unusable, I will revert back to 2.6 which was problem free for me with LP. I am waiting to hear back from Ady so I can give him this log and see what he thinks....

I hear you on not wanting to lose everything. I was using LP for every build before this one as well. Honestly, the only reason I tried it was because I'm off from work today and have had all day to fool around with my phone. Better off to wait and see what Adr has to say about the issue.

Incase you guys can't tell I'm a little gung-ho about playing around with my phone. I've bricked plenty of phones in the past so I'm not afraid to try different things to solve a problem.

 

[Landshark]

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.....

I guess my point of posting was to say there wasn't any delay at all with the media scanner in 2.9 as there was in previous versions. My post was stating the media scanning wasn't happening and questioning if that was a problem, or if it was by design in 2.9. I haven't loaded any special script, I just noticed when I upgraded to 2.9...

Ok, it just sounded like there was a delay in the media scanner starting when you said "and i don't notice the media scanner for some time" So no, it is not normal for the media scanner to not run at all. Even with the scripts Adryanlyne provided it only shuts down the unnecessary part of the media scan. You definitely have something major going on. Let's hope Adrynalyne can work his usual magic.

 

[k rock]

Well I just flashed 2.9 again and wipe both cache and dcache twice. Install went smooth as it did before. Now I just wait to see if it'll random reboot whenever.

 

[nghthawk47]

Ok, it just sounded like there was a delay in the media scanner starting when you said "and i don't notice the media scanner for some time" So no, it is not normal for the media scanner to not run at all. Even with the scripts Adryanlyne provided it only shuts down the unnecessary part of the media scan. You definitely have something major going on. Let's hope Adrynalyne can work his usual magic.

I see.....It does eventually happen, just not in the beginning.....a decent time later....15 minutes or even later. Very odd....as everything else about this version is great, the phone seems noticeably smoother/faster than previous versions, I don't notice any lag (even though I am on NV) and Battery life seemed better than previous (no actual proof, just seemed to last longer). I like the changes he made in UI and APKs. I would hate to have to kill it....

 

[nghthawk47]

Well I just flashed 2.9 again and wipe both cache and dcache twice. Install went smooth as it did before. Now I just wait to see if it'll random reboot whenever.

My reboot issue didn't happen for a day or so after I upgraded it....

 

[T3CH9ICIAN]

so ive downloaded steelblue 1.5 SC28 and the market theme and now im getting at boot a force closing of the market i removed and reinstalled steel blue without the theme and still stuck im unable to get to the market any ideas out there

 

[k rock]

My reboot issue didn't happen for a day or so after I upgraded it....

Me too, I flashed 2.9 last night and no issues. This morning maybe around 9am I had my first random reboot, then around noon and 5pm today.

We'll see how tomorrow goes.

 

[Suicide Shift]

so ive downloaded steelblue 1.5 SC28 and the market theme and now im getting at boot a force closing of the market i removed and reinstalled steel blue without the theme and still stuck im unable to get to the market any ideas out there

what ROM / Kernel you using?

I have seen this as well. Only way I have been able to fix it is to flash my SC2.9 again, boot to ensure I am good, and then apply the theme again.

I am not sure what settings etc you may loose as I have been flashing crap like crazy and have not been worried about what is there or not.

 

[jcom86]

Ok, now I'm really curious.. I'm no expert on this, but I know that after flashing a new os on a blackberry it takes a while for things to settle in before any issues pop up. Is the same true for android or is everything faster? My reboot issue took a day to manifest like nghthawk's did.

K rock- let me know what happens now that you've done a reflash. Hopefully you're able to duplicate my results

 

[T3CH9ICIAN]

im EB01SC29 i had steel blue 1.2 on and going fine till i lost the market theme look so went to update and now market force closes so i have no market at all i jsut when and wiped cache and d cache and flashed sc2.9 again and still getting a forced close market on boot