Related
Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working? I'm running Starburst 1.7 with the stable kernel if it matters.
Sent from my SPH-D710 using xda premium
poppygt said:
Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No, it wasn't listed previously.
Probably the first stages of giving us official support.
I never installed it before because it was easy enough to use Odin and I knew we weren't supported when I got my device. That's cool though because I had read he was gonna nail down recovery and pass the phone onto the team for development. Nice step in the right direction.
Sent from my SPH-D710 using xda premium
mattykinsx said:
No, it wasn't listed previously.
Probably the first stages of giving us official support.
Click to expand...
Click to collapse
Exactly. Koush writes cwm and he is supposed to be our dev for cm7 too.
I flashed it from rom manager. It didn't work. I tried booting into recovery by turning off the phone and using volume up and power and it brought up stock recovery but then gave me a "!" Error. I also tried booting into it through rom manager with the same results.
Sent from my Samsung Galaxy S II Epic 4G Touch
Has anybody successfully flash cwm from rom manager or boot into recovery from rom manager?
This is good news! Koush is obviously working on support. Cool!
Samsung Galaxy S II
I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App
deano0714 said:
I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Still good because rom manager allows you to select quick backup and restore which speeds thing up.
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Really? Still didn't work for me... I just went into rom manager, flashed cwm and then selected reboot into recovery and when it rebooted I got the box with the arrow then the triangle with the "!" In it.
I'm fully stock(kernel and rom) just rooted.
Sent from my Samsung Galaxy S II Epic 4G Touch
Worked great I formatted usb and ad storage, odined the new recovery, and flashed the new recovery through rom manager by selecting download recovery, after it downloads click install rom from sd, go into clockwork folder/downloads and select the new recovery, choose wipe dalvik and Ok. It boots into recovery, flashes, performs back ups seems to be fully functional so far. Thanks Koush! You daMan, may we please, respectfully request some CM7 bits? Been waiting a year and half to get some bacon again. (had the OG Epic previously)
Sent from my SPH-D710 using XDA App
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same exact thing happens to me!
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Instead of pulling the battery, I held the power button until the phone rebooted in CWM itself.
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Midnight rom with lostkernal
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk
musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.
move_over said:
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.
Click to expand...
Click to collapse
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch
graffixnyc said:
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch
Click to expand...
Click to collapse
Same for me rom manager says i have 5.0.2.6 but when i boot into recovery it shows the older version
Chris's CWM now shows up as 5.0.2.6,and rom manager can reboot into recovery
Sent from my SPH-D710 using Tapatalk
Ok, so i followed all of the tutorials for installing the
Blazer rom onto my samsung epic touch 4g
now when it loads up
it turns on
starts loading
then turns off
how can i fix this?
Plus its not evenclockwork mod anymore, its some rogue one now or something
help please?
i made a backup in clockwork
but this new one doesnt recognize it...
EDIT:
Rogue ET Recovery 1.1.2 (CMW v5.0.2.7)
Same thing happened to me. My MD5 Sum wasn't recognized. Had to flash Caulkins Stock to get back up and running.
After I flashed that I was in original CWM.
rocketmn333 said:
Ok, so i followed all of the tutorials for installing the
Blazer rom onto my samsung epic touch 4g
now when it loads up
it turns on
starts loading
then turns off
how can i fix this?
Plus its not evenclockwork mod anymore, its some rogue one now or something
help please?
i made a backup in clockwork
but this new one doesnt recognize it...
EDIT:
Rogue ET Recovery 1.1.2 (CMW v5.0.2.7)
Click to expand...
Click to collapse
OK Rogue is a derivative of Clockwork and with that said before you rooted you should of done some more research. What you should do is look for calkulins format all zip and flash it then flash the rom again. Also download another version of the rom just incase you have a corrupted zip.
Lastly try not to do anything else until you do some more research.... Quite a few stickys that can help you....
Sent from my Xoom using Tapatalk
h4304 said:
Same thing happened to me. My MD5 Sum wasn't recognized. Had to flash Caulkins Stock to get back up and running.
After I flashed that I was in original CWM.
Click to expand...
Click to collapse
Guys Rogue recovery is much better IMO
Sent from my Xoom using Tapatalk
ok, so after going through the menus over and over, the recovery finally let me use my clockwork recovery, and now im back into my phone like nothing happened
idk why this didnt happen from the begining but w.e
Can anyone lead me to a tutorial of where i can completely wipe my phone like i just got it out of the box at the sprint store, unrooted and all
i wanna go through this process from the begining the right way
playya said:
OK Rogue is a derivative of Clockwork and with that said before you rooted you should of done some more research. What you should do is look for calkulins format all zip and flash it then flash the rom again. Also download another version of the rom just incase you have a corrupted zip.
Lastly try not to do anything else until you do some more research.... Quite a few stickys that can help you....
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Also, i did find that file, i downloaded it from the same page i got the rom from, only it was a modified copy?
idk, it said to use it, so i did
anyway, phone is back to stock with root and clockwork back on it, so ima leave it for now, until i do more research like you said
I just flashed this rom 5 minutes ago. You're not following the instructions
Sent from my SPH-D710 using XDA App
Hi i used the wrong recovery to backup my Samsung epic touch and now all I get is a blue light it won't start or boot to recovery or odin any help will be appreceiated. I'm using EL26 kernal to flash ICS roms I went to cwm touch recovery instead of rouge recovery and now I'm stuck.
I do also have the FE02 plus recovery I forgot to mention that with having all my stress.
Sounds like another hard brick... Your only small hope would be in a usb jig and then a jtag service, but both might fail and you now have an expensive paperweight.
Sent from my SPH-D710 using Tapatalk 2
Try the manual method to get into download mode (copied from sfhub's TAR posts):
Code:
Method #1
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Without getting into download mode you're probably a victim of the eMMC lockup. But to know for sure, what kernel version were you on when you last tried a CWM restore or wipe?
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
BTW it won't go into download mode
bigdaddy619 said:
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
Click to expand...
Click to collapse
OK, the behavior - specifically that the phone froze and wouldn't respond until you pulled the battery - matches the eMMC lockup. Unfortunately yours appears to be locking up during the boot process which is why you can't get to download mode. Only way to fix is to take to Sprint for replacement.
Still curious how you did it though - and let's try our best to find it so that others don't suffer the same fate:
bigdaddy619 said:
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
Click to expand...
Click to collapse
Can you link to the post containing the file you used to flash? I'm not aware of an FE02 build - maybe Agat's FF02 repack? And can you also include source of CWM touch if from a different ROM?
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
shiftr182 said:
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
Click to expand...
Click to collapse
Yea even then he stated fe02? Isnt that an ics kernal and also used touch which neither is good for flashing a new rom.. either way people make mistakes and like said already you have a nice paperweight.. to sprint you must go lol
Sent from my SPH-D710 using XDA
http://forum.xda-developers.com/showthread.php?t=1342728 this the link where i got the e4gtauto.
If you want CWM use Option C in the Auto Root Package to install EL26+CWM (you are already rooted so Option A is not necessary)
OOOOOPS it was the FD02+recovery sorry
bigdaddy619 said:
OOOOOPS it was the FD02+recovery sorry
Click to expand...
Click to collapse
There's your culprit. Once you get it replaced you'll want to stick with GB or FF02 repack which was done with care to avoid triggering the lockup for now. Sorry you had to find out this way...
Sent from my SPH-D710 using XDA
Close please
Sent from my MB855 using xda app-developers app
where did you find cmw touch?
I've been looking all over for it!
emottau said:
I've been looking all over for it!
Click to expand...
Click to collapse
Looking for what?
Sent from my MB855 using xda app-developers app
when i hit reboots it will go through, vibrate once and show the samsung logo and black screen and it doesnt power on.
had this issue with different roms.
anyway to fix???
Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2
VoiD_Dweller said:
Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
already did, used it before flashing each rom, i got this phone brand new last week too
AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
What recovery are you using? Please include the version too.
RTFOP said:
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
will try it
Afeety said:
What recovery are you using? Please include the version too.
Click to expand...
Click to collapse
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now
AngryDinosaur said:
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now
Click to expand...
Click to collapse
Try using TWRP 2.22
Sent from my SGH-T989 using xda premium
you may be semi-bricked. Just try a gingerbread rom or something.
AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
So you did this before the flash.. Do this.. Pull the battery, insert the battery, turn phone on and boot it into recovery (not into ROM) and flash the cache wipe script.. See if that works.
Am I correct in you saying the roms work and it just doesnt reboot properly?
ya when i hit reboot it vibrates once to power off but then it will vibrate one more time and show the samsung logo and black screen, need to pull battery to get out of it
Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime
idbl_fanatic said:
Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime
Click to expand...
Click to collapse
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch
patrao_n said:
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
No, you can do shut down, reboot, recovery, boot loader, and hot boot.
idbl_fanatic said:
No, you can do shut down, reboot, recovery, boot loader, and hot boot.
Click to expand...
Click to collapse
ill try quick boot too then
Mine did that too when I first installed a cm9. I did a complete wipe from cwm (dark side super wipe because I was on non-touch) then reflashed my recovery (flashed twrp via cwm) and it stopped having issues and not one since.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Isn't the CWM supposed to be updated to 5.0.2.7?
I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.
idbl_fanatic said:
I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.
Click to expand...
Click to collapse
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.
d01100100 said:
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.
Click to expand...
Click to collapse
Cwm 6.0.1.4 works for me I just prefer twrp. Moral of the story if you flash a recovery and have issues rebooting to it check the md5 (should do this with anything you flash) and re-flash in case it was a bad download or bad install.
Cwm when flashed from Odin always gave me issues until I did a dark side and reflashed.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!