[ROM]Superclean 2.8!! *UPDATED*

Status
Not open for further replies.
Thanks Pikanate,

now for the 2 hours to download the file! :-) (Yes, too cheap to pay for premium download) Then give it a try..
 
Anyone having problems with accessing the Market? I get "a server error has occurred".
I had the same problem after going back to 2.6 from 2.7. I un installed the market, got a market apk from xda, re installed it and everything was fixed, never had the problem again.



Sent from my SC2.8 Honeycombed Fascinate.
 
Is there another source for these files? The download seems to not be working and I've had a couple folks try it.

EB16SC28x_DXC.tar.rar
 
Is there another source for these files? The download seems to not be working and I've had a couple folks try it.

EB16SC28x_DXC.tar.rar

what ROM are you running on now?

if your on dl09, you need to use EB16SC28_DXC.tar.
 
I assume dl09 as I've only had the patch pushed down from verizon, I thought the only difference was one wiped the data clean the other kept it in tack (figured that meant the sms and such..)

phone says Firmware 1.2-Update1
Kernel version 2.6.29
 
I assume dl09 as I've only had the patch pushed down from verizon, I thought the only difference was one wiped the data clean the other kept it in tack (figured that meant the sms and such..)

phone says Firmware 1.2-Update1
Kernel version 2.6.29

follow the directions in droidxcons thread but use EB16SC28_DXC.tar and everything should work out just fine. This will clear your data so make sure you backup everything you want. The EB16SC28x_DXC.tar file is for upgrading, for instance, if you were running on superclean 2.6 that file would upgrade you to 2.8 and none of your data would be wiped.
 
Currently running 2.6nv. Can I flash 2.8nv from my sdcard using orange cwm? I already have the zip on my card, but like several others, the cwm rainbow is a bit confusing.
TIA


Sent from my Samsung Galaxy S
 
Currently running 2.6nv. Can I flash 2.8nv from my sdcard using orange cwm? I already have the zip on my card, but like several others, the cwm rainbow is a bit confusing.
TIA


Sent from my Samsung Galaxy S

you want red for 2.8
 
Two things:

1. will this work if i am coming from a non-rooted ea28 phone.
2. Do i need to be rooted in order to flash a super clean rom or another rom in general?

Thanks,

1. Yes, this will work if you are coming from a non-rooted EA28 phone
2. Yes you need to be rooted in order to flash superclean or any other rom. You can use DroidXcon's all-in one packages and you get the ROM, root, and clockwork mod recovery at the same time here:
http://forum.androidcentral.com/ver...ged-roms-w-root-clockwork-updated-3-04-a.html
 
  • Like
Reactions: Fandango#AC
up and running on 2.8. liking everything so far. No issues here besides the soft key stuff thats already been mentioned in previous posts(worked at first/issue after reboot) but thats not a deal breaker for me. Added back in some Tw video,clock,calc,nfs and running great. thanks for the hard work Adrynalyne!!
 
Hello Everyone,

I am having a hell of a time using superclean (2.8). As i posted in another thread, it took about 10 times to flash with odin for it to take. All was good, but now...the internet force crashes. It vibrates once, then three times in a row and drops to the home screen. I can go to google, and do a google search, it shows the sites, but when it starts to load it crashes. It will however let me go to websites already in my bookmarks. i am at my wits end. please help!!

i went into clockwork and cleared my cache. that didnt help..

check the OP of SC 2.8, it says to flash this browser if you are getting FC's on the browser: http://forum.androidcentral.com/ver...g-roms-hacks/59528-eb01-debinged-browser.html

hope that helps.

Hey jackmei2, with as many people as are posting in these threads, when you are responding to someone's post, especially if you are helping them and giving them an answer, please hit the "quote" button under that person's post so they know you are responding to them. Otherwise your answer may get lost in the shuffle. Thanks.
 
Hey I know its somewhere around but I can't find it I put the orange cwm on today how do I use both the orange and red. Like how do I go back to red when I need it?

