[FIX][4-1-11]Latest ClockworkMod and SuperClean ROM's - Erasing the CWM Confusion

so just so im crystal clear now that ive read and reread first ill odin

EBO1.. The full enchilada Multiupload.com - upload your files to multiple file hosting sites!

atlas_v2.2.pit ... http://dl.dropbox.com/u/2056318/atlas_v2.2.pit

then ill reboot phone move around it make sure im running good then remove battery and odin this

Odin Package cwm-recovery-ALL-3-30-FIX.tar
MD5 Hash: 00e90e790a70e2d66b6cba6a152de504

then boot into recovery and flash this

Non-Voodoo Kernel
super_frankenclean_2_9_2nv_CWMFIX.zip
MD5: 06bed73a07f4b4f3cc32d6a0d60a05ee

as im staying nv and ill b wiping cache and wiping dalvik then reboot from there i can flash the theme of my choice or kernal or boot animation or anything always clearing cache and dalvik make sure my os is running good and then make a nandroid

Yes that is all correct. You can get the full EB01 file and the Atlas file from post #9 of this thread. The others are obviously in the OP. If you want to use a different kernel than the one included in Superclean, you will need to flash that separately in a different cwm session after flashing the superclean ROM.
 
absolutly awesome im glad ive gotten a yea thats right cause i was mixed up moving from the top to thread 9 and back and staying on task so now ill fallow my post side by side with the first post here goes nothing well later tonight haha thanks again MASTER SHARK THE DROID IS STRONG WITH THIS ONE
 
i just went threw the process went super smooth all the odin is done havent flashed anything yet most likely comming soon but running top notch thanks for all the help from everyone
 
Okay beloved AC fam... here is the latest.
I flashed 2.9 via odin.
booted up.
yay, win win all good.

then I flashed cwm recovery, and flashed 2.92 via cwm and was back to black screens and cranky buttons that didn't respond to my oh-so-gentle touch.

so I flashed the odin 2.9.2 and now I seem to be back to normal.

Do I still want to do the gizmodroid fix. of course.
But after today, I think I'm going to wait a while.

Things seem to be smooth right now.
I'm guessing I messed up by flashing the wrong EB01 file earlier.

So, that's my story... :D

Just wanted to hopefully make you feel a little bit better and let you know you weren't the only one who did what you did with the EB01 file. Found this in this same thread over at XDA:

So, I tried step 1. I flashed, via Odin, the stock EB01 tar from adyn's stock post. Also pulled the atlas_v2.2.pit from his "how to fix brick after 2.7" post. I believe I'm bricked. I selected repartition, pit in pit section, eb01 tar in pda section. My phone now boots directly into the samsung stock recovery. I don't get a samsung boot logo either. I can get into download mode via holding down vol-down, but no matter what I flash now to try to bring my phone back to life, I'm still stuck. Has anyone run into this? I'm not a noob when it comes to Odin, so I don't believe I've made any mistakes.

EDIT: Ugh, I flashed what I thought was the full EB01 stock rom. It was the pre-rooted version I found a while ago. When flashed with the atlas v2.2 pit, it soft bricked the phone. So, just a suggestion for the OP that you can get the needed EB01 tar and atlas files from adryn's post on fixing your phone after it's borked with SC 2.7:
 
  • Like
Reactions: jampot
ive done all the odin and now went to set up my facebook sync under accounts and sync i tried to set it up to sync never and going threw set up i choose calander and contacts and uncheck all fb contacts then it goes to sync and it just sits on the loading page 10 plus minutes tried with usb plugged in and out on the wi fi and out on data network it would not finish or sync so what i ended up having to do was go into contacts then settings menu then get friends choose my friends and sync them is there a better way to sync my contacts with fb besides threw the get friends way? not a big deal i only wanted it for the contact pictures but was curious if it was something i had done to not allow the original set up route not work
 
Just wanted to hopefully make you feel a little bit better and let you know you weren't the only one who did what you did with the EB01 file.
Thanks Lando! That totally makes me feel better :)

I just finished flashing all the stuff from the OP and post #9 in this thread (not in that order, of course.)
I couldn't help myself. I had to do it. I've got flash fever.

And guess what? I did it right and my phone is now what my hubby lovingly refers to as "my tank" haha! It's perfect.

Thanks again for all the expert advice and constant support. I'm super appreciative. *wish there was a pom-pom droid smilie*
Yay!! :D
 
Thanks Lando! That totally makes me feel better :)

