Fixed cwm files on CM7 OP - Fascinate Q&A, Help & Troubleshooting

What are the fixed cwm files on the CM7 OP about? What is fixed? What purpose since CM7 has cwm built in? Thanks in advance for info.
Sent from my SCH-I500 running CM7 using XDA Premium

I don't know if it is meant for a last resort if you have a boot loop issue or the like and you use 3 finger method to get to recovery and try a re-flash from there?
I installed it but haven't used it for anything yet.
Edit: I guess I was lucky and didn't have any issues, but jt has updated his OP in the CM7 fascinatemtd thread that anyone already on CM7 should not flash these recoveries.

It's if you're coming from ComRom or whatever else ROM and the CWR you have is giving you errors.
I had asserts errors in recovery and couldn't install the test builds. it's for people who want to initally put CM7, so you don't really need it if you had no problems installing.
Actually there's a warning in the OP that specifically says don't flash those recoveries if you are already on CM7 or MIUI MTD ROMs

CWM version
So I have red cwm from EF 3.6.0, should that be fine to use for flashing CM7, or should I flash one of the fixed files in JT's OP?
edit: I guess the above post sort of answers my question - So basically if I have problems with my existing CWM I should flash one of those?

Related

[Q] Phone seems bricked after flashing OMFGB

Allright, so there I was, running a rather stable Comm Rom 2.0 Voodoo Rom with the ED10 Kernel/Radio, and then I saw the thread on the OMFGB GB release, that I, of course, just HAD to have...
So, my first mistake was being impatient and not being able to find any installation notes, and pretending that I knew what I was doing by installing the rom via CWM mod.
Here's the rub, for some reason, whenever I did the 3 finger salute, it would pull a RED CWM that went orange when I applied update.zip ... because if I tried to install rom from sd card with the initial CWM boot, it wouldn't install anything, it would just error out unless I applied update.zip. After selecting apply update from zip, it would boot the orange CWM and allow me to install whatever I wanted...
So after applying the OMFGB rom, it showed the Fascinate/ Cyanogenmod 7 bootscreen, then went to boot loop. I panicked, pulled the battery, then backed up everything to my computer, and formatted the sd card in FAT32 with Windows 7 64 bit...
Shortly thereafter, I was using ODIN and the original "return to stock" files, and ended up getting into the stock OS.
Now I never show 3G or even 1x, and never pull data at all... when I go to place calls, it says that verizon cannot authenticate my phone... when I activate, it reboots and says everything was successful, but was noticeably a faster process than standard activation. Upon reboot, nothing improves... the os is there, everything shows that everything is fine, yet I am still not able to place calls...
Here is where it gets weird... My wife called me today, and the call came through... I received text messages, but still couldn't make calls... My bill is zeroed out, I'm not locked out that I know of, and I just want my phone working again...
Running out of ideas. I have flashed ED01 DL01 and even reapplied the stock .PIT in odin... I am going to try heimdall while I wait for help from here, but any quick help would be GREATLY appreciated...
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I will definately take this into consideration, but first i want to confirm that my phone is in full working order...
I appreciate the quick response, and hope to get some more love from the community.
Sent from my Transformer TF101 using XDA Premium App
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Trying this in about 15 minutes, will report asap...
Again, thanks for help...
Sent from my Transformer TF101 using XDA Premium App
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
martyr2k6 said:
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
Click to expand...
Click to collapse
also, lets assume I am completely as stock as possible... how should I get CWM on, and which version please link...
Also it miht be worth mentioning, though I think I already did... but when I go to activate my pjone, it says its successful, but then I go to make a call and it say that verizon annot authenticate my phone...
Here's a confusing screenshot...
Sent from my Transformer TF101 using XDA Premium App
Alright the issue is resolved, my main concern was whether or not I could use my phone for phone calls... after finally mustering up the guts to call Verizon, it turned out that the main problem in which I was experiencing was due to some form of typical midnight updates that big red does... apparently, my phone, missed some form of update that ended up de-authorizing my phone, but Verizon was able to help out, even at this late hour.
On the good note, everything went through just fine as far as flashing cm7... I just seem a bit conflicted with which rom is best. I guess its just a matter of personal preference, really. So far I prefer jt's rom just fine, but I might be switching back and forth between jt's and omfgb...
Thanks again for all the help folks, I appreciate it more than you could know.
Sent from my Transformer TF101 using XDA Premium App
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Not sure that I totally understand as to why I need to flash cm7 0713, then omfgb, then reflash cm7 0704... seems a bit redundant.
If you could clarify this for me and what improvement this offers, I would appreciate it.
Sent from my Transformer TF101 using XDA Premium App
Because omfgb apparently doesn't convert to mtd but cyan does, so you have to flash cm first
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yup, that was your mistake. prior to flashing omfgb, you need to be on jt's cm7.
I'm too lazy to read all the posts but try flashing cm7 via cwm4. then, Odin back to stock using the right files and configurations. there's a sticky in the development section.