Sent from my SCH-I500 using Tapatalk

I am on SC2.7 Non-Voodoo. When I boot into recovery I go straight into red without the e:\blah blah errors.

Is this the correct CWM for SC2.8 or do I need to converyt to the old one that boots into blue, apply update.zip and go to red with the e:\ errors? If so where is the file and how do I flash/use it?

Thanks

flash this through odin MEGAUPLOAD - The leading online storage and file delivery service

this is the link dxc gave me and it works perfect. it goes straight to red but when you flash a new ROM through red next time your in recovery it will go back to orange. If you want to go back to red again just flash it through odin again:)


Currently running 2.6nv. Can I flash 2.8nv from my sdcard using orange cwm? I already have the zip on my card, but like several others, the cwm rainbow is a bit confusing.
TIA


Sent from my Samsung Galaxy S

you want red for 2.8

OK everyone. Sheepdog Elite does one hell of a fine job describing the different cwm's here:
http://forum.androidcentral.com/ver...56394-beginners-rooting-read-me-3-3-11-a.html
But I will break it down again. You have stock blue (2e) recovery which came with all our phones, but is not an actual clockwork mod recovery. Then there was a green clockwork mod recovery and a red clockwork mod recovery specifically for voodoo. When we got the first Froyo leak which was build DL30, the green cwm no longer worked, so jt1134 came out with a new green cwm, but that only lasted a day or two. He came up with a red cwm known as cwm-froyo because the green did not work correctly and our phones were not being supported by Rom Manager which was developed by the same person who developed cwm originally. That is the red cwm that everyone sees that has the bitmap error messages in white lettering on their screens. Then jt1134 came out with the "new" red cwm (AKA cwm-recovery-all or cwm-all) which looks exactly like the old red cwm-foyo except it didn't have the bitmap error messaages. Both of these red cwm's even have the same version number 2.5.1.x. The difference between the two is cwm-all installs directly to our phone's boot partition and does not require the update.zip like cwm-froyo, so you boot directly to cwm-all without having to go through stock blue recovery and hitting apply sdcard:update.zip like cwm-froyo. Right now you can safely flash anything in either red cwm. If you are like me and on a nonvoodoo kernel and build, cwm-all will not stay permanently on your phone after you flash a new ROM. That is because all the nonvoodoo ROMs still contain a stock kernel. Some are modified, but they are still stock. The stock kernel pushes you back to stock blue recovery instead of booting directly into red. So if you are on nonvoodoo you have two choices: 1) You can leave update.zip on the base of your sd card, flash cwm-froyo in ODIN and not have to flash cwm again, you will just have to go through stock blue first every time; or 2) You can flash cwm-all in ODIN, but have to do that after each time you flash a new ROM. If you don't plan on flashing a new ROM for say several months, you can flash cwm-all and not have to worry about it for that entire time. If you have caught the flashing bug and will be trying different ROMs, you may be better off sticking with cwm-froyo. We will all be able to flash cwm-all and have it stick permanently on our phones once the source code for Froyo is released and the devs can put out some custom kernels. As I said before the developer of Rom Manager and cwm was not supporting our phone for a while, but has since made up with our devs and working together they have come up with this new cwm orange which is version 3.0.0.8. If you click the Flash Clockworkmod Recovery button in Rom Manager, it will update your Fascinate so you will boot to orange if you boot into recovery from Rom Manager. You will also boot into orange from update.zip if you do not have cwm-froyo flashed on your phone. CWM orange uses a script called Edify, everything before orange used a script called Amend. Right now hardly anybody is using Edify, so orange is basically useless except for making and restoring nandroid backups. So for now, if you see one of the few things that was written to work with Edify, you have to use cwm orange for that. For everything else you can either use red cwm-froyo or red cwm-all. I have heard of a few small bugs with cwm-froyo on EB01, so I guess the end result of this long-winded diatribe is the safest and best practice for all of us on a nonvoodoo EB01 build is to use red cwm-recovery-all and just do a battery pull and flash it through ODIN each time we flash a new ROM.

