I was sent a Fascinate as a Droid Incredible replacement. I was able to root it without a hitch but now my CWM can't mount anything. Won't mount anything can't bring up any logs. I am using the CM7 Clockwork and my phone is now bricked and I'm tired of using Odin to restore it and root it again then flash CWM and CM7, I lose all my games and free apps which I have to download again.
What am I doing wrong?
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
skafan2 said:
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
Click to expand...
Click to collapse
Yeah. I can work on stock just great.
What is the best rooting method to use if I plan on using CM7?
What I do is use Super One Click to root (http://forum.xda-developers.com/showthread.php?t=803682), then flash the custom CM7 CWM, and then flash CM7 in the custom recovery after wiping data, cache, and dalvik.
Use the CM7 from here: http://forum.xda-developers.com/showthread.php?t=1190668
Do I use the recovery in that thread? I've been using that one as well. I will re download the rom then.
Yes. Here are the exact steps from that thread after rooting with SuperOneClick:
Start with a rooted device (do not ask us how to do this).
Flash ClockworkMod Recovery attached to this post.
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Wipe Data! Seriously! Do it!
Install the ROM zip from sdcard
Install gapps package linked here (http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps)
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Yeah. It's stuck at the logo. I reboot into recovery and I get the log errors. That's 6 Odin resets today.
Make sure you use atlas.pit when restoring to stock. If you are following those directions exactly, all I can say at this point is to try another ROM (maybe MIUI or OMGB) and see if that works, unless another poster wants to take a stab at this.
Yeah, I'm using the atlas 2.2.pit
I had it working yesterday but only if I flashed the rom using the orange recovery through ROM Manager. I might try that again.
Hyphnx said:
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Click to expand...
Click to collapse
I think the nightly might be your problem?...my $.02...and there are a lot of extra steps but it works for me if I really can't get cm7 to load (I've done this more then once)
Odin eb01 with the atlas 2.2pit and reboot fully when odin is done.
Pull battery...Odin cwm 3/30 fix all..and when that's done, install battery and 3 finger salute into recovery....wipe everything and flash com rom 2.0 and reboot.
This is where you may have to try different recoveries, putting com rom on your phone gives you root, recovery and voodoo. So from here if your recovery doesn't properly flash cm7 you can simply pull the battery re odin a different recovery and try again, as long as you don't try to reboot the phone.
Make sure you are using the 7/17 build from, jt's pretty much official cm7 Thread, not the nightly. even if this is not what you want it should properly get you to mtd format, so another rom on an mtd build can just be flash the good old way.
I've had the cwm4.x.x.x work fine and then today it would not work after I flash a different kernel with out wiping anything...oops! I've had 3/30 fix all cwm give me the best results but even today would not work.
What did work was using the com rom recovery to flash times infinity's purple recovery zip...reboot recovery into the purple one, and then wipe everything and flash cm7 7/17...ugh finally! Once I was there just power button menu... reboot recovery to install gapps, and glitch. You could at this point wipe cache and dalvik and flash nightly if you wanted...hope some of this helps.
Sent from my SCH-I500 using XDA App
I've had the same problem tryin to flash all mtd based roms...it always sticks at the samsung logo when I three finger back to recovery. I get the error logs aswell...**** sucks lol. That's odining ed05, fully boot, odin cwm 4 fix for cm7, boot recovery, wipe data,cache, dalvick, install rom.zip, all for a samsung logo and log error lol. So instead of spending 5hrs trying to flash a rom, I spent 10min and flashed power wash ed05, works great!
Related
Tried to install CM7 on my Vibrant 2.2 Rooted using Superoneclick method - Phone has superuser, Busybox, rom manager premium. I tried to flash clockwork recovery...
Clicked on Rom Manager
Clicked Flash ClockworkMod Recovery
Tried both Galaxy S Vibrant and Vibrant (MTD) options (seperately)
current recovery showed both versions after each flash and reboot
Clicked reboot into recovery
Phone boots into stock recovery
Tried reinstall packages like 5 times after each flash
always get signature verification errors
Im stuck here.. Could not figure out how to get past this issue
Any help greatly appreciated!
Only flash cwm recovery mtd 2.xxx since you're going from froyo to cm7.
Flash the recovery again, reboot into recovery, reinstall package, wipe data, reboot......sometimes this worked when I had issues a while ago.
Please back up everything before you flash...
I have just learned that I have the Stock 3e recovery on my phone... I have read that on the I9000 that you have to flash a new kernal... Im not sure if this is my problem, but last time I did this I bricked my phone where it would not power at ALL
On your phone, go to settings, applications, development, is debugging checked?
crazy25000 said:
On your phone, go to settings, applications, development, is debugging checked?
Click to expand...
Click to collapse
Yes it is, I had to use that for Superoneclick
There you go.....I've used this.
http://forum.xda-developers.com/showpost.php?p=7324731&postcount=1
crazy25000 said:
There you go.....I've used this.
http://forum.xda-developers.com/showpost.php?p=7324731&postcount=1
Click to expand...
Click to collapse
Thats the exact Thread I was using before
1. Download ROM Manager from the Market.
2. Flash Recovery.
3. Choose Vibrant as your phone.
4. Accept the Superuser prompt.
5. On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6. Watch the backup go!
After step 5 It always says signature verification failed, no matter how man times i click it or reboot phone
Even if I force reboot by holding all three buttons or reboot into recovery from rom managers menu it does this
Have you heard of this 3e recovery not working and only 2e works
Did you use Odin to flash the kernel that's posted?
Here is froyo that has modified recovery and it's rooted.....makes everything easier
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
crazy25000 said:
Did you use Odin to flash the kernel that's posted?
Here is froyo that has modified recovery and it's rooted.....makes everything easier
Well I decided to flash using the file you specified... this file gave me the GTI9000 software that bricked my phone last time... I hope it doesnt brick my phone --- This is not the SGH-T959 Firmware....
Click to expand...
Click to collapse
spaceman8988 said:
crazy25000 said:
Did you use Odin to flash the kernel that's posted?
Here is froyo that has modified recovery and it's rooted.....makes everything easier
Well I decided to flash using the file you specified... this file gave me the GTI9000 software that bricked my phone last time... I hope it doesnt brick my phone --- This is not the SGH-T959 Firmware....
Click to expand...
Click to collapse
Well I got it back to the original software because it did brick my phone again, but it was just a soft brick. I restored it back to 2.2 froyo and I have it rooted again.. Not sure what to do now, I think i need to try getting back to the 2e recovery system
Click to expand...
Click to collapse
Ill be free later if you want to work on this.....sorry about the soft brick, I've done it this way and it never bricked, but not every phone is the same
if u want to install cm7 on ur phone its really quite easy! odin back to stock 2.1 as 2.1 is easier to root then froyo. Once ur at 2.1 root the eclair method by installing the update package twice and the second time it should turn green. Now go into Rom manager premium it wont u download the cm7 nightlies if ur on 2x! Pick Vibrantmtd and pick 3x not 2x. then when thats done go into downloads and download the newest cm7 nightlie which is 33#. For ur first nightlie always choose all three! Wipe data, wipe dalvik, backup rom. Then when u move on to #34 u only have to pick the 2-wipe dalvik and backup rom. As its always good to wipe data on ur first cm7 nightlie. With rom manager premium its as easy as 1.2,3
http://forum.xda-developers.com/showthread.php?t=849028
movieaddict said:
if u want to install cm7 on ur phone its really quite easy! odin back to stock 2.1 as 2.1 is easier to root then froyo. Once ur at 2.1 root the eclair method by installing the update package twice and the second time it should turn green. Now go into Rom manager premium it wont u download the cm7 nightlies if ur on 2x! Pick Vibrantmtd and pick 3x not 2x. then when thats done go into downloads and download the newest cm7 nightlie which is 33#. For ur first nightlie always choose all three! Wipe data, wipe dalvik, backup rom. Then when u move on to #34 u only have to pick the 2-wipe dalvik and backup rom. As its always good to wipe data on ur first cm7 nightlie. With rom manager premium its as easy as 1.2,3
http://forum.xda-developers.com/showthread.php?t=849028
Click to expand...
Click to collapse
Lol Tried this when I had to flash back to stock after I soft bricked my phone... For some reason, every time I tried to root it again it would always tell me I was already rooted, but would not let me actually reinstall the packages... I tried the update.zip method and the superoneclick with both exploits. Its like even if I wipe it something gets stuck behind..
crazy25000 said:
Ill be free later if you want to work on this.....sorry about the soft brick, I've done it this way and it never bricked, but not every phone is the same
Click to expand...
Click to collapse
Was it the same software that you flashed? cause the Eugene software in your link always puts the I9000 software on it... Its a Vibrant(SGH-T959) and the boot screen changed to I9000 and it wouldnt boot past that when I flashed it with yours.
spaceman8988 said:
spaceman8988 said:
Well I got it back to the original software because it did brick my phone again, but it was just a soft brick. I restored it back to 2.2 froyo and I have it rooted again.. Not sure what to do now, I think i need to try getting back to the 2e recovery system
Click to expand...
Click to collapse
very simple, if you have already done the "flash CWM" via Rom Manager, then you should have an update.zip file in your root. Odin back to stock and hit reinstall packages. It should reboot into recovery. Hit reinstall packages again and you should have green clockwork..
OR
You can try to flash a stock + voodoo kernel via Odin as well.
http://forum.xda-developers.com/showthread.php?t=870480
Good luck,.
Click to expand...
Click to collapse
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
Im running into problems with Cyanogen Mod 7 I can't get it to install. I choose the zip in cwm and it sits there for a sec then gives me either a bunch of errors or a status 7. Its like the zip is corrupt. I tried re downloading it with no luck. I tried installing the 7 04 build and it just bootloops or doesn't work. I installed the june 19 build just fine though. Anyone else having problems? I got ukb to work just fine too
EDIT: Has been resolved. Thanks everyone for your kindness to my noobness
Have u tey to flash custom recovery tht jt list in his op then flash from tht 1
Sent from my I500 using XDA App
Yeah I've tried to do it from there too. I actually got the 7/04 build to flash. Then when I try to flash the 7/13 one it gives me a status7.
shakeandscream said:
Yeah I've tried to do it from there too. I actually got the 7/04 build to flash. Then when I try to flash the 7/13 one it gives me a status7.
Click to expand...
Click to collapse
i ran into the same thing. If your already on 7/04 go into orange recovery, wipe cache and dalvik and it should work. If not try flashing one of the OTB kernals, rebooting then go to recovery and try to flash.
Orange recovery? Like do I use the recovery that I already have or should I download rom manager on 7/04 and flash that recovery because if that's not the case and I use the one I already have it won't work cause I tried it. :\
shakeandscream said:
Orange recovery? Like do I use the recovery that I already have or should I download rom manager on 7/04 and flash that recovery because if that's not the case and I use the one I already have it won't work cause I tried it. :\
Click to expand...
Click to collapse
Once you have 7/4 test, you should go to Recovery via the reboot menu or adb reboot recovery.. DON'T use the power & vol- 7 vol+ method..
Also do not use rom manager with the fascinate period.
bobthesalesclerk said:
Also do not use rom manager with the fascinate period.
Click to expand...
Click to collapse
Until jt's commits get official CyanogenMod support - once that happens new CM7 nightlies will be posted to ROM Manager and the CM7 version of ROM Manager will work 100% for the Fasc.
Another Fascinating post by my XDA app...
it's frustrating I know.. make sure you are on 7/04 build. When you flash CM7, instead of the red recovery, you should get the orange recovery. You can only flash 7/13 build from the orange recovery. Wipe cache/dalvik and you should be able to flash 7/13 without any problem.
If you are getting bootloop from 7/04, that's because you did not wipe data on red recovery before you flashed 7/04. Go back to the red recovery, wipe data, and flash 7/04 again. Flash 7/04 fully on orange recovery, reboot recovery, flash 7/13 after wiping cache/dalvik, profit.
edit-moved to Q&A
So how do I get orange recovery? Cause when I flash 7/04 I still have my old recovery
Sent from my SCH-I500 using XDA App
After you boot 7/4 cm7, you want to get into recovery by holding power button, selecting reboot, then recovery. Or open a terminal and type su <return> reboot recovery <return>.
After you are on cm7 my experience is never do 3 button recovery or it will hose everything that you have achieved to this point.
ej
Okay well I got it installed. What I did was install 7/04 build, then I went into Rom Manager and chose the recovery I had installed or whatever. Then I rebooted into recovery and it was orange. Then I installed it just fine. I am now running on the 7/13 update Thanks everyone for your help, took me a bit to figure out but I got it.
OK, so it has been a while since I have had to flash recoveries etc... Anyway, I Odin'ed back to stock today because I had to go to the Verizon store to talk about my replacement phone so I wanted to have it unrooted. Anyway, now I am trying to get CM7 back on for the time being but I can't get in to CWM. I tried pushing the cwm_recovery_all tar file via ODIN and when I do the three finger boot, it still brings me to the stock recovery and when I hit apply update.zip it fails.
What the heck am I doing wrong? I figured I could just get recovery on there and not have to worry about "rooting" since all the ROM's have that built in anyway.
Any help is appreciated!
Nevermind, I think I figured it out
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Kevin Gossett said:
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Click to expand...
Click to collapse
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
xceebeex said:
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
Click to expand...
Click to collapse
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
efan450 said:
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
My point is that I was able to boot in to red recovery (2.5.1.x) BEFORE flashing any custom kernel. I understand that CM7 has a kernel built in, but I was able to boot in to both the red recovery and jt's cwm 4 fix (4.0.1.0) before flashing any ROMs/Kernels. I wasn't even rooted (flashing CM7 is what rooted me).
After re-reading what he wrote, the way he says it is correct. I must have read it wrong the first time. So I apologize for saying "Nope." For some reason I read it as if he was saying I had to flash a custom kernel before being able to boot in to any recovery. He is just saying that you can't let the phone fully boot after pushed the recovery (which is what I ended up doing in my steps).
Sorry for the confusion.
No problem...glad you didn't take offense I'm just nearly thinking of all the noobs that are just getting into this kind if stuff and when they read the thread they might be misinformed...
that being said I've been on cm7 for a while and I know not to flash with anything other than the included recovery, I can confirm power button menu gets you to the new blue recovery but if you three finger salute it (done on accident just out of habit) you will get to an older recovery! In my case the old red one....Weird having both on the phone simultaneously, but it's no prob as long as we only use the new recovery to flash anything.
Sent from my SCH-I500 using XDA App
I really don't know who to credit for this, so if your reading this Credits to you! Koush & CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
09/30/12 (Mainly a JellyBean reference)
Easily switch between ROMS and the different partition layouts!
Reboot to recovery and flash cwm4-fix, power the phone down (might need to pull battery) and three finger back into recovery!
Wipe data, flash chosen GB,ICS, or any partion JB ROM from any order! (ie: downgrade or upgrade)
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
cwm4-repack no asserts Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)(Allows force flashing)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
cwm6_recovery Contents:
Latest source built CWM Based 6.0.1.0 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
cwm4-repack no asserts 5.83 MB - 06/27/12
cwm6-recovery (JB) - 5.15 MB - 07/29/2012
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Click to expand...
Click to collapse
If you download, power off, three finger and flash cwm4-repack and reboot it should break the boot loop and continue booting your ROM (However sometimes when updating the recovery it will automatically reboot to recovery, reboot now if this happens). Assuming ICS...
Also if you power down, three finger, do nothing and reboot, your phone will actually reboot! Assuming you already flashed cwm4-repack...
Not to sound dirty but I was three fingering all day while doing yard work...
Back n forth from CM7,CM9 & AOKP Based!
notta said:
I really don't know who to credit for this, so if your reading this Credits to you! CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
Click to expand...
Click to collapse
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Nice dude! that's nice to keep on the Sd card.
Sent from my Glitched AOKP Unicorn.
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
tetrismonkey said:
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
Click to expand...
Click to collapse
The horror...
Sent from my Glitched AOKP Unicorn.
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
jmac9 said:
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Click to expand...
Click to collapse
So am I to assume all is well with both scenarios...
notta said:
So am I to assume all is well with both scenarios...
Click to expand...
Click to collapse
Sorry....never went back to twrp. With the new devil kernal, I've been playing too much to want to try anything different. On a side note, I went back to the glitch kernal this morning (experiment) and had issues with trying to get the Rom to load and then actually had to go the three fingered route. This worked great once I followed your directions EXACTLY!
Note to anyone else.....if you are flashing a Rom that requires gapps, make sure you flash the cwm-4 repack right after the Rom....BEFORE the gapps. Loop doesn't break if you try to slip the gapps in there too soon I found.
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
SeatownGST said:
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
Click to expand...
Click to collapse
Not sure exactly what your asking but typically you would compile cm7 for cwm4 and cm9 for cwm5!
Or the answer for exactly how I read this:
A computer, some time and some knowledge...
notta said:
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
Click to expand...
Click to collapse
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
SotYPL said:
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
Click to expand...
Click to collapse
Well, my apologies for mis-leading. However I did just repeat the above steps exactly, coming from Geewiz EH03 to a today built build 40! Perhaps a limitation against pure stock?
If this was stock and you are put in the position again, you could try flashing a non stock kernel after a odin/heimdall of cwm of course! I suppose this could be an issue... Maybe?
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Click to expand...
Click to collapse
I'm not really sure! I was going to attempt a look but a short search came up empty for some older sources.
Speaking of, they need a smiley that is bashing his head against a wall in shame..
Clearly, Credits for this go to Koush! (And queue the above mentioned smiley)
notta said:
Not to sound dirty but I was three fingering all day while doing yard work...
Click to expand...
Click to collapse
LMAO!! Nice! And good guide btw, I still have no idea why three fingering does that :/
Sent from my SCH-I500(Fascinate)
It seems with the recovery wipe repack method, i get all the way to the point of the rom booting up, but it will just sit there and play the boot animation over and over and over.... how long is it supposed to take? I'm beginning to think i'm going to have to odin... ugh!
notta, you needta update this to cwm6 for jb, please & ty
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
+1
Sent from my A500 using xda app-developers app
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
lifeofcoding said:
+1
Click to expand...
Click to collapse
Technically it isn't needed! CWM4 is all I have been using for JB so far. Works perfect to break the 3 finger curse and also to downgrade the recovery for better JB flashing in some scenario's.
Truth be told I only need heimdall now once in a blue moon and that is always because of something I'm trying. :silly:
I still posted it though as I figure it may come in handy at some point or at least have an odin/heimdall alternative. In OP for those in seeking...
Also while getting this together for you guys, I noticed the files in the OP are pushing close to a 1,000 downloads. Yet only 9 people have thanked me.
Has this not been useful? Just Curious...