[ROM]Superclean 2.8!! *UPDATED*

Status
Not open for further replies.
ok
@everyone that had a hang up ,,,the recovery you were using, does it have the error missing xxx when you boot into clockwork?
 
I tried to update to nonvoodoo 2.7 in CWM 2.5.1 and in 3.0.0.8 and when updating via CWM 2.5.1 it hangs at the Samsung screen. When updating in CWM 3.0.0.8 it reboots back into CWM 2.5.1.

I wiped everything before trying multiple times.

Also the 2.7 update file is only about 133MB. It is quite a bit smaller than previous versions. For those that got it to work, was your file larger?

Thanks for all the help and the new ROM!
 
I don't see any errors when booting into CWM.

I boot into CWM 2.5.1 by holding VOL Up + Down + Power and then apply update.zip to get into CWM 3.0.0.8.

I no longer have access to ROM Manager because I can't boot up successfully.
 
Yes. Mine hung on the Samsung screen and when I boot into ClockWork (red) I get two errors:

E:Missing bitmap progress_empty (Code-1)
E:Missing bitmap progress_fill (Code-1)
 

I can tell you I did not have that error message.

No boot issues.

Edit: I can also tell you that there are some posters having issues with enabling the lagfix over in XDA after flashing the voodoo version. I would bet they have used the same CWM.
 


Like this?
This is at the bottom when I go into red...
not sure if this is what your looking for..

E:missing bitmap progress_empty
(Code -1)

E:missing bitmap progress_fill
(Code -1)

EDIT:
oops...didn't see the responses posted above
 
Yes. Mine hung on the Samsung screen and when I boot into ClockWork (red) I get two errors:

E:Missing bitmap progress_empty (Code-1)
E:Missing bitmap progress_fill (Code-1)

i always have those but they never effected anything that i have flashed before earlier today i did 2.6 then tried 2.7 and got screwed lol
 
read posts on voodoo first as you could get undesirable results. gunnermike did a good post on it.
 
FOR NON VOODOO USERS NOT BOOTING

nvfix.tar

Please Odin that and report back.

I will not be re-uploading the nv version until i hear back that this works.
 
ok
@everyone that had a hang up ,,,the recovery you were using, does it have the error missing xxx when you boot into clockwork?

I can only plead ignorance to that question - I really didn't pay attention based on the fact that I've had no probs flashing the last 3 versions, & I got back to 2.6 no problem. I'll have to go back & run it again...
 
read posts on voodoo first as you could get undesirable results. gunnermike did a good post on it.

I have read thisbut thst doesnt answer my ? Can I flash 2.7 voodoo ovr 2.6 non voodoo n enable the lag fix or do I have 2 flash a voodoo kernel first?
 
nvfix.tar os hanging at...
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
 
Status
Not open for further replies.