Links:
Update.zip - MEGAUPLOAD - The leading online storage and file delivery service
CWM-Froyo - Multiupload.com - upload your files to multiple file hosting sites!
CWM-Recovery-All - MEGAUPLOAD - The leading online storage and file delivery service

I will not be around for the rest of the night to answer any questions about this as I am already running late for my niece's (and goddaughter) birthday, but since there was so much confusion about all this, I felt it necessary to write this post. I will be back on tomorrow during the day for any questions.

EDIT - Since I have already seen this question asked and know it will be asked again, if you used one of DroidXcon's all-in-one ODIN packages you probably have cwm-froyo since he has you put update.zip on your sd card. If you are unsure boot to recovery, apply sdcard:update.zip and if you see the bitmap error messages in white you have cwm-froyo. If booted straight to red and don't see the white bitmap error messages, you have cwm-all.
 
Last edited:
just had one small glitch today. came home put phone on wifi, when i turned wifi off my 3G would not come back on. tried hitting the data button a few times but it didnt work. I finally got it working again by rebooting.
 
i was over at xda and there was some people saying that bluetooth was not working on 2.8voodoo, anyone know if it is working on 2.8NV??
 
i was over at xda and there was some people saying that bluetooth was not working on 2.8voodoo, anyone know if it is working on 2.8NV??

Because of your post, I checked my Jabra 3030 headphones with my SC 2.8, NV, and all seems fine. I even unpaired and repaired the headset to make sure that there wasn't an issue. Again, they're working as expected.
 
I had to dump eb01 voodoo as it has heating up my phone with wifi and gps off. EG16 voodoo did not work at all. Back on non-voodoo. BT is working fine for me on 2.8.
 
Tap on Contacts > Groups > long press on Not Assigned if you have any > tap on Create

Create a group name. I made one called bob, because I'm lazy, and then tapped Save.

Tap on Add member > select any contact > Tap on Add

You should get an instant buzz, then buzz buzz buzz

"Sorry! - Use *#9900# to take log -
The process android.process.acore has stopped unexpectedly. Please try again"

I have duplicated this issue several times, and opted to do so because of a complaint over on DroidX's thread for Odin flashing. Since I don't create groups, it's not much of an issue for me, but hopefully the syntax for the FC helps Adrynalyne, or someone else, to chase down the root cause.

[EDIT] It would help if I said that I'm running SC 2.8, NV, and have only updated with non data wipe versions since around 2.3 or 2.4, and have had SC 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 and now 2.8, all non voodoo. I can provide additional data as requested.



SuD
 
Last edited:
Because of your post, I checked my Jabra 3030 headphones with my SC 2.8, NV, and all seems fine. I even unpaired and repaired the headset to make sure that there wasn't an issue. Again, they're working as expected.

thanks i actually flashed 2.8NV myself and my bluetooth has been working fine, not sure why its not working for others but it seems to be on people running 2.8voodoo
 
Tap on Contacts > Groups > long press on Not Assigned if you have any > tap on Create

Create a group name. I made one called bob, because I'm lazy, and then tapped Save.

Tap on Add member > select any contact > Tap on Add

You should get an instant buzz, then buzz buzz buzz

"Sorry! - Use *#9900# to take log -
The process android.process.acore has stopped unexpectedly. Please try again"

I have duplicated this issue several times, and opted to do so because of a complaint over on DroidX's thread for Odin flashing. Since I don't create groups, it's not much of an issue for me, but hopefully the syntax for the FC helps Adrynalyne, or someone else, to chase down the root cause.

[EDIT] It would help if I said that I'm running SC 2.8, NV, and have only updated with non data wipe versions since around 2.3 or 2.4, and have had SC 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 and now 2.8, all non voodoo. I can provide additional data as requested.



SuD

Just tried it and it worked fine.

Best thing for you to do at this point is to provide a logcat during the crash.
 
Status
Not open for further replies.