[Q] GIVE ME CLEAR INSTRUCTION! CM7 and OMFG

okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Did you remember to flash gapps?
Sent from my SCH-I500 using XDA Premium App
izzjkjoe said:
okay guys so i made this thread since it was getting too confusing and hard to track CLEAR INSTRUCTION on how to root from Rooted rom to cm7 or omfg roms!!
Basically this is what i did and STILL have iSSUE:
1.ODIN and atlas v.2.2pit (DL09 stock rom)
2. updated all OTA
3. pulled out battery and ODINed blue CM7 (latest one from jt's site)
4. did 3 method cmr and clear all data/wipe/davik
5. installed latest cm7 7/17
6. waited and seem like everything is perfect then it stops at cm7 logo with galaxy s sign and kept waiting and nothing HAPPENS anyone help???!!!
this is really pissing me off because I've been trying this several times now!!
ALSO for omfg i dont even know the instruction to get there anyone help it would be great!!!
Click to expand...
Click to collapse
- In step 1 use vzw eb01 instead of dl09
- No need for step 2 just flash eb01 and reboot fully
-In step 3 pull batt and odin cwr 3-30 fix all (instead of jts blue one) and immediately do step 4...
-do step 4 the same as you did..wipe data/cache/delvik
-install cm7 build date 7/4 and reboot
That will get you running on cm7...from there you can install mtd kernel of choice (if you want something different then the one thats comes with, it) gapps, and/or the newest cm7 build..do not wipe here to go to the newest build but make sure you only use the recovery that came with cm7 by accessing it via the power button menu, or terminal emulator...reboot recovery...no three finger booting recovery from here out.the cm7 recovery will also be blue..you only odin the 3_30 fix all to get the cm7 build on your phone do after that first time seeing red recovery after you're on cm7 it will be blue from there on.
-odin desired radio.
Sent from my SCH-I500 using XDA App
well apparently, there seems to be no links to the earlier versions of cm7 and the only thing is the latest cm7 with blue recovery from jt's site can..... i really want to try CM7 geez im missing out...
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
wjsmaggle said:
You can just install the latest CM7 following the same steps the previous poster gave you. No need to install 7/4. Install 7/17 then 7/18 update.
Click to expand...
Click to collapse
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
izzjkjoe said:
Thanks for the info but that is the issue i'm having I'm currently in stock froyo then i ODINED cmr 4 (blue from jt site) then i installed the latest 7/17 and everything seems to be working then i'm left hanging on cm7/galaxy s logo forEVER!! and nothign happens...
AND i did wipe date/davik/cache... please anyone???
Click to expand...
Click to collapse
My previous post says to try to flash it with cwr 3-30 fix all did you odin that recovery and try to flash cm7 from there?
Sent from my SCH-I500 using XDA App
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
izzjkjoe said:
well there was no link on jt's site for cmr 3 or cm7 7/4 your talking about
Click to expand...
Click to collapse
The Latest build should still work just try flashing it with the 3-30 recovery
here is a link
http://forum.xda-developers.com/showthread.php?t=942021
Scroll down to the .tar file and download it..odin it and three finger boot into recovery wipe everything and flash the newest cm7 build and reboot...once on cm7 don't three finger boot anymore.
Sent from my SCH-I500 using XDA App
When you odin, did you tick the re-partition box? Also you need to use one of the tar balls in the sticky about moving from cm7 to another rom. I know you're not going from cm7 but the tar balls still apply to this situation.
Sent from my SCH-I500 using XDA Premium App
I also had problems installing cm7 at first so what I did was installed latest miui.us build first which gave me blue cwm and converted all my files. Then flashed cm7 with no probs. This worked for me.
Sent from my I500 using XDA App
well tell me the instructions not just say "install miui" obviously i dont know how to do give me the steps!
Sorry, I had stock 2.2 eb01 (edo3/4 should work) to start. Then I used odin and flashed cwm-all (2.x.x or something) / three button boot to get to recovery/ wipe data/cache/flash super user zip/reboot/power off and back to odin/flash cwm-all again/three button boot/wipe data/cache/dalvik/flash latest miui . At this point it should reboot (cyanogen logo) then back to recovery and automatically install/reboot recovery/flash cm7 11.1. But like I said this worked for me, for some reason miui installed perfect like any other rom and not cm7. Sorry if this doesn't help.
Sent from my SCH-I500 using XDA App

Installing CM7 nightlies is killin me!

what is the best way to install the nightlies now? i have tried the fool proof tutorial and it never seems to install properly, just keeps taking me back into cwm. can i just flash nightly 62 from cmw 2.x? whats the deal?
When running CM7 (or any 2.2/2.1 rom), the easiest way is make sure you can get into cwm by hand. If you can, then dl the latest nightly (you can still do this using rom manager premium), make sure toy have gapps, reboot into recovery, and flash by hand.
Sent from my SGH-T959 using XDA App
Once I have cm7 on the phone, I download the new nightly and run cmw then select install rom and point to the new file. I leave the check for wipe cache and it keeps my info. It even works with the glitch kernel.
Sent from my hacked Samsung Vibrant running CM7.

Flashed Glitch with THS 6.1, Stuck in Recovery.

I'm running the ths build 6.1, flashed gltich B5 for 6.1 and it booted up fine. Went to reboot and now the phone is stuck in the recovery, wiped, both caches, rebooted, still stuck. Restored back up, still just reboots to recovery. This has happened twice. Followed all the instructions. Why can't I flash this kernel.
Should I have flashed another older build of the kernel first then upgraded to the B5?
Can someone please maybe give me a different kernel to flash for the AOKP build as well. I've had poor luck with this rom and glitch and wouldn't mind running something else.
Thanks for the help
Same thing happened to me first time I flashed 6.5. I forgot to flash build 2 before 6.5, I blamed it on that. Since starting from scratch, adding Build 2 and Glitch my phone is running pretty darn good. Hope this helps.
See I flashed build 2 rather than build 1, due to better results, and it still did this. (Unless you're referring to Glitch Build 2 and not THS) ICS and Glitch v14 seem to be way more involved or complicated than GB and V13. I think I'm just not doing something incorrect.
I know there is other good kernels out there I'd rather run at the moment. I read that the Sephamore Kernel add some Voodoo Fix options like BLN and Voodoo Sound which is all I really care about.
Id rather have Glitch though
It sounds like you may have possibly 3-fingered into recovery at some point? That will make you bootloop. Also, you don't want to flash semaphore kernel or any other kernel/rom/whatever that is for a different device, that's pretty much asking for a brick. Glitch is the only custom kernel available on this device for ICS.
I think I honestly just did something out of order. I originally reflashed the nandroid because I lost 3G once the glitch was flashed. I'll have to give it another shot.
Sent from my SCH-I500 using xda premium
Keuka79 said:
I think I honestly just did something out of order. I originally reflashed the nandroid because I lost 3G once the glitch was flashed. I'll have to give it another shot.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
You flashed the wrong glitch... Read more flash less.
Sent from my SCH-I500 using xda premium
k_nivesout said:
It sounds like you may have possibly 3-fingered into recovery at some point? That will make you bootloop. Also, you don't want to flash semaphore kernel or any other kernel/rom/whatever that is for a different device, that's pretty much asking for a brick. Glitch is the only custom kernel available on this device for ICS.
Click to expand...
Click to collapse
I think that may have happened in my pocket. Is there any way out of that if I'm at work? I can't odin until I get home.
Sorry, I don't know of any way to get out of the bootloop short of odin (assuming there was a 3-finger). You'll just want to reflash the CWM4 fixed recovery in odin, then boot into that and try clearing cache/dalvik or just reflash your rom.
That was the only solution, thanks.
Tapatalking on my Fascinate

Updating Clockwork Mod Recovery

I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Slusho said:
I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Click to expand...
Click to collapse
From what I've heard you should never update CWM. Also are you backing up in recovery? or Using (God forbid) Rom Manager
CWM is easy to install.
There are two methods that I know of.
The first being using ROM manager though it could (ironically) break it and your device end up in a soft brick.
The second is to manually push it using adb, but first you must download the CWM for our phone (i777) from the clockwork mod website.
Sent from my SGH-I777 using Tapatalk 2
Biporch said:
CWM is easy to install.
There are two methods that I know of.
The first being using ROM manager though it could (ironically) break it and your device end up in a soft brick.
The second is to manually push it using adb, but first you must download the CWM for our phone (i777) from the clockwork mod website.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Don't tell him to use rom manager.
CWM is part of the kernel on our phones, so you would have to find a kernel with the version of CWM you want to install and flash that to update it.
Are you sure you have enough free space on your SD card to do a backup?
I am using recovery, not rom manager. If I shouldn't update it, how should I backup without getting that error?
Slusho said:
I am using recovery, not rom manager. If I shouldn't update it, how should I backup without getting that error?
Click to expand...
Click to collapse
You sure you have space in SD card?
Sent from my SGH-I777
mvi57 said:
CWM is part of the kernel on our phones, so you would have to find a kernel with the version of CWM you want to install and flash that to update it.
Click to expand...
Click to collapse
I can't stress this enough to people.
For the ATT Samsung Galaxy S2, model SGH-I77, ClockworkMod is a custom recovery built into a custom kernel. It is not separate and you do not flash or update it separately. Please do not attempt to update ClockworkMod at all, this will only result in a soft brick.
As mvi57 said, if you want a newer version of CWM, you'll have to find a custom I777 kernel which has the newer version built in.
I wish we could place this warning somewhere where newbies can see it while trying to flash stuff. I'm glad we caught OP before he soft bricked. OP, I don't mean to make you sound stupid or anything by such a highlighted post, I just want to warn as many newbies as possible, and I'm hoping they see your thread and thus this post.
122ninjas said:
You sure you have space in SD card?
Click to expand...
Click to collapse
That was it. I had past backups taking up space. Thanks.
Also, when I backup my phone to my computer (manually), some files don't copy over (I'm pretty sure it's because the file names are horrendously long). Is there a way I can get around this?
And karate, I take no offense to that. I prefer clear posts like yours, and I actually remember that it's part of a kernel now. I knew back when I first rooted, but forgot, as I'm sure many do. Maybe it should be added to a sticky about updating?
Slusho said:
That was it. I had past backups taking up space. Thanks.
Also, when I backup my phone to my computer (manually), some files don't copy over (I'm pretty sure it's because the file names are horrendously long). Is there a way I can get around this?
And karate, I take no offense to that. I prefer clear posts like yours, and I actually remember that it's part of a kernel now. I knew back when I first rooted, but forgot, as I'm sure many do. Maybe it should be added to a sticky about updating?
Click to expand...
Click to collapse
From past experience it seems like people don't read the stickies
Sent from my SGH-I777
Slusho said:
I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Click to expand...
Click to collapse
Just install the latest cm9 nightly for the i777. It will install cwm 6.0.1.1... our device is different than others, cwm must be built into the kernal.

Categories

Resources