I just finished flashing all the stuff from the OP and post #9 in this thread (not in that order, of course.)
I couldn't help myself. I had to do it. I've got flash fever.

And guess what? I did it right and my phone is now what my hubby lovingly refers to as "my tank" haha! It's perfect.

Thanks again for all the expert advice and constant support. I'm super appreciative. *wish there was a pom-pom droid smilie*
Yay!! :D

You're welcome and you'll be handing out the advice and help like crazy now. And you'll be able to tell people, "I'm speaking from personal experience here, don't do that." :D
 
  • Like
Reactions: jampot
Im not clear so im askin if after ive done this full fix odin process if im able to just flash comavolt right on to here of if I need to do anything at all im nv so I know only flash nv but otherthen that is there anything besides normal wipes before flash and I assume a nandroid thanks for any advice
 
Im not clear so im askin if after ive done this full fix odin process if im able to just flash comavolt right on to here of if I need to do anything at all im nv so I know only flash nv but otherthen that is there anything besides normal wipes before flash and I assume a nandroid thanks for any advice

Once you have gone through the whole process you can flash the kernel of our choice in cwm. Just be sure to finish the whole process first, including flashing the sc 2.9.2 from the OP. If you flash the comavolt kernel then the sc 2.9.2 the comavolt kernel will be overwritten by the kernel in sc.
 
  • Like
Reactions: T3CH9ICIAN
Thanks as always most my info comes from u and its always good I'm running 2.92 from the op here everythings been running for a day now its nice but if there is a longer batt life with same performance ill try it out thanks again ur always a great help
 
  • Like
Reactions: Landshark
I'm just wondering if anyone has done a nandroid restore either themed or unthemed with the new cwm?
Is it all good now? I would just do one but I chicken. Last one with the old one really screwed me up.

This message was sent via Tapatalk
 
OH ****....a HARD BRICK!!!

So here I was determined to make better better...now I cannot even flash using ODIN because it fails 1/6 of the way through- usually to a solid color screen on my phone. The last thing I did was use odin to flash CWM fixed and this new ATLAS pit file. I am pretty sure it was the pit that bit.

PLEASE HELP, anyone??
 
Hey guys... could use some help here...

I followed the steps in the OP, and, on the first boot... everything appears fine. I restored using TiBu. However, after a reboot, I find myself in an endless loop of FCs. I am really not sure why considering I have used this methood in the past and never ran into this problem.

Thoughts anyone?

Thanks!
 
Hey guys... could use some help here...

I followed the steps in the OP, and, on the first boot... everything appears fine. I restored using TiBu. However, after a reboot, I find myself in an endless loop of FCs. I am really not sure why considering I have used this methood in the past and never ran into this problem.

Thoughts anyone?

Thanks!

Did you tried running the fix permissions script in Terminal Emulator or CWM? First time doing this I followed all the steps in the OP and when booting up I enter FCing hell even with fixing permissions afterwards. Make sure when you odin EB01.md5.tar you pair it with atlas_v2.2.pit. I realized I made a big mistake of pairing the CWM_Recovery_All_Fix.tar with atlas_v2.2.pit in odin which results in force close city. Or that you are restoring other system data in TiBu besides the green highlighted ones you are gonna have conflict.
 
  • Like
Reactions: JOrtenzi
Downloaded it, flashed it with CWM and my phone went into the endless reboot loop after rebooting from CWM. Tried reflashing the new CWM fix and then 2.9.2 and nothing worked, kept rebooting. Just went ahead wiped and reinstalled the FIX ALL and then 2.9.2 thru Odin. Everything back up and running but I think I will leave my CWM alone !

This Newbie survived his first crash !

I never got the reboot loops, but when I tried to flash the update thru CWM, it wouldn't take, no matter how many times I tried. I recommend going the ODIN way.
 
Since using this version of cwm, I have been unable to make a nandroid backup (get md5 sum error). This has happened with 2 different kernels, both of which that error was supposed to be fixed. Should I try re-flashing cwm 3-30 in odin?
 
Since using this version of cwm, I have been unable to make a nandroid backup (get md5 sum error). This has happened with 2 different kernels, both of which that error was supposed to be fixed. Should I try re-flashing cwm 3-30 in odin?

Same thing happened to me.

It was working fine until one day I tried and started to get md5 sum error.
 
Someone else posted in another thread when they did a nandroid backup with the battery at 98% or higher, they did not get the md5 sum error.
 

Trending Posts

Forum statistics

Threads
956,411
Messages
6,968,101
Members
3,163,539
Latest member
